Repository navigation
chore: release - #421
chore: release#421moq-bot[bot] wants to merge 1 commit into
Conversation
|
Your OpenCode Go account is out of credit. Top it up, then re-trigger Pullfrog. OpenCode Go's response
|
kixelated
left a comment
There was a problem hiding this comment.
Automated review by review (OpenAI)
Reviewed head: 9b93359
No actionable findings in this release diff. The seven published crate versions agree with their lockfile entries, and the adapters' versioned rind dependencies all move to 0.2.0. The unpublished workspace members remain path-compatible. rind-rcgen's 0.1.14 bump does not expose the newly versioned rind types through its public API. The additional lockfile patch updates are consistent with .release-plz.toml enabling dependency updates.
Direction: no changes requested based on this inspection. This is a comment-only review, not approval to merge or publish.
Verification limits: GitHub-only static review of the 16 changed files and relevant workspace/public-API context. I did not build, run tests, run package/publish checks, audit the upstream dependency patch releases, or re-review the implementation changes already on main. The head's returned workflow list contained only the expected skipped Queue run, with no commit statuses; this is not evidence of a passing build. PR state, head, and existing reviews were rechecked immediately before submission.

🤖 New release
rind: 0.1.13 -> 0.2.0 (⚠ API breaking changes)rind-jsonwebtoken: 0.1.13 -> 0.2.0 (✓ API compatible changes)rind-rustls: 0.1.13 -> 0.2.0 (✓ API compatible changes)rind-dimpl: 0.1.13 -> 0.2.0 (✓ API compatible changes)rind-object-store: 0.1.13 -> 0.2.0 (✓ API compatible changes)rind-ring: 0.1.12 -> 0.2.0 (✓ API compatible changes)rind-rcgen: 0.1.13 -> 0.1.14⚠
rindbreaking changesChangelog
rindrind-jsonwebtokenrind-rustlsrind-dimplrind-object-storerind-ringrind-rcgenThis PR was generated with release-plz.