Skip to content

feat(release): recover missed publications from last published ancestor tag - #9

Merged
DiegoV71 merged 7 commits into
mainfrom
fix/recover-unpublished-runtime-on-next-push-20261107
Nov 7, 2026
Merged

DiegoV71 merged 7 commits into
mainfrom
fix/recover-unpublished-runtime-on-next-push-20261107

Conversation

@DiegoV71

@DiegoV71 DiegoV71 commented Nov 7, 2026

Copy link
Copy Markdown
Contributor

Problem

If a runtime-affecting push fails CI, the next docs-only push is not release-eligible under the current github.event.before..github.sha classifier. The missed release remains unpublished indefinitely.

Implementation

  • Opt-in recover-unpublished: 'true' and read-only token inputs for the common runtime-changes Action, with old default behavior preserved.
  • Query published GitHub Releases (paginated); choose the most recent tagged ancestor with ZIP assets. Compare its tag to current HEAD using the same allowlist and no-rename diff.
  • Fail closed on GitHub API, missing tag or invalid ancestry failures; never rewrite existing releases.
  • If no published Release exists, fall back to the original current-push range (no forced first release on docs-only push).
  • Add regression tests for missing CI publication, successful publication, no previous Release, unrelated branches, tag validation, pagination, API failures and Action outputs.
  • Document rollout and security controls in RELEASE_RECOVERY.md and AGENTS.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.

@DiegoV71
DiegoV71 merged commit 2e96162 into main Nov 7, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant