Repository navigation
chore: release - #511
Open
moq-bot[bot] wants to merge 1 commit into
Open
chore: release#511moq-bot[bot] wants to merge 1 commit into
moq-bot[bot] wants to merge 1 commit into
Conversation
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — the complete release-plz commit: version bumps, changelog entries, dependency-requirement updates, and lockfile regeneration across the workspace.
rind0.3.2 → 0.4.0 (breaking) — driven by #510'schore!:title (deleting therind-instant-acmeworkspace crate, which waspublish = false).rind's own published API is unchanged, and the PR body already marks the bump "✓ API compatible changes", so consumers only need a version-requirement bump.- Adapter patch releases — all nine published adapters bump a patch and move their
rindrequirement to0.4.0;rind-str0m's cross-deps onrind-dimpl/rind-rcgentrack the new 0.9.4/0.14.4. No stalerind = "0.3.x"requirements remain anywhere in the workspace. rind-dartvsrind-pythonasymmetry is configured —rind-dartgets the dep bump but no release (its Dart package carries the version), whilerind-python0.1.3 isgit_only = truein.release-plz.toml, versioned by tag for the PyPI wheel flow.Cargo.lock— workspace versions in sync, plus the configureddependencies_update = truepicking up the semver-compatible transitivecrypto-bigint0.7.10 → 0.7.11 (pulled byelliptic-curve,rsa,rfc6979, etc.).- Changelogs — entries match the PR titles and PR #510's actual impact; the remaining
rind-instant-acmementions are immutable changelog history and a historical quest document, correctly left alone. Compare links target the tags release-plz creates on merge.
glm-5.3 | 𝕏
moq-bot
Bot
force-pushed
the
release-plz-2026-11-08T23-00-26Z
branch
2 times, most recently
from
November 9, 2026 06:25
c58729e to
8a65fc6
Compare
moq-bot
Bot
force-pushed
the
release-plz-2026-11-08T23-00-26Z
branch
12 times, most recently
from
November 10, 2026 01:31
4d68acc to
4d4de50
Compare
moq-bot
Bot
force-pushed
the
release-plz-2026-11-08T23-00-26Z
branch
from
November 10, 2026 01:43
4d4de50 to
483a254
Compare
This branch has not been deployed
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.

🤖 New release
rind: 0.3.2 -> 0.3.3rind-aws-lc-rs: 1.0.2 -> 1.0.3rind-rustls: 0.23.3 -> 0.24.0 (⚠ API breaking changes)rind-rcgen: 0.14.3 -> 0.15.0 (⚠ API breaking changes)rind-ring: 0.17.3 -> 0.18.0 (✓ API compatible changes)rind-str0m: 0.25.2 -> 0.26.0 (✓ API compatible changes)rind-python: 0.1.2 -> 0.2.0rind-jsonwebtoken: 11.0.3 -> 11.0.4rind-dimpl: 0.9.3 -> 0.9.4rind-object-store: 0.14.3 -> 0.14.4⚠
rind-rustlsbreaking changes⚠
rind-rcgenbreaking changesChangelog
rindrind-aws-lc-rsrind-rustlsrind-rcgenrind-ringrind-str0mrind-pythonrind-jsonwebtokenrind-dimplrind-object-storeThis PR was generated with release-plz.