Skip to content

Conversation

@QaidVoid
Copy link
Member

@QaidVoid QaidVoid commented Jan 18, 2026

🤖 New release

  • soar-config: 0.3.0 -> 0.4.0 (⚠ API breaking changes)
  • soar-core: 0.11.1 -> 0.12.0 (⚠ API breaking changes)
  • soar-cli: 0.10.2 -> 0.10.3
  • soar-registry: 0.2.1 -> 0.2.2
  • soar-db: 0.3.1 -> 0.3.2
  • soar-package: 0.2.1 -> 0.2.2

soar-config breaking changes

--- failure enum_missing: pub enum removed or renamed ---

Description:
A publicly-visible enum cannot be imported by its prior path. A `pub use` may have been removed, or the enum itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.45.0/src/lints/enum_missing.ron

Failed in:
  enum soar_config::packages::UpdateSource, previously in file /tmp/.tmpPqCNTL/soar-config/src/packages.rs:245

--- failure struct_pub_field_missing: pub struct's pub field removed or renamed ---

Description:
A publicly-visible struct has at least one public field that is no longer available under its prior name. It may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.45.0/src/lints/struct_pub_field_missing.ron

Failed in:
  field update of struct PackageOptions, previously in file /tmp/.tmpPqCNTL/soar-config/src/packages.rs:219
  field update of struct ResolvedPackage, previously in file /tmp/.tmpPqCNTL/soar-config/src/packages.rs:309

soar-core breaking changes

--- failure function_missing: pub fn removed or renamed ---

Description:
A publicly-visible function cannot be imported by its prior path. A `pub use` may have been removed, or the function itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.45.0/src/lints/function_missing.ron

Failed in:
  function soar_core::package::remote_update::check_for_update, previously in file /tmp/.tmpPqCNTL/soar-core/src/package/remote_update.rs:38

--- failure struct_missing: pub struct removed or renamed ---

Description:
A publicly-visible struct cannot be imported by its prior path. A `pub use` may have been removed, or the struct itself may have been renamed or removed entirely.
        ref: https://doc.rust-lang.org/cargo/reference/semver.html#item-remove
       impl: https://github.com/obi1kenobi/cargo-semver-checks/tree/v0.45.0/src/lints/struct_missing.ron

Failed in:
  struct soar_core::package::remote_update::RemoteUpdate, previously in file /tmp/.tmpPqCNTL/soar-core/src/package/remote_update.rs:19
Changelog

soar-config

0.4.0 - 2026-01-18

⛰️ Features

  • (config) Add placeholder support and remove update field - (824d060)
  • (config) Make link_as optional and add glob support in binary maps - (c3945ee)

soar-core

0.12.0 - 2026-01-18

⛰️ Features

  • (config) Add placeholder support and remove update field - (824d060)

soar-cli

0.10.3 - 2026-01-18

⛰️ Features

  • (config) Add placeholder support and remove update field - (824d060)
  • (config) Make link_as optional and add glob support in binary maps - (c3945ee)

soar-registry

0.2.2 - 2026-01-18

⚙️ Miscellaneous Tasks

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

soar-db

0.3.2 - 2026-01-18

⚙️ Miscellaneous Tasks

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

soar-package

0.2.2 - 2026-01-18

⚙️ Miscellaneous Tasks

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


This PR was generated with release-plz.

Summary by CodeRabbit

  • New Features

    • Added placeholder support in configuration
    • Enabled glob pattern matching for binary maps
    • Made link_as field optional for improved flexibility
    • Removed deprecated update field from configuration
  • Chores

    • Updated internal dependencies across workspace packages

✏️ Tip: You can customize this high-level summary in your review settings.

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

coderabbitai bot commented Jan 18, 2026

📝 Walkthrough

Walkthrough

This pull request performs coordinated version bumps across the workspace's package ecosystem, updating package versions in individual crate manifests and the root workspace file, alongside corresponding changelog entries documenting feature additions and dependency updates.

Changes

Cohort / File(s) Summary
Root workspace version bumps
Cargo.toml, CHANGELOG.md
Root workspace Cargo.toml updated to reference new crate versions; root-level CHANGELOG.md enhanced with version 0.10.3 entry containing two config-related feature items.
soar-cli version and metadata
crates/soar-cli/Cargo.toml
Package version bumped from 0.10.2 to 0.10.3.
soar-config version, manifest, and changelog
crates/soar-config/Cargo.toml, crates/soar-config/CHANGELOG.md
Cargo.toml version updated from 0.3.0 to 0.4.0; CHANGELOG.md updated with version 0.4.0 entry featuring two config-enhancement items (placeholder support and glob support for binary maps).
soar-core version, manifest, and changelog
crates/soar-core/Cargo.toml, crates/soar-core/CHANGELOG.md
Cargo.toml version bumped from 0.11.1 to 0.12.0; CHANGELOG.md augmented with version 0.12.0 release entry documenting feature changes.
soar-db version, manifest, and changelog
crates/soar-db/Cargo.toml, crates/soar-db/CHANGELOG.md
Cargo.toml version incremented from 0.3.1 to 0.3.2; CHANGELOG.md updated with version 0.3.2 entry under Miscellaneous Tasks noting soar-registry dependency update.
soar-package version, manifest, and changelog
crates/soar-package/Cargo.toml, crates/soar-package/CHANGELOG.md
Cargo.toml version advanced from 0.2.1 to 0.2.2; CHANGELOG.md updated with version 0.2.2 entry documenting soar-config dependency update.
soar-registry version, manifest, and changelog
crates/soar-registry/Cargo.toml, crates/soar-registry/CHANGELOG.md
Cargo.toml version bumped from 0.2.1 to 0.2.2; CHANGELOG.md updated with version 0.2.2 entry noting soar-config dependency update.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • chore: release #146: Performs coordinated release and version-bump changes across the same crate manifests and changelogs (soar-config, soar-core, soar-db, soar-package, soar-registry, and root Cargo.toml).
  • chore: release #124: Automated release update applying the same pattern of Cargo.toml version bumps and CHANGELOG.md entries across multiple workspace crates.

Poem

🐰 A version bump hops through the fold,
From 0.3 to 0.4, new features bold!
Config placeholders dance with glee,
Glob support blooms wild and free—
Release notes sing in harmony! 🎉

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'chore: release' is generic and vague; it does not convey specific information about the version bumps, breaking changes, or features introduced in this multi-package release. Consider using a more descriptive title that highlights the major version changes, such as 'chore: release soar-config 0.4.0 and soar-core 0.12.0 with breaking changes' or similar.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
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.


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.

@codecov
Copy link

codecov bot commented Jan 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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-db/CHANGELOG.md`:
- Around line 2-6: The changelog entry for version [0.3.2] contains a
placeholder commit reference "0000000"; update the commit SHA in that entry so
both the visible link text and the URL in the markdown list item under the "###
⚙️ Miscellaneous Tasks" section are replaced with the real commit hash for this
release (i.e., change "([0000000](.../commit/0000000))" to the actual SHA in
both places).

In `@crates/soar-package/CHANGELOG.md`:
- Around line 2-6: The CHANGELOG entry for version 0.2.2 contains a placeholder
commit link "0000000" in the line "- Updated the following local packages:
soar-config - ([0000000](https://github.com/pkgforge/soar/commit/0000000))"; fix
this by replacing "0000000" with the actual commit hash for the soar-config
update or remove the Markdown link entirely (leaving just the package name and
optional commit short-hash) so the changelog does not contain a dead/placeholder
reference.

Comment on lines +2 to +6
## [0.3.2](https://github.com/pkgforge/soar/compare/soar-db-v0.3.1...soar-db-v0.3.2) - 2026-01-18

### ⚙️ Miscellaneous Tasks

- Updated the following local packages: soar-registry - ([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 the placeholder commit link before release.
The 0000000 commit hash will render as a dead link in the changelog. Please update it to the actual commit SHA for this release entry.

🤖 Prompt for AI Agents
In `@crates/soar-db/CHANGELOG.md` around lines 2 - 6, The changelog entry for
version [0.3.2] contains a placeholder commit reference "0000000"; update the
commit SHA in that entry so both the visible link text and the URL in the
markdown list item under the "### ⚙️ Miscellaneous Tasks" section are replaced
with the real commit hash for this release (i.e., change
"([0000000](.../commit/0000000))" to the actual SHA in both places).

Comment on lines +2 to +6
## [0.2.2](https://github.com/pkgforge/soar/compare/soar-package-v0.2.1...soar-package-v0.2.2) - 2026-01-18

### ⚙️ Miscellaneous Tasks

- Updated the following local packages: soar-config - ([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 the placeholder commit link.

0000000 is a broken placeholder; please replace with the real commit hash or drop the link to avoid a dead reference.

🧩 Suggested fix (remove placeholder link)
-- Updated the following local packages: soar-config - ([0000000](https://github.com/pkgforge/soar/commit/0000000))
+- Updated the following local packages: soar-config
📝 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.2.2](https://github.com/pkgforge/soar/compare/soar-package-v0.2.1...soar-package-v0.2.2) - 2026-01-18
### ⚙️ Miscellaneous Tasks
- Updated the following local packages: soar-config - ([0000000](https://github.com/pkgforge/soar/commit/0000000))
## [0.2.2](https://github.com/pkgforge/soar/compare/soar-package-v0.2.1...soar-package-v0.2.2) - 2026-01-18
### ⚙️ Miscellaneous Tasks
- Updated the following local packages: soar-config
🤖 Prompt for AI Agents
In `@crates/soar-package/CHANGELOG.md` around lines 2 - 6, The CHANGELOG entry for
version 0.2.2 contains a placeholder commit link "0000000" in the line "-
Updated the following local packages: soar-config -
([0000000](https://github.com/pkgforge/soar/commit/0000000))"; fix this by
replacing "0000000" with the actual commit hash for the soar-config update or
remove the Markdown link entirely (leaving just the package name and optional
commit short-hash) so the changelog does not contain a dead/placeholder
reference.

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.

2 participants