Skip to content

ci: start release-please after v0.4.0 for the moved grantry package - #39

Merged
stmh merged 1 commit into
mainfrom
fix/release-please-base
Nov 9, 2026
Merged

stmh merged 1 commit into
mainfrom
fix/release-please-base

Conversation

@stmh

@stmh stmh commented Nov 9, 2026

Copy link
Copy Markdown
Member

Release PR #38 proposes grantry 0.2.0 and grantry-redis 0.2.0. It should be grantry 0.5.0 and grantry-redis 0.1.0.

Moving grantry from . to grantry/ (#37) broke release-please's link to the v0.4.0 release. It scanned all of history and applied the Release-As: 0.2.0 footer of fb23cb4 to both crates.

This sets last-release-sha to a06c6c1, the last commit before #37, for both packages. Release-please then only reads the commits since v0.4.0 and takes the versions from the manifest.

After merging, the release PR (#38) should update to grantry 0.5.0 and grantry-redis 0.1.0. Remove last-release-sha again after that release.

Moving grantry from . to grantry/ lost the link to the v0.4.0 release, so
release-please read all of history and applied the old Release-As: 0.2.0
footer of fb23cb4 to both crates. last-release-sha limits it to the commits
since v0.4.0. Remove it once grantry 0.5.0 and grantry-redis 0.1.0 are out.
@claude

claude Bot commented Nov 9, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@stmh
stmh merged commit b515535 into main Nov 9, 2026
4 checks passed
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