ci(internal-workflows): make release publishing recoverable - #933
Merged
Merged
Conversation
homelab-agent-bot
Bot
force-pushed
the
fix/publish-retry
branch
from
September 17, 2026 00:46
83bceed to
c1b4b35
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds a manual publish trigger for an existing release tag while keeping the published template version unchanged. Publishing automation is loaded from main and release source remains pinned to the requested tag. If the target version already exists, recovery proceeds only when Coder reports it failed and inactive: the failed record is renamed with an ID-derived suffix, then the replacement is pushed under the original release version. Successful or active versions are never altered.
Validation: pre-commit run --all-files; source-verified against Coder v2.37.1 template-version list and PATCH contracts.