fix: skip version file updates on main for pre-release tags#1396
Merged
chris-rock merged 1 commit intomainfrom Feb 19, 2026
Merged
fix: skip version file updates on main for pre-release tags#1396chris-rock merged 1 commit intomainfrom
chris-rock merged 1 commit intomainfrom
Conversation
Contributor
imilchev
approved these changes
Feb 19, 2026
When a pre-release is created (e.g. v12.1.0-alpha.1), the release workflow was updating Chart.yaml, kustomization.yaml, and other version files on main with the pre-release version string. This is undesirable because main should only reference stable release versions. Add a !contains(github.event.release.tag_name, '-') guard to the prepare-release job, matching the convention already used in publish.yaml and release-manifests.yaml. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
chris-rock
force-pushed
the
fix/skip-prerelease-version-updates
branch
from
921847b to
6cfef8e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
v12.1.0-alpha.1) triggers the release workflow, theprepare-releasejob was updating version files (Chart.yaml,kustomization.yaml, etc.) onmainwith the pre-release version string. This leftmainreferencing a pre-release version, which is undesirable.!contains(github.event.release.tag_name, '-')guard to theprepare-releasejob condition, matching the convention already used inpublish.yamlandrelease-manifests.yaml.v12.1.0) continue to work as before.Test plan
make lint/actionspassesv12.1.0-alpha.1would be skipped by the updated conditionv12.1.0still triggers the job normally🤖 Generated with Claude Code