Repository navigation
chore: release - #367
chore: release#367moq-bot[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the full diff of the release-plz output (16 files): version bumps, Cargo.lock, and changelog entries for all seven published crates, against git history since the previous release.
rind0.1.13 → 0.1.14 — changelog correctly records exactly the two commits landed since7a1f4d6:feat(proofs)#346 andci(build)#356; thequest/-only planning commit (#364) is correctly excluded.- Adapter bumps —
rind-{jsonwebtoken,rustls,dimpl,rcgen,object-store}0.1.13 → 0.1.14 andrind-ring0.1.12 → 0.1.13, each with itsrindpath dependency bumped to 0.1.14 and its changelog entry inserted below## [Unreleased]. Unpublishedrind-instant-acmegets only the dependency bump, as expected. Cargo.lock— package versions updated to match; nothing else touched.
glm-5.3-flash | 𝕏
d24656b to
80e060a
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the incremental delta since the prior pullfrog review (d24656b): release-plz regenerating the PR after the breaking AES-CTR change #360 landed on main.
rindbumped 0.1.14 → 0.2.0 — correct and required: #360 changes the public arity ofAesCtr::newandAesCtr::apply_keystream(flagged by cargo-semver-checks in the PR body as a semver violation), and 0.x semver permits breaking changes in a minor bump. The new changelog bullet*(cipher)* [**breaking**]correctly carries the breaking marker.- Adapter dependency bumps — all six adapters now require
rind0.2.0; their own versions stay at the already-recorded 0.1.14 bumps (none of them use or re-exportAesCtr, so their APIs are unaffected). Unpublishedrind-instant-acmegets only the dep bump, as expected. Cargo.lock— consistent with the 0.2.0 bump; the complete 0.2.0 changelog section still matches exactly the commits landed since7a1f4d6(verified against git history).
glm-5.3-flash | 𝕏
3890127 to
ffd8de7
Compare
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes
Reviewed the incremental delta since the prior pullfrog review (3890127): release-plz regenerating the PR after the breaking SHA-256 change #352 landed on main.
rind-ringandrind-rustlsbumped to 0.2.0 — justified: both consume the affected digest API (rind-ringexposes a publicdigestmodule wrappingrind::digest;rind-rustlswiresrind::digestinto its rustls hash provider), so #352 reaches them, and release-plz replaced their previous "updated local packages" entries with the inherited*(sha256)* [**breaking**]bullet. Thecargo-semver-checks-gated CI also confirms no adapter that stays at 0.1.14 needed a major bump.rind/CHANGELOG.md— adds the*(sha256)* [**breaking**]bullet under### Other; the 0.2.0 section now records exactly the eleven commits landed since7a1f4d6(#346, #356, #358, #359, #360, #361, #362, #365, #366, #363, #352), with thequest/-only planning commit (#369) correctly excluded. Verified against git history.Cargo.lock— consistent with all new versions (rind0.2.0,rind-ring/rind-rustls0.2.0, adapters 0.1.14); nothing else touched.
glm-5.3-flash | 𝕏
ffd8de7 to
d6d254e
Compare
|
Your OpenCode Go account is out of credit. Top it up, then re-trigger Pullfrog. OpenCode Go's response
|
a6466cc to
320978b
Compare
46e50b1 to
e127ea7
Compare
f5131ae to
ab0b030
Compare
47c9971 to
a93323f
Compare
a93323f to
4188fd8
Compare

🤖 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.