[ci] Make the release workflows backport-safe - #6854
Merged
Conversation
Shipping v0.291.1 from its release branch required hand-patching every floating pointer out of the branch's workflow copies, because the release workflows assume each release is the newest version. Compute whether the released version is the newest existing tag and gate the floating pointers on it: the GitHub 'latest' marker, the :latest docker tag, and the docs.feldera.com deploy. Skip the post-release version bump on main when the published release is older than main's current version. Bump the action-gh-release pin: the old commit predates the make_latest input and silently ignored it. With this, a backport release runs through the normal release path without touching what newer releases own. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
gz
requested review from
jyotshnayaparla-00 and
mihaibudiu
and removed request for
mihaibudiu
August 13, 2026 17:20
feldera/cloud's release workflow needs the identical comparison; a composite action gives both repos one source of truth. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
The is-newest-version check now errors out when no vX.Y.Z tag is visible instead of defaulting to newest (a tagless checkout would have moved every floating pointer onto a backport), and only strict X.Y.Z tags participate in the comparison (a stray vnext or v1.2.3-rc1 tag outranks real versions under sort -V and would flip a normal release to a backport). Also correct the pin-bump rationale: v2.3.2 accepts make_latest but fails to apply it when publishing. Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
Signed-off-by: Gerd Zellweger <mail@gerdzellweger.com>
jyotshnayaparla-00
approved these changes
Aug 13, 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
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.
Shipping v0.291.1 from its release branch required hand-patching every floating pointer out of the branch's workflow copies, because the release workflows assume each release is the newest version (see the v0.291.1 backport runbook).
ci-release.yml: computeis_newest(released version vs highest existing tag) and gate the GitHubmake_latestmarker, the:latestdocker retag, and the docs.feldera.com deploy on it.ci-release.yml: bump thesoftprops/action-gh-releasepin — the old commit predates themake_latestinput and silently ignored it, which is why v0.291.1 briefly became the 'latest' release during the backport (remediated by re-marking v0.332.0).ci-post-release.yml: skip the version bump on main when the published release is older than main's current version. The publish jobs stay unguarded: registries order by semver, so publishing an old version is safe.With this, a future backport release can run through the normal release path without touching what newer releases own.