fix(ci): chart releases must not masquerade as product releases - #128
Merged
Conversation
The first chart-releaser run (chart 0.1.1, triggered by the PR #122 merge) created the GitHub release libredb-studio-0.1.1 and, via chart-releaser's mark_as_latest default, took the repository's Latest marker away from the 0.9.41 product release (restored manually). - helm-release.yml: mark_as_latest: false - chart releases never claim the Latest marker. - docker-build-push, release-artifacts, npm-publish: release-triggered jobs now skip libredb-studio-* tags explicitly. Today GITHUB_TOKEN events do not trigger these workflows at all, but that protection is implicit; this guard keeps product pipelines closed to chart releases even if the publishing token ever changes.
|
This was referenced Jul 4, 2026
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The Helm chart release for 0.1.1 (first chart-releaser run, triggered by the #122 merge) created GitHub release
libredb-studio-0.1.1and took the repo's Latest marker from the 0.9.41 product release (already restored manually:gh release edit 0.9.41 --latest).Verified blast radius before fixing: no release-triggered workflow ran for the chart release (chart-releaser publishes with
GITHUB_TOKEN, whose events do not trigger workflows), so npm still has 0.9.41, GHCR tags are intact, and no standalone artifacts were produced. Artifact Hub showing chart 0.1.1 is correct and intended.Fixes:
helm-release.yml:mark_as_latest: falseon chart-releaserdocker-build-push.yml,release-artifacts.yml,npm-publish.yml: release-triggered jobs skiplibredb-studio-*tags explicitly (defense in depth for a future PAT switch)