Skip to content

fix(release): recover exact legacy promotions#9

Merged
monkseekee-max merged 1 commit into
mainfrom
fix/legacy-v1-promotion-recovery-20260718
Jul 18, 2026
Merged

fix(release): recover exact legacy promotions#9
monkseekee-max merged 1 commit into
mainfrom
fix/legacy-v1-promotion-recovery-20260718

Conversation

@monkseekee-max

Copy link
Copy Markdown
Contributor

Outcome

Allows one additional reviewed promotion only for an exact unpublished legacy v1 receipt. It preserves the normal v2 rule: after a v2 promotion merges, recover the exact publisher run instead of creating another release PR.

Safety boundaries

  • requires exactly one prior merged promotion PR
  • rejects any abandoned promotion PR
  • requires the legacy receipt source SHA, workflow run, exact-17 count, and asset digest to match the newly verified candidate
  • final-tag absence remains mandatory
  • keeps the deterministic release branch expected by the target publisher

Validation

  • actionlint on all organization workflows
  • governance workflow-policy fixtures: 41/41
  • governance commitlint tests: 8/8
  • git diff --check

This closes the pre-v2 v1.7.8 recovery gap without deleting provenance or moving a final tag.

@monkseekee-max
monkseekee-max requested review from a team and xionghaoh July 18, 2026 06:04
@monkseekee-max
monkseekee-max enabled auto-merge (rebase) July 18, 2026 06:04
@monkseekee-max

Copy link
Copy Markdown
Contributor Author

@xionghaoh v1.7.8 is waiting on this fail-closed legacy receipt recovery. All organization checks are green; please review when available.

@monkseekee-max
monkseekee-max removed the request for review from xionghaoh July 18, 2026 06:46
@monkseekee-max
monkseekee-max merged commit 733de63 into main Jul 18, 2026
4 checks passed
@monkseekee-max
monkseekee-max deleted the fix/legacy-v1-promotion-recovery-20260718 branch July 18, 2026 06:46
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