Repository navigation
feat(release): recover missed publications from last published ancestor tag - #9
Merged
DiegoV71 merged 7 commits intoNov 7, 2026
Merged
Conversation
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.
Problem
If a runtime-affecting push fails CI, the next docs-only push is not release-eligible under the current
github.event.before..github.shaclassifier. The missed release remains unpublished indefinitely.Implementation
recover-unpublished: 'true'and read-onlytokeninputs for the commonruntime-changesAction, with old default behavior preserved.RELEASE_RECOVERY.mdandAGENTS.md.Rollout contract
This PR does not alter consumer workflows and must not itself publish a release. After platform CI passes, merge this first; then update each product's pinned SHA and opt-in to recovery via separate PRs. Release workflows must run on all pushes to
main, including docs-only pushes; preserve existing PR CI checks and publish gates.No product source, builder, GitVersion config, release asset or existing tag changes.