[Vivswan]

What this specifies

before: "last-release-sha": "046adf3b24454f26f569850630809bcf481f8b84"
after:  "last-release-sha": "56d949aec56aaaf95ed0cd324b02f47d0f76ed97"

before: the anchor rides inside release PR #58 -> its squash merge lands the boundary on main
after:  the anchor is its own PR against main, off the release PR branch

How

• One line in release-please-config.json moves release-please's boundary to main's tip at the time of writing.
• The commit is the release pipeline's own, lifted unchanged from the release PR branch.

Proof

• boundary-check fails on main with this config: NEWER than 046adf3b, exit 1. The unchanged config passes the same checker.
• That check is skipped on this PR and runs on main, where its red fails all-green and skips post-green and release.

Technical details

• Do not merge as it stands. It needs a matching change to the boundary policy in .github/scripts/release-pipeline/anchor.ts first.
• Changelog effect: with the boundary at main's tip, release-please sees nothing to release, so the 3.0.0 release PR empties or closes.
• Release PR chore(main): release 3.0.0 #58: the same commit is removed from its branch; anchor-check there expects it, and the next release-please refresh adds it back.
• Files: release-please-config.json.

[github-actions]

File size check

0 over a hard cap (fails), 6 warning(s).

File	Size	Tier	Cap
src/engine/diff.ts:56	11 comment lines	warn	10
src/github/api-error.ts:9	11 comment lines	warn	10
src/problem.ts:73	18 comment lines	warn	10
src/sections/contract/errors.ts:13	11 comment lines	warn	10
src/sections/contract/module.ts:55	12 comment lines	warn	10
src/sections/shared/list/decl.ts:265	14 comment lines	warn	10

Split the file, wrap the line, shorten or exempt the comment, or list the path in .file-size-allow.local with a # reason.

5 managed file(s) skipped; repo-platform owns them.

[github-actions]

Member shape check

1 finding(s).

File	Line	Rule
test/sections/contract/validate-hook.test.ts	80	all-or-none

Add the blank lines, make the comment one line directly above the item, comment every field or none, or list the path in .member-shape-allow.local with a # reason.

4 generated file(s) skipped.

[Vivswan]

Closed: the anchor commit is back on the release PR branch (#58), where the release pipeline lands it.

[Copilot]

🟡 Changes recommended

The new release anchor is rejected by the unchanged boundary policy, causing main to fail boundary-check and blocking publishing and releases despite green PR checks.

1 open issue

• Keep the release boundary unchanged until its policy update lands · New

What changed in this PR

This PR separates the release boundary update from release PR #58, moving release-please's history cutoff to the main tip recorded when this PR was prepared.

Changes:

• Updates last-release-sha from 046adf3b... to 56d949ae....
• Leaves the release pipeline and boundary validation policy unchanged.

File	Description
release-please-config.json	Advances the commit boundary used by release-please.

_{Review effort: Balanced}