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/.tmpGOXRlR/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/.tmpGOXRlR/soar-config/src/packages.rs:219
  field update of struct ResolvedPackage, previously in file /tmp/.tmpGOXRlR/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/.tmpGOXRlR/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/.tmpGOXRlR/soar-core/src/package/remote_update.rs:19
Changelog

soar-config

0.4.0 - 2026-01-21

⛰️ 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-21

⛰️ Features

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

soar-cli

0.10.3 - 2026-01-21

⛰️ 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-21

⚙️ Miscellaneous Tasks

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

soar-db

0.3.2 - 2026-01-21

⚙️ Miscellaneous Tasks

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

soar-package

0.2.2 - 2026-01-21

⚙️ 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 for configuration
    • Introduced glob pattern matching for binary maps
    • Made link_as field optional in configuration
  • Chores

    • Released version 0.10.3 with dependency updates

✏️ 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

Coordinated release update: bump crate versions across the workspace and add matching changelog entries documenting config-related features and minor dependency notes.

Changes

Cohort / File(s) Summary
Root workspace
Cargo.toml, CHANGELOG.md
Root workspace Cargo.toml updated to reference new versions; CHANGELOG.md added 0.10.3 entry with two config-related feature bullets.
soar-cli
crates/soar-cli/Cargo.toml
Package version bumped 0.10.20.10.3.
soar-config
crates/soar-config/Cargo.toml, crates/soar-config/CHANGELOG.md
Version bumped 0.3.00.4.0; CHANGELOG.md added 0.4.0 entry listing placeholder support, removal of update field, optional link_as, and glob support for binary maps.
soar-core
crates/soar-core/Cargo.toml, crates/soar-core/CHANGELOG.md
Version bumped 0.11.10.12.0; CHANGELOG.md added 0.12.0 entry noting config placeholder support and removal of update.
soar-db
crates/soar-db/Cargo.toml, crates/soar-db/CHANGELOG.md
Version bumped 0.3.10.3.2; CHANGELOG.md added 0.3.2 entry with miscellaneous note about local package updates.
soar-package
crates/soar-package/Cargo.toml, crates/soar-package/CHANGELOG.md
Version bumped 0.2.10.2.2; CHANGELOG.md added 0.2.2 entry noting local soar-config update.
soar-registry
crates/soar-registry/Cargo.toml, crates/soar-registry/CHANGELOG.md
Version bumped 0.2.10.2.2; CHANGELOG.md added 0.2.2 entry noting local soar-config update and removed the prior 0.2.1 bullet.

Sequence Diagram(s)

(Skipped — changes are release metadata and changelog entries only.)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • chore: release #146: Coordinated release/version-bump changes across the same crate manifests and changelogs.
  • chore: release #124: Automated release updates touching the same Cargo.toml version fields and CHANGELOG.md entries.
  • chore: release #139: Related config API changes (removal of update field and config placeholder/link_as updates) referenced in changelogs.

Poem

🐇 I hopped through crates and bumped each tag,
Version carrots piled in my bag.
Placeholders sprout, glob petals unfurl,
Changelogs shimmer — a release-y whirl! 🎉

🚥 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 summarizes the primary purpose of the PR, which is a coordinated release with version bumps across multiple workspace packages.
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.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.

@QaidVoid QaidVoid force-pushed the release-plz-2026-01-18T05-01-19Z branch from 48e3776 to 0b21158 Compare January 21, 2026 17:04
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-registry/CHANGELOG.md`:
- Around line 2-6: The CHANGELOG entry contains a placeholder commit link
"([0000000](https://github.com/pkgforge/soar/commit/0000000))" that must be
corrected; open the line containing "Updated the following local packages:
soar-config - ([0000000]" and either replace 0000000 with the actual commit hash
for the soar-config update or remove the entire parenthetical link so it reads
"soar-config" (or "soar-config - <commit-hash>" if you prefer bare hash), then
save the CHANGELOG.md.
♻️ Duplicate comments (1)
crates/soar-package/CHANGELOG.md (1)

2-6: Replace the placeholder commit link.

Line 6 still points to 0000000, which is a dead reference. Please replace it with the real hash or drop the link.

🧩 Proposed 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

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

### ⚙️ 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.

Line 6 points to 0000000, which is a dead reference. Please replace with the real hash or remove the link.

🧩 Proposed 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-registry-v0.2.1...soar-registry-v0.2.2) - 2026-01-21
### ⚙️ 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-registry-v0.2.1...soar-registry-v0.2.2) - 2026-01-21
### ⚙️ Miscellaneous Tasks
- Updated the following local packages: soar-config
🤖 Prompt for AI Agents
In `@crates/soar-registry/CHANGELOG.md` around lines 2 - 6, The CHANGELOG entry
contains a placeholder commit link
"([0000000](https://github.com/pkgforge/soar/commit/0000000))" that must be
corrected; open the line containing "Updated the following local packages:
soar-config - ([0000000]" and either replace 0000000 with the actual commit hash
for the soar-config update or remove the entire parenthetical link so it reads
"soar-config" (or "soar-config - <commit-hash>" if you prefer bare hash), then
save the CHANGELOG.md.

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