[cixzhang]

Maintainer impact

v0.7.7 cannot publish until the frozen 79-Changeset plan is consumed into package changelogs on the dedicated release branch.

Intended invariant

The release keeps the version, cut SHA, branch, and frozen plan digest declared by release/v0.7.7. Product source and the release declaration do not move.

Change

Consume the exact frozen Changesets into the 0.7.7 changelogs. Keep all stable fixed-group packages at the version already declared by the cut.

Evidence

• Failure before the change: the release branch still contains 79 frozen Changesets and no 0.7.7 changelog entries.
• Success after the change: 79 Changesets are consumed into 11 formatted changelogs; the generated-only release diff validator passes with plan digest bbd074518aadb01d13be123c9759ef9aacf75e3a6c1056a0837ac8281d679059.
• Product/runtime behavior verified unchanged: pnpm review:pre --base release/v0.7.7 --head chore/release-v0.7.7 reports 0 findings and a clean merge.
• CI impact: no workflow or action changes.

The generated notes contain no triggerBehavior entry and no post-cut #9727 or #8653 work.

Scope

• No intended public API, product behavior, visual direction, or policy change.
• Product changes discovered during the work were removed or split.
• Public text and artifacts contain no private context.

Testing

• pnpm version-packages
• pnpm install --lockfile-only
• pnpm install --frozen-lockfile
• python3 ~/astryx/release/check_truncation.py <worktree>
• pnpm check:changesets
• node scripts/release/active-release.mjs validate-diff --base 0d72d92b5cbb2181f435f194f1dc2e512ed59754 --head 7bf58e05cb4d6adf11e044b47e4e098feff300f2

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
astryx	Ready	Preview	Nov 3, 2026 4:50pm UTC

[astracat-bot]

AI review status for this pull request.

Review status	Updated
🟢 Reviewed (for maintainers only)	Nov 3, 2026, 4:51 PM UTC

[astracat-bot]

This looks ready to merge: the 0.7.7 changelogs and the 79 deleted Changesets are exactly what the release generator produces from the frozen plan, and every fixed-group package stays at the declared 0.7.7, as the release versioning spec (AST-017 FR47) requires.

Before merging, record the editorial self-grade of the generated changelogs and draft release notes on this pull request, as step 4 of docs/release.md asks.

[Automated review]