Update release script

Signed-off-by: Kevin Su <[email protected]>
flyteorg · Sep 26, 2023 · 0f4e71f · 0f4e71f
1 parent 8c05f4e
commit 0f4e71f
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 2 deletions.
diff --git a/charts/flyteagent/values.yaml b/charts/flyteagent/values.yaml
@@ -23,7 +23,7 @@ image:
   # -- Docker image for flyteagent deployment
   repository: ghcr.io/flyteorg/flyteagent
   # -- Docker image tag
-  tag: 1.8.3
+  tag: 1.8.3  # FLYTEAGENT_TAG
   # -- Docker image pull policy
   pullPolicy: IfNotPresent
 ports:

diff --git a/script/release.sh b/script/release.sh
@@ -7,7 +7,7 @@ set -ex
 #                 In other words, if we have two consecutive releases the latest tag in the second release is going to point to an invalid
 #                 tag (because there will not be images tagged with the previous release tag).
 LATEST_TAG=$(git tag | sed 's#[^/]*/##' | sort | tail -n 1)
-
+FLYTEKIT_TAG=$(curl --silent "https://api.github.com/repos/flyteorg/flytekit/releases/latest" | jq -r .tag_name)
 FLYTECONSOLE_TAG=$(curl --silent "https://api.github.com/repos/flyteorg/flyteconsole/releases/latest" | jq -r .tag_name)
 
 # bump latest release of flyte component in kustomize
@@ -36,6 +36,8 @@ sed -i "s,image:[^P]*# FLYTECOPILOT_IMAGE,image: cr.flyte.org/flyteorg/flytecopi
 sed -i "s,image:[^P]*# FLYTECOPILOT_IMAGE,image: cr.flyte.org/flyteorg/flytecopilot:${LATEST_TAG} # FLYTECOPILOT_IMAGE," ./charts/flyte-core/values.yaml
 sed -i "s,tag:[^P]*# FLYTECOPILOT_TAG,tag: ${LATEST_TAG} # FLYTECOPILOT_TAG," ./charts/flyte-binary/values.yaml
 
+sed -i "s,tag:[^P]*# FLYTEAGENT_TAG,tag: ${FLYTEKIT_TAG} # FLYTEAGENT_TAG," ./charts/flyteagent/values.yaml
+
 go get github.com/flyteorg/flyte/flyteadmin@${LATEST_TAG}
 go get github.com/flyteorg/flyte/flytepropeller@${LATEST_TAG}
 go get github.com/flyteorg/flyte/datacatalog@${LATEST_TAG}