Repository navigation
fix: recover tagged releases after tooling advances main - #2552
Merged
codeforester merged 1 commit intoOct 14, 2026
Merged
codeforester merged 1 commit into
codeforester merged 1 commit into
Conversation
codeforester
deleted the
ci/2551-20261014-recover-tagged-release-after-tooling-change
branch
October 14, 2026 17:42
8 tasks
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.
Refs #2551\n\nAllow a narrowly scoped publication recovery when the release tag was already pushed before publication tooling advanced main. The recovery path requires:\n- an original canonical, sidecar-verified BOM;\n- the BOM release commit to match both local and remote annotated tag peel;\n- no published GitHub Release; and\n- no readiness blockers outside BOM/provenance/tag state.\n\nIt uses the BOM/tag commit for the remaining publication steps and keeps normal first-time publication strict.\n\nTests: PYTHONPATH=cli/python /Users/rameshhp/.base.d/base/.venv/bin/python -m pytest -q cli/python/base_release/tests/test_engine.py cli/python/base_release/tests/test_release_publication.py cli/python/base_release/tests/test_release_readiness.py (74 passed, 8 subtests)