Repository navigation
chore(release): ship rind as 0.2.1, not 0.3.0 - #457
Merged
Merged
Conversation
Since 0.2.0, rind's API changes are all compatible (cargo-semver-checks agrees). The release PR proposed 0.3.0 only because #440's `feat!` title touched files rind's package includes. release-plz keeps a hand-set version that is ahead of the published one. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Your OpenCode Go account is out of credit. Top it up, then re-trigger Pullfrog. OpenCode Go's response
|
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 6 minutes. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Merged
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.
The release PR (moq-dev/rind#424) proposed
rind0.2.0 → 0.3.0, though cargo-semver-checks rates rind's changes since 0.2.0 as API compatible. The bump came from moq-dev/rind#440'sfeat!title, which touched files rind's package includes.This sets rind's version to 0.2.1 by hand, along with the adapters' requirements on it. release-plz keeps a hand-set version that's ahead of the published one, so the regenerated release PR ships rind 0.2.1 beside the adapters' new upstream-matched versions. A 0.3.0 would make every rind 0.2 user re-pin, and would put two copies of rind in trees that use rind directly and through an adapter.
just checkpasses.🤖 Generated with Claude Code
(Written by Claude Opus 5.5)