Repository navigation
docs: point to grantry-redis from the crate docs - #41
Merged
Merged
Conversation
Code reviewNo issues found. Checked for bugs and CLAUDE.md compliance. |
The features below landed in src/ before grantry moved to grantry/, so release-please did not attribute them to the grantry package. They are repeated here, in release-please's multi-change format, so grantry releases and its changelog lists them. feat: add conformance checks for OAuthStore implementations feat(routes): expose each endpoint as a MethodRouter so hosts can layer one
stmh
force-pushed
the
fix/release-grantry-0.5
branch
from
November 9, 2026 14:43
a406700 to
a522248
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After #40, release-please still skipped grantry: "Setting version for grantry from release-as configuration", then "No user facing commits found ... skipping". The only commit under
grantry/since v0.4.0 is therefactor:move. A hidden type (refactor, docs, chore, ci) doesn't count, andrelease-asis only consulted after that check. Another project hit the same behavior: elee1766/acphost#145.This commit touches
grantry/and repeats the two grantry features in release-please's documented multi-change commit format. The features landed insrc/before the move, so release-please never attributed them to grantry. That gives grantry user-facing commits, so it releases (0.5.0 via the existingrelease-as), and its changelog lists the real features. Merge with rebase, so the commit message reachesmainunchanged.Expected in #38: grantry 0.5.0 (conformance checks, per-endpoint routes), and grantry-redis 0.1.0 requiring
grantry = "0.5".