From d8123ba5cdf964eb668879a2ee3a5c8aa353d569 Mon Sep 17 00:00:00 2001 From: Chris Arderne Date: Fri, 3 Jul 2026 13:11:39 +0100 Subject: [PATCH] chore: update self-host image release references --- .github/workflows/publish-webapp.yml | 4 ++++ .github/workflows/publish-worker-v4.yml | 4 ++++ docs/self-hosting/kubernetes.mdx | 16 ++++++++-------- 3 files changed, 16 insertions(+), 8 deletions(-) diff --git a/.github/workflows/publish-webapp.yml b/.github/workflows/publish-webapp.yml index 3f8c03a4166..421257a1e02 100644 --- a/.github/workflows/publish-webapp.yml +++ b/.github/workflows/publish-webapp.yml @@ -76,6 +76,10 @@ jobs: # therefore publishes to its own package automatically. image_tags=$REF_WITHOUT_TAG:${STEPS_GET_TAG_OUTPUTS_TAG} + if [[ "${STEPS_GET_TAG_OUTPUTS_TAG}" =~ ^v4\.[0-9]+\.[0-9]+$ ]]; then + image_tags=$image_tags,$REF_WITHOUT_TAG:v4,$REF_WITHOUT_TAG:latest + fi + # when pushing the mutable main tag, also push an immutable-by-convention # full-commit-sha tag so a commit can be resolved to a specific digest if [[ "${STEPS_GET_TAG_OUTPUTS_TAG}" == "main" ]]; then diff --git a/.github/workflows/publish-worker-v4.yml b/.github/workflows/publish-worker-v4.yml index 777919a67b7..5906b34ff4a 100644 --- a/.github/workflows/publish-worker-v4.yml +++ b/.github/workflows/publish-worker-v4.yml @@ -76,6 +76,10 @@ jobs: ref_without_tag=${IMAGE_REGISTRY}/${STEPS_GET_REPOSITORY_OUTPUTS_REPO} image_tags=$ref_without_tag:${STEPS_GET_TAG_OUTPUTS_TAG} + if [[ "${STEPS_GET_TAG_OUTPUTS_TAG}" =~ ^v4\.[0-9]+\.[0-9]+$ ]]; then + image_tags=$image_tags,$ref_without_tag:v4,$ref_without_tag:latest + fi + echo "image_tags=${image_tags}" >> "$GITHUB_OUTPUT" env: IMAGE_REGISTRY: ${{ inputs.image_registry || vars.IMAGE_REGISTRY || format('ghcr.io/{0}', github.repository_owner) }} diff --git a/docs/self-hosting/kubernetes.mdx b/docs/self-hosting/kubernetes.mdx index 8fbf8aab90a..3d6d1bc66db 100644 --- a/docs/self-hosting/kubernetes.mdx +++ b/docs/self-hosting/kubernetes.mdx @@ -61,7 +61,7 @@ webapp: ```bash helm upgrade -n trigger --install trigger \ oci://ghcr.io/triggerdotdev/charts/trigger \ - --version "~4.0.0" \ + --version "^4.5.0" \ --create-namespace ``` @@ -107,11 +107,11 @@ The following commands will display the default values: ```bash # Specific version helm show values oci://ghcr.io/triggerdotdev/charts/trigger \ - --version "4.0.5" + --version "4.5.0" # Latest v4 helm show values oci://ghcr.io/triggerdotdev/charts/trigger \ - --version "~4.0.0" + --version "^4.5.0" ``` ### Custom values @@ -171,7 +171,7 @@ Deploy with your custom values: ```bash helm upgrade -n trigger --install trigger \ oci://ghcr.io/triggerdotdev/charts/trigger \ - --version "~4.0.0" \ + --version "^4.5.0" \ --create-namespace \ -f values-custom.yaml ``` @@ -510,14 +510,14 @@ You can lock versions in two ways: # Pin to a specific version for production helm upgrade -n trigger --install trigger \ oci://ghcr.io/triggerdotdev/charts/trigger \ - --version "4.0.5" + --version "4.5.0" # The app version will be different from the chart version # This is the version of the Trigger.dev webapp and supervisor # ..and should always match your Trigger.dev CLI version helm show chart \ oci://ghcr.io/triggerdotdev/charts/trigger \ - --version "4.0.5" | grep appVersion + --version "4.5.0" | grep appVersion ``` **Specific image tags:** @@ -525,11 +525,11 @@ helm show chart \ ```yaml webapp: image: - tag: "v4.0.0" + tag: "v4.5.0" supervisor: image: - tag: "v4.0.0" + tag: "v4.5.0" ``` The chart version's `appVersion` field determines the default image tags. Newer image tags may be incompatible with older chart versions and vice versa.