Skip to content

Conversation

@QaidVoid
Copy link
Member

@QaidVoid QaidVoid commented Feb 11, 2026

🤖 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.1
  • soar-config: 0.5.0 -> 0.5.1
  • soar-dl: 0.8.0 -> 0.8.1
  • soar-registry: 0.3.0 -> 0.3.1
  • soar-db: 0.4.0 -> 0.4.1

soar-utils breaking changes

--- failure enum_variant_added: enum variant added on exhaustive enum ---

Description:
A publicly-visible enum without #[non_exhaustive] has a new variant.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#enum-variant-new
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.46.0/src/lints/enum_variant_added.ron

Failed in:
  variant UtilsError:Lock in /tmp/.tmpDyZ3uW/soar/crates/soar-utils/src/error.rs:383
Changelog

soar-utils

0.4.0 - 2026-02-12

⛰️ Features

  • (lock) Add locking for concurrent process safety (#154) - (e3bef6a)

soar-package

0.2.4 - 2026-02-12

🐛 Bug Fixes

  • (desktop) Preserve flags/args in Exec/TryExec - (465422d)

soar-core

0.13.1 - 2026-02-12

🐛 Bug Fixes

  • (substitute) Normalize package version - (c66c4c2)

soar-cli

0.11.1 - 2026-02-12

⛰️ Features

  • (lock) Add locking for concurrent process safety (#154) - (e3bef6a)

🐛 Bug Fixes

  • (substitute) Normalize package version - (c66c4c2)

soar-config

0.5.1 - 2026-02-12

⚙️ Miscellaneous Tasks

  • Updated the following local packages: soar-utils - (0000000)

soar-dl

0.8.1 - 2026-02-12

⚙️ Miscellaneous Tasks

  • Updated the following local packages: soar-utils - (0000000)

soar-registry

0.3.1 - 2026-02-12

⚙️ Miscellaneous Tasks

  • Updated the following local packages: soar-utils, soar-config, soar-dl - (0000000)

soar-db

0.4.1 - 2026-02-12

⚙️ Miscellaneous Tasks

  • Updated the following local packages: soar-registry - (0000000)


This PR was generated with release-plz.

Summary by CodeRabbit

  • New Features

    • Added lock mechanism for concurrent process safety.
  • Bug Fixes

    • Fixed package version normalization.

@QaidVoid QaidVoid added the release New Release (Probably Automated) label Feb 11, 2026
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 11, 2026

📝 Walkthrough

Walkthrough

Coordinated workspace release: package versions bumped across multiple crates, changelog entries added for each crate, and a new lock-related feature documented for crates/soar-utils (0.4.0). No public API signatures or code-level behavior changes in this diff.

Changes

Cohort / File(s) Summary
Workspace top-level
Cargo.toml, CHANGELOG.md
Added workspace release 0.11.1 to top-level CHANGELOG; updated workspace dependency versions.
soar-utils
crates/soar-utils/Cargo.toml, crates/soar-utils/CHANGELOG.md
Bumped 0.3.0 → 0.4.0; CHANGELOG documents a lock for concurrent process safety and updates to prior entry.
soar-cli
crates/soar-cli/Cargo.toml
Bumped package version 0.11.0 → 0.11.1 (metadata only).
soar-config
crates/soar-config/Cargo.toml, crates/soar-config/CHANGELOG.md
Bumped 0.5.0 → 0.5.1 and added changelog entry (misc update).
soar-core
crates/soar-core/Cargo.toml, crates/soar-core/CHANGELOG.md
Bumped 0.13.0 → 0.13.1 and added changelog entry (version normalization note).
soar-db
crates/soar-db/Cargo.toml, crates/soar-db/CHANGELOG.md
Bumped 0.4.0 → 0.4.1 and added changelog entry (misc update).
soar-dl
crates/soar-dl/Cargo.toml, crates/soar-dl/CHANGELOG.md
Bumped 0.8.0 → 0.8.1 and added changelog entry (misc update).
soar-package
crates/soar-package/Cargo.toml, crates/soar-package/CHANGELOG.md
Bumped 0.2.3 → 0.2.4 and added changelog entry (bugfix note).
soar-registry
crates/soar-registry/Cargo.toml, crates/soar-registry/CHANGELOG.md
Bumped 0.3.0 → 0.3.1 and added changelog entry (misc update).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

Poem

🐰 I hopped through crates and nudged each tag,

A tiny lock to stop the snag,
Versions climbed, the changelogs sing,
I twitched my nose — release bells ring,
Carrot time! 🥕🔐

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'chore: release' accurately describes the pull request as an automated release that updates package versions and changelogs across multiple crates.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch release-plz-2026-02-11T16-28-03Z

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Contributor

@coderabbitai coderabbitai bot left a 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: Move serial_test from [dependencies] to [dev-dependencies].

serial_test is 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
Copy link

codecov bot commented Feb 11, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@QaidVoid QaidVoid force-pushed the release-plz-2026-02-11T16-28-03Z branch from bbe5011 to 8a25a26 Compare February 12, 2026 11:45
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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 | 🟠 Major

Move serial_test to [dev-dependencies] — it's only used in tests.

serial_test is exclusively used within the #[cfg(test)] module in path.rs and has no other usages in the crate. Keeping it in [dependencies] causes it to ship as a transitive dependency to all consumers of soar-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).

@QaidVoid QaidVoid force-pushed the release-plz-2026-02-11T16-28-03Z branch from 8a25a26 to 01411d3 Compare February 12, 2026 17:05
Copy link
Contributor

@coderabbitai coderabbitai bot left a 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))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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))".

Comment on lines +2 to +7
## [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))

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

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.

Suggested change
## [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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release New Release (Probably Automated)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant