https://prefect.io logo
Title
l

Lukáš Polák

10/03/2022, 8:59 PM
Hi everyone. We're trying to update our prefect v1 from 1.2.2 to 1.4.0. Since we operate the infrastructure on our own, we use the official helm chart to deploy everything. That part works just fine. Our services make sure that they work with the correct version of prefect when they are about to start after an upgrade in the k8s cluster. This check makes sure that Prefect Server version matches the used prefect library. We use following graphl query to fetch the API version:
query { api { core_version } }
We ran into a problem with version 1.4.0 when prefect API reports version "1.3.0+13.g4142953a5". Is that intended?
The same problem is present in docker tags with version
1.3.1
c

Christopher Boyd

10/04/2022, 2:27 PM
Hi @Lukáš Polák - I’m not 100% sure here, I’ll raise this concern to the platform team
Hi, discussing with the team, that does not seem an issue here -
server
has a loose pin on
prefect
https://github.com/PrefectHQ/server/blob/master/setup.py#L8 setup.py
"prefect >= 1.0.0, < 2.0.0",
l

Lukáš Polák

10/07/2022, 9:07 AM
Hi @Christopher Boyd the real problem is this :
$ docker run -it --rm prefecthq/server:core-1.3.1 /bin/bash
root@b5f78de7ef45:/prefect-server# prefect version
1.3.0+13.g4142953a5
and
$ docker run -it --rm prefecthq/server:core-1.4.0 /bin/bash
root@1fe334fce751:/prefect-server# prefect version
1.3.0+13.g4142953a5
so it seems the images are generated incorrectly