-
Notifications
You must be signed in to change notification settings - Fork 12
chore: release #155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
chore: release #155
Conversation
📝 WalkthroughWalkthroughCoordinated workspace release: package versions bumped across multiple crates, changelog entries added for each crate, and a new lock-related feature documented for Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@crates/soar-config/CHANGELOG.md`:
- Line 6: Replace the placeholder commit hash "0000000" in the CHANGELOG entry
for "soar-utils" with the actual commit SHA for the soar-utils update; locate
the line containing "soar-utils -
([0000000](https://github.com/pkgforge/soar/commit/0000000))" and update both
the visible hash and the URL to the real 7+ character hex commit SHA so the
changelog link resolves correctly.
🧹 Nitpick comments (1)
crates/soar-utils/Cargo.toml (1)
17-17: Moveserial_testfrom[dependencies]to[dev-dependencies].
serial_testis used only in test code (within#[cfg(test)]module in path.rs). Having it under[dependencies]means it compiles into production builds, adding unnecessary binary size and transitive dependencies.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
bbe5011 to
8a25a26
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
crates/soar-utils/Cargo.toml (1)
17-17: 🛠️ Refactor suggestion | 🟠 MajorMove
serial_testto[dev-dependencies]— it's only used in tests.
serial_testis exclusively used within the#[cfg(test)]module inpath.rsand has no other usages in the crate. Keeping it in[dependencies]causes it to ship as a transitive dependency to all consumers ofsoar-utils. Moving it to[dev-dependencies]eliminates this unnecessary dependency footprint for downstream crates.
🤖 Fix all issues with AI agents
In `@crates/soar-package/CHANGELOG.md`:
- Line 6: The changelog entry contains a placeholder commit hash "0000000" which
produces a broken link; update the entry in CHANGELOG.md by replacing the
placeholder commit hash/link with the real commit SHA for the dependency-only
update (or remove the link and leave a plain text reference) so the line "-
Updated the following local packages: soar-utils, soar-config - ([0000000])"
points to a valid commit; also verify other entries with "0000000" and correct
them similarly to avoid broken links (this addresses the release-plz generated
placeholder).
8a25a26 to
01411d3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@crates/soar-dl/CHANGELOG.md`:
- Line 6: The changelog entry contains a placeholder commit hash "0000000" for
the updated package "soar-utils"—replace that placeholder with the actual commit
SHA for the release and update the link so it points to
https://github.com/pkgforge/soar/commit/<actual-hash> (keep the same Markdown
format); ensure the replacement appears in the line that currently reads
"soar-utils - ([0000000](https://github.com/pkgforge/soar/commit/0000000))".
In `@crates/soar-utils/CHANGELOG.md`:
- Around line 2-7: Update the 0.4.0 changelog entry to mark the API break: add a
“[**breaking**]” marker to the 0.4.0 header or the specific bullet describing
the new UtilsError::Lock variant so readers know this release contains a
breaking change; reference the enum variant UtilsError::Lock and keep the
existing commit/PR metadata intact to match the repository’s changelog format.
|
|
||
| ### ⚙️ Miscellaneous Tasks | ||
|
|
||
| - Updated the following local packages: soar-utils - ([0000000](https://github.com/pkgforge/soar/commit/0000000)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Replace placeholder commit reference.
The commit hash 0000000 is a placeholder and should be replaced with the actual commit hash for this release.
🤖 Prompt for AI Agents
In `@crates/soar-dl/CHANGELOG.md` at line 6, The changelog entry contains a
placeholder commit hash "0000000" for the updated package "soar-utils"—replace
that placeholder with the actual commit SHA for the release and update the link
so it points to https://github.com/pkgforge/soar/commit/<actual-hash> (keep the
same Markdown format); ensure the replacement appears in the line that currently
reads "soar-utils -
([0000000](https://github.com/pkgforge/soar/commit/0000000))".
| ## [0.4.0](https://github.com/pkgforge/soar/compare/soar-utils-v0.3.0...soar-utils-v0.4.0) - 2026-02-12 | ||
|
|
||
| ### ⛰️ Features | ||
|
|
||
| - *(lock)* Add locking for concurrent process safety ([#154](https://github.com/pkgforge/soar/pull/154)) - ([e3bef6a](https://github.com/pkgforge/soar/commit/e3bef6a09435e83a524b719f7b9f3e0d133c6b64)) | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Mark the breaking change explicitly.
The PR objectives indicate that soar-utils 0.4.0 includes a breaking API change (a new enum variant UtilsError::Lock was added). The changelog entry should include a [**breaking**] marker to clearly indicate this, consistent with the pattern used elsewhere in the codebase (e.g., line 12).
📝 Suggested format
### ⛰️ Features
-- *(lock)* Add locking for concurrent process safety ([`#154`](https://github.com/pkgforge/soar/pull/154)) - ([e3bef6a](https://github.com/pkgforge/soar/commit/e3bef6a09435e83a524b719f7b9f3e0d133c6b64))
+- *(lock)* [**breaking**] Add locking for concurrent process safety ([`#154`](https://github.com/pkgforge/soar/pull/154)) - ([e3bef6a](https://github.com/pkgforge/soar/commit/e3bef6a09435e83a524b719f7b9f3e0d133c6b64))📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## [0.4.0](https://github.com/pkgforge/soar/compare/soar-utils-v0.3.0...soar-utils-v0.4.0) - 2026-02-12 | |
| ### ⛰️ Features | |
| - *(lock)* Add locking for concurrent process safety ([#154](https://github.com/pkgforge/soar/pull/154)) - ([e3bef6a](https://github.com/pkgforge/soar/commit/e3bef6a09435e83a524b719f7b9f3e0d133c6b64)) | |
| ## [0.4.0](https://github.com/pkgforge/soar/compare/soar-utils-v0.3.0...soar-utils-v0.4.0) - 2026-02-12 | |
| ### ⛰️ Features | |
| - *(lock)* [**breaking**] Add locking for concurrent process safety ([`#154`](https://github.com/pkgforge/soar/pull/154)) - ([e3bef6a](https://github.com/pkgforge/soar/commit/e3bef6a09435e83a524b719f7b9f3e0d133c6b64)) |
🤖 Prompt for AI Agents
In `@crates/soar-utils/CHANGELOG.md` around lines 2 - 7, Update the 0.4.0
changelog entry to mark the API break: add a “[**breaking**]” marker to the
0.4.0 header or the specific bullet describing the new UtilsError::Lock variant
so readers know this release contains a breaking change; reference the enum
variant UtilsError::Lock and keep the existing commit/PR metadata intact to
match the repository’s changelog format.
🤖 New release
soar-utils: 0.3.0 -> 0.4.0 (⚠ API breaking changes)soar-package: 0.2.3 -> 0.2.4 (✓ API compatible changes)soar-core: 0.13.0 -> 0.13.1 (✓ API compatible changes)soar-cli: 0.11.0 -> 0.11.1soar-config: 0.5.0 -> 0.5.1soar-dl: 0.8.0 -> 0.8.1soar-registry: 0.3.0 -> 0.3.1soar-db: 0.4.0 -> 0.4.1⚠
soar-utilsbreaking changesChangelog
soar-utilssoar-packagesoar-coresoar-clisoar-configsoar-dlsoar-registrysoar-dbThis PR was generated with release-plz.
Summary by CodeRabbit
New Features
Bug Fixes