fix: anchor release-please to v3.0.0 release commit

[nieblara]

Summary

Fixes the release-please version regression from 3.0.0 to 0.12.1.

Root cause: The v3.0.0 git tag is permanently burned by GitHub's immutable releases feature. Without the tag, release-please walks all 698 commits from the beginning of the repo and computes 0.12.x instead of 3.0.1.

Fix: Add last-release-sha pointing to the 3.0.0 release commit (caa1fd2) so release-please only considers commits after that point. No change to release-type.

After this merges, release-please should correctly create a 3.0.1 release PR.

Made with Cursor

---

Note

Low Risk
Config-only change affecting automated release version calculation; no runtime, security, or data-path code is modified.

Overview
Anchors release-please history by adding last-release-sha to release-please-config.json, so version calculation starts from the v3.0.0 release commit instead of scanning the full repo history.

This prevents release-please from regressing the computed version (e.g., to 0.12.x) when the v3.0.0 tag is unavailable, and should restore correct 3.x release PR generation.

^{Reviewed by Cursor Bugbot for commit 8287853. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 8287853. Configure here.}

[cursor]

Wrong file for last-release-sha configuration option

High Severity

The last-release-sha property is not a valid option inside release-please-config.json package configuration. According to release-please documentation, last-release-sha belongs in .release-please-manifest.json (alongside version entries), not in the config file. The config file equivalent for anchoring commit history is bootstrap-sha, which goes at the top level of release-please-config.json, not nested inside a package. Since this property is unrecognized here, it will be silently ignored, and release-please will continue walking all commits and computing the wrong version — defeating the entire purpose of this PR.

 

^{Reviewed by Cursor Bugbot for commit 8287853. Configure here.}