chore: release v0.13.32#142
Open
paperbenni wants to merge 2 commits into
Open
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideRelease PR bumping the ins crate from v0.13.30 to v0.13.31 and recording the changes in the changelog (fixed test failure and removal of redundant tests). File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✅ Files skipped from review due to trivial changes (2)
📝 WalkthroughWalkthroughBumps crate version to 0.13.32 in Cargo.toml, updates packaging metadata ( ChangesVersion Release 0.13.32
Possibly Related PRs
Estimated Code Review Effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@Cargo.toml`:
- Line 3: Revert the manual change to the version line (version = "0.13.31") in
Cargo.toml and stop editing crate versions by hand; instead use the repository's
release tooling or script (e.g., the canonical release task/CLI used by this
repo such as cargo release or the project's release script) to bump versions so
automated metadata and CI remain in sync; locate the version entry in Cargo.toml
to undo the edit and run the established release command/workflow to perform the
version bump.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 52c91cbc-bcd6-4d69-b846-95d5bfbe5e62
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (2)
CHANGELOG.mdCargo.toml
| [package] | ||
| name = "ins" | ||
| version = "0.13.30" | ||
| version = "0.13.31" |
There was a problem hiding this comment.
Use the release tooling instead of editing Cargo.toml version directly.
Line 3 manually changes the crate version, which violates the repo rule and can desync automated release metadata.
As per coding guidelines, **/Cargo.toml: Use package managers for dependencies; do not hand-edit Cargo.toml versions.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@Cargo.toml` at line 3, Revert the manual change to the version line (version
= "0.13.31") in Cargo.toml and stop editing crate versions by hand; instead use
the repository's release tooling or script (e.g., the canonical release task/CLI
used by this repo such as cargo release or the project's release script) to bump
versions so automated metadata and CI remain in sync; locate the version entry
in Cargo.toml to undo the edit and run the established release command/workflow
to perform the version bump.
paperbenni
force-pushed
the
release-plz-2026-05-10T13-49-34Z
branch
from
df989f0 to
9c729cb
Compare
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
1 participant
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
ins: 0.13.31 -> 0.13.32Changelog
This PR was generated with release-plz.
Summary by CodeRabbit
Chore
Bug Fixes
Tests