[stmh]

🤖 I have created a release beep boop

0.5.0

0.5.0 (2026-11-09)

Features

• add conformance checks for OAuthStore implementations (a5262a0)
• routes: expose each endpoint as a MethodRouter so hosts can layer one (a5262a0)

grantry-redis: 0.1.0

0.1.0 (2026-11-09)

Features

• add grantry-redis, a Redis / Valkey OAuthStore (a56ae2e)

Dependencies

• The following workspace dependencies were updated
  • dependencies
    • grantry bumped from 0.4 to 0.5.0
  • dev-dependencies
    • grantry bumped from 0.4 to 0.5.0

---

This PR was generated with Release Please. See documentation.

[claude]

This release downgrades grantry from 0.4.0 to 0.2.0. The same change appears in .release-please-manifest.json, the grantry/CHANGELOG.md entry (whose compare link is v0.4.0...v0.2.0), and the grantry dependency in grantry-redis/Cargo.toml ("bumped from 0.4 to 0.2.0").

Versions 0.2.0 through 0.4.0 already exist, so publishing 0.2.0 would fail or clash with the existing release. The cause looks like a release-as: 0.2.0 override, or a Release-As: 0.2.0 footer in the release 0.2.0 commit (fb23cb4), applied to both packages. The grantry version should move forward from 0.4.0. Only grantry-redis, going from 0.1.0 to 0.2.0, is a valid bump here.

Fix the release-as override and regenerate this PR.

[stmh]

🤖 Created releases:

• v0.5.0
• grantry-redis-v0.1.0

🌻