Skip to content

fix(release): preserve the monotonic sequence ledger - #32

Merged
rldyourmnd merged 1 commit into
mainfrom
fix/release-explicit-monotonic-sequence
Aug 24, 2026
Merged

fix(release): preserve the monotonic sequence ledger#32
rldyourmnd merged 1 commit into
mainfrom
fix/release-explicit-monotonic-sequence

Conversation

@rldyourmnd

Copy link
Copy Markdown
Contributor

Summary

  • require an explicit monotonic release_sequence workflow input
  • stop deriving trust order from repository-local github.run_number
  • document that repository migration does not reset the consumer acceptance ledger

Root cause

The verified public 0.1.2 canary used sequence 4, while the existing trusted GDS lineage had already accepted sequence 43. Offline verification correctly quarantined it as a rollback.

Verification

  • go test ./core/releasebuilder
  • actionlint .github/workflows/release-bundle.yml
  • scripts/validate_go_core.sh --quick
  • git diff --check

@rldyourmnd
rldyourmnd merged commit d96ad1e into main Aug 24, 2026
7 checks passed
@rldyourmnd
rldyourmnd deleted the fix/release-explicit-monotonic-sequence branch August 24, 2026 04:56
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