chore: release #139
chore: release #139
Conversation
📝 WalkthroughWalkthroughThis PR adds new release changelog entries, bumps crate versions across multiple crates, updates workspace dependency versions in the root Changes
Sequence Diagram(s)(omitted — changes are manifest/changelog and do not introduce new multi-component control flow) Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ 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. Comment |
![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
🤖 Fix all issues with AI agents
In @crates/soar-utils/CHANGELOG.md:
- Around line 2-7: Replace the placeholder commit hash "0000000" in the
CHANGELOG entry under the 0.1.2 heading with the actual commit SHA produced by
the release automation; locate the line containing "- Update Cargo.toml
dependencies - ([0000000](...))" and update the link text and URL fragment to
use the real commit hash so the compare/commit link points to the correct
commit.
🧹 Nitpick comments (1)
crates/soar-db/CHANGELOG.md (1)
2-7: Consider adding explicit breaking change documentation.The 0.3.0 entry documents refactors but doesn't explicitly mention the API-breaking changes identified by cargo-semver-checks: removal of
version_upstreamfield fromNewPackage,PackageListing, andPackagestructs, plus schema symbol removals. Downstream consumers would benefit from explicit "⚠️ Breaking Changes" documentation.This may be a limitation of the auto-generated changelog from conventional commits.
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (17)
CHANGELOG.mdCargo.tomlcrates/soar-cli/Cargo.tomlcrates/soar-config/CHANGELOG.mdcrates/soar-config/Cargo.tomlcrates/soar-core/CHANGELOG.mdcrates/soar-core/Cargo.tomlcrates/soar-db/CHANGELOG.mdcrates/soar-db/Cargo.tomlcrates/soar-dl/CHANGELOG.mdcrates/soar-dl/Cargo.tomlcrates/soar-package/CHANGELOG.mdcrates/soar-package/Cargo.tomlcrates/soar-registry/CHANGELOG.mdcrates/soar-registry/Cargo.tomlcrates/soar-utils/CHANGELOG.mdcrates/soar-utils/Cargo.toml
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2026-01-09T16:14:13.649Z
Learnt from: QaidVoid
Repo: pkgforge/soar PR: 137
File: crates/soar-cli/src/apply.rs:149-153
Timestamp: 2026-01-09T16:14:13.649Z
Learning: In crates/soar-cli/src/apply.rs, for URL packages, passing non-installed records (is_installed=false) as existing_install is intentional. The query filters by repo_name, pkg_name, and pkg_id, ensuring the record is for the same package. This allows resuming partial installs and preserving settings (portable paths, profile) from previous installs.
Applied to files:
crates/soar-package/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: coverage
- GitHub Check: test
🔇 Additional comments (15)
crates/soar-package/CHANGELOG.md (1)
2-11: LGTM!The changelog entry for version 0.2.0 is well-formatted and documents the features and refactors. The version bump to 0.2.0 correctly reflects the breaking API change (parameter count change to
integrate_package).crates/soar-dl/Cargo.toml (1)
3-3: LGTM!Patch version bump to 0.7.2 is appropriate for an API-compatible release.
crates/soar-package/Cargo.toml (1)
3-3: LGTM!Version bump to 0.2.0 correctly reflects the breaking API change (
integrate_packageparameter count changed from 7 to 8).crates/soar-core/CHANGELOG.md (1)
2-14: LGTM!The changelog entry for version 0.10.1 is comprehensive and well-documented. The patch version bump correctly indicates API-compatible changes.
crates/soar-utils/Cargo.toml (1)
3-3: LGTM!Patch version bump to 0.1.2 is appropriate for an API-compatible release.
crates/soar-dl/CHANGELOG.md (1)
2-10: LGTM!The changelog entry for version 0.7.2 is properly formatted and documents the new feature and refactor.
crates/soar-db/Cargo.toml (1)
3-3: LGTM!Version bump to 0.3.0 correctly reflects the breaking API changes (removal of
version_upstreamfield from schema and structs).crates/soar-core/Cargo.toml (1)
3-3: LGTM! Patch version bump is appropriate.The version bump from 0.10.0 to 0.10.1 correctly reflects an API-compatible release as documented in the PR objectives.
crates/soar-registry/CHANGELOG.md (1)
2-12: Document breaking changes in CHANGELOG.The version bump to 0.2.0 correctly signals breaking changes and is semver-compliant for 0.x releases. However, the CHANGELOG entry lacks explicit documentation of the breaking changes. Add a "Breaking Changes" section documenting the RemotePackage field removals (rank, pkg, version_upstream) using the existing
[**breaking**]notation pattern found in other parts of the CHANGELOG. This ensures consumers of the library are explicitly aware of the breaking API changes.⛔ Skipped due to learnings
Learnt from: QaidVoid Repo: pkgforge/soar PR: 137 File: crates/soar-cli/src/apply.rs:149-153 Timestamp: 2026-01-09T16:14:13.649Z Learning: In crates/soar-cli/src/apply.rs, for URL packages, passing non-installed records (is_installed=false) as existing_install is intentional. The query filters by repo_name, pkg_name, and pkg_id, ensuring the record is for the same package. This allows resuming partial installs and preserving settings (portable paths, profile) from previous installs.crates/soar-registry/Cargo.toml (1)
3-3: Version bump looks correct.The bump from 0.1.1 to 0.2.0 appropriately reflects the API-breaking changes (removal/renaming of public fields
rank,pkg,version_upstreamonRemotePackage) as reported by cargo-semver-checks.CHANGELOG.md (1)
2-14: Changelog entry is well-structured.The 0.9.2 release entry follows the established format with proper categorization (Features, Refactor), commit references, and PR links. The release date aligns with the PR creation date.
crates/soar-config/Cargo.toml (1)
3-3: Version bump is appropriate for the breaking changes.The 0.1.1 → 0.2.0 bump correctly reflects the API-breaking additions (new fields on
PackageOptionsandResolvedPackage, newConfigError::Customvariant) identified by cargo-semver-checks.crates/soar-config/CHANGELOG.md (1)
2-7: Changelog entry properly documents the new features.The 0.2.0 entry correctly documents the features that introduced the breaking changes (entrypoint option and remote URL package updates), which align with the new struct fields flagged by cargo-semver-checks.
Cargo.toml (1)
51-57: LGTM!The workspace dependency version bumps are consistent with the documented changes:
- Breaking API changes (soar-config, soar-db, soar-package, soar-registry) correctly receive minor version bumps following semver for 0.x versions.
- Compatible changes (soar-core, soar-dl, soar-utils) correctly receive patch version bumps.
crates/soar-cli/Cargo.toml (1)
3-3: LGTM!The patch version bump to 0.9.2 is appropriate for the CLI crate consuming updated workspace dependencies.
QaidVoid
force-pushed
the
release-plz-2026-01-13T13-51-31Z
branch
from
cd78fc8 to
853d98d
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@crates/soar-db/CHANGELOG.md`:
- Around line 2-8: Add a breaking-change entry to CHANGELOG.md for v0.3.0
documenting the cargo-semver-checks findings: state that the public struct field
version_upstream was removed (struct_pub_field_missing) from NewPackage,
PackageListing, and Package and that the version_upstream field is missing from
the schema metadata collections (soar_db::schema::metadata::packages and
::columns) (struct_missing); briefly note impact to downstream consumers (API
and DB schema changes) and recommend migration steps (update
callers/constructors and database schema or client code) so users know how to
adapt when upgrading from 0.2.0 to 0.3.0.
🧹 Nitpick comments (1)
crates/soar-config/CHANGELOG.md (1)
2-9: Consider documenting breaking changes in the changelog.This 0.x pre-release contains API additions (
ConfigError::Customvariant, new fields toPackageOptionsandResolvedPackage). While breaking changes are conventionally allowed in 0.x minor version bumps per semver, documenting them in a "BREAKING CHANGES" section would help users understand the upgrade path.
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (17)
CHANGELOG.mdCargo.tomlcrates/soar-cli/Cargo.tomlcrates/soar-config/CHANGELOG.mdcrates/soar-config/Cargo.tomlcrates/soar-core/CHANGELOG.mdcrates/soar-core/Cargo.tomlcrates/soar-db/CHANGELOG.mdcrates/soar-db/Cargo.tomlcrates/soar-dl/CHANGELOG.mdcrates/soar-dl/Cargo.tomlcrates/soar-package/CHANGELOG.mdcrates/soar-package/Cargo.tomlcrates/soar-registry/CHANGELOG.mdcrates/soar-registry/Cargo.tomlcrates/soar-utils/CHANGELOG.mdcrates/soar-utils/Cargo.toml
✅ Files skipped from review due to trivial changes (1)
- crates/soar-dl/Cargo.toml
🚧 Files skipped from review as they are similar to previous changes (10)
- crates/soar-db/Cargo.toml
- Cargo.toml
- crates/soar-package/CHANGELOG.md
- crates/soar-dl/CHANGELOG.md
- crates/soar-utils/Cargo.toml
- CHANGELOG.md
- crates/soar-registry/CHANGELOG.md
- crates/soar-package/Cargo.toml
- crates/soar-core/CHANGELOG.md
- crates/soar-config/Cargo.toml
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: test
- GitHub Check: coverage
🔇 Additional comments (3)
crates/soar-registry/Cargo.toml (1)
3-3: LGTM!The version bump from 0.1.1 to 0.2.0 correctly follows semver conventions for breaking changes in pre-1.0 versions. This aligns with the cargo-semver-checks report indicating
struct_pub_field_missingforRemotePackagefields (rank,pkg,version_upstream).crates/soar-core/Cargo.toml (1)
3-3: LGTM!The version bump from 0.10.0 to 0.11.0 correctly follows semantic versioning conventions for pre-1.0 crates, where minor version increments signal breaking changes. This aligns with the documented API breaking changes in the PR objectives.
crates/soar-cli/Cargo.toml (1)
3-3: LGTM!The patch version bump from 0.9.1 to 0.9.2 is appropriate for an API-compatible release. The internal workspace dependencies with breaking changes (soar-config, soar-core, soar-db, soar-registry, soar-package) are correctly managed via workspace versioning.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
crates/soar-db/CHANGELOG.md
Outdated
| ## [0.3.0](https://github.com/pkgforge/soar/compare/soar-db-v0.2.0...soar-db-v0.3.0) - 2026-01-15 | ||
|
|
||
| ### 🚜 Refactor | ||
|
|
||
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | ||
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) | ||
|
|
There was a problem hiding this comment.
Document the breaking changes in the changelog.
The version bump from 0.2.0 to 0.3.0 indicates a breaking change, but the changelog only lists refactors. According to the PR objectives, cargo-semver-checks detected breaking changes:
struct_missing:version_upstreammissing fromsoar_db::schema::metadata::packagesandcolumnsstruct_pub_field_missing:version_upstreamfield removed or renamed onNewPackage,PackageListing, andPackage
These breaking changes should be documented in the changelog to help users understand the impact when upgrading from 0.2.0 to 0.3.0.
📝 Suggested addition to the changelog
## [0.3.0](https://github.com/pkgforge/soar/compare/soar-db-v0.2.0...soar-db-v0.3.0) - 2026-01-15
+### ⚠️ Breaking Changes
+
+- *(schema)* Removed `version_upstream` field from `NewPackage`, `PackageListing`, and `Package` structs
+- *(schema)* Removed `version_upstream` from metadata schema tables
+
### 🚜 Refactor
- *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025))
- *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548))📝 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.3.0](https://github.com/pkgforge/soar/compare/soar-db-v0.2.0...soar-db-v0.3.0) - 2026-01-15 | |
| ### 🚜 Refactor | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | |
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) | |
| ## [0.3.0](https://github.com/pkgforge/soar/compare/soar-db-v0.2.0...soar-db-v0.3.0) - 2026-01-15 | |
| ### ⚠️ Breaking Changes | |
| - *(schema)* Removed `version_upstream` field from `NewPackage`, `PackageListing`, and `Package` structs | |
| - *(schema)* Removed `version_upstream` from metadata schema tables | |
| ### 🚜 Refactor | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | |
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) |
🤖 Prompt for AI Agents
In `@crates/soar-db/CHANGELOG.md` around lines 2 - 8, Add a breaking-change entry
to CHANGELOG.md for v0.3.0 documenting the cargo-semver-checks findings: state
that the public struct field version_upstream was removed
(struct_pub_field_missing) from NewPackage, PackageListing, and Package and that
the version_upstream field is missing from the schema metadata collections
(soar_db::schema::metadata::packages and ::columns) (struct_missing); briefly
note impact to downstream consumers (API and DB schema changes) and recommend
migration steps (update callers/constructors and database schema or client code)
so users know how to adapt when upgrading from 0.2.0 to 0.3.0.
853d98d to
e6b740b
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@crates/soar-registry/CHANGELOG.md`:
- Around line 2-11: Changelog for 0.2.0 must explicitly document the breaking
changes: add a "⚠️ Breaking changes" subsection under the 0.2.0 header that
lists the removed/renamed public fields on the RemotePackage struct—rank, pkg,
and version_upstream—explaining that these public fields are no longer available
(or were renamed) and instructing downstream consumers to update usages
accordingly; if there are direct replacements or new field names, include those
mappings and a short migration note (e.g., find-and-replace guidance or example
call sites) so consumers can adapt their code.
♻️ Duplicate comments (1)
crates/soar-db/CHANGELOG.md (1)
2-8: Document the breaking changes in the changelog.The version bump from 0.2.0 to 0.3.0 indicates breaking changes, but this was already flagged in a previous review. The breaking changes (removal of
version_upstreamfield fromNewPackage,PackageListing, andPackagestructs, and from schema metadata) should be documented.
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (17)
CHANGELOG.mdCargo.tomlcrates/soar-cli/Cargo.tomlcrates/soar-config/CHANGELOG.mdcrates/soar-config/Cargo.tomlcrates/soar-core/CHANGELOG.mdcrates/soar-core/Cargo.tomlcrates/soar-db/CHANGELOG.mdcrates/soar-db/Cargo.tomlcrates/soar-dl/CHANGELOG.mdcrates/soar-dl/Cargo.tomlcrates/soar-package/CHANGELOG.mdcrates/soar-package/Cargo.tomlcrates/soar-registry/CHANGELOG.mdcrates/soar-registry/Cargo.tomlcrates/soar-utils/CHANGELOG.mdcrates/soar-utils/Cargo.toml
🚧 Files skipped from review as they are similar to previous changes (10)
- crates/soar-core/CHANGELOG.md
- crates/soar-core/Cargo.toml
- crates/soar-config/Cargo.toml
- crates/soar-db/Cargo.toml
- crates/soar-utils/CHANGELOG.md
- crates/soar-cli/Cargo.toml
- crates/soar-registry/Cargo.toml
- crates/soar-package/Cargo.toml
- CHANGELOG.md
- Cargo.toml
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2026-01-09T16:14:21.516Z
Learnt from: QaidVoid
Repo: pkgforge/soar PR: 137
File: crates/soar-cli/src/apply.rs:149-153
Timestamp: 2026-01-09T16:14:21.516Z
Learning: In crates/soar-cli/src/apply.rs, for URL packages, passing non-installed records (is_installed=false) as existing_install is intentional. The query filters by repo_name, pkg_name, and pkg_id, ensuring the record is for the same package. This allows resuming partial installs and preserving settings (portable paths, profile) from previous installs.
Applied to files:
crates/soar-package/CHANGELOG.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: test
- GitHub Check: coverage
🔇 Additional comments (5)
crates/soar-dl/CHANGELOG.md (1)
2-10: LGTM!The changelog entry for 0.7.2 is consistent with a patch release (API compatible changes as confirmed by cargo-semver-checks). The documented feature and refactor entries are appropriate.
crates/soar-utils/Cargo.toml (1)
3-3: LGTM!The version bump to 0.2.0 correctly reflects the breaking API changes (function arity changes to
path::icons_dirandpath::desktop_dir) identified by cargo-semver-checks.crates/soar-dl/Cargo.toml (1)
3-3: LGTM!The patch version bump to 0.7.2 is appropriate for the API-compatible changes in this crate.
crates/soar-config/CHANGELOG.md (1)
2-10: LGTM! Well-formatted changelog entry.The 0.2.0 release entry is properly structured with clear feature descriptions and appropriate references. The version bump to 0.2.0 correctly reflects the breaking changes validated by cargo-semver-checks.
crates/soar-package/CHANGELOG.md (1)
2-13: LGTM! Changelog entry is complete and accurate.The 0.2.0 release entry properly documents both new features and refactoring work. The version bump appropriately reflects the breaking changes in the public API as validated by cargo-semver-checks.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
crates/soar-registry/CHANGELOG.md
Outdated
| ## [0.2.0](https://github.com/pkgforge/soar/compare/soar-registry-v0.1.1...soar-registry-v0.2.0) - 2026-01-15 | ||
|
|
||
| ### ⛰️ Features | ||
|
|
||
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | ||
|
|
||
| ### 🚜 Refactor | ||
|
|
||
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | ||
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) |
There was a problem hiding this comment.
Document the breaking changes in the changelog.
The version bump to 0.2.0 indicates breaking changes, but the changelog only lists features and refactors. According to PR objectives, cargo-semver-checks detected:
- Public fields removed/renamed on
RemotePackage:rank,pkg,version_upstream
These breaking changes should be documented to help downstream consumers understand the migration impact.
📝 Suggested addition
## [0.2.0](https://github.com/pkgforge/soar/compare/soar-registry-v0.1.1...soar-registry-v0.2.0) - 2026-01-15
+### ⚠️ Breaking Changes
+
+- *(RemotePackage)* Removed/renamed public fields: `rank`, `pkg`, `version_upstream`
+
### ⛰️ Features📝 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.2.0](https://github.com/pkgforge/soar/compare/soar-registry-v0.1.1...soar-registry-v0.2.0) - 2026-01-15 | |
| ### ⛰️ Features | |
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | |
| ### 🚜 Refactor | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | |
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) | |
| ## [0.2.0](https://github.com/pkgforge/soar/compare/soar-registry-v0.1.1...soar-registry-v0.2.0) - 2026-01-15 | |
| ### ⚠️ Breaking Changes | |
| - *(RemotePackage)* Removed/renamed public fields: `rank`, `pkg`, `version_upstream` | |
| ### ⛰️ Features | |
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | |
| ### 🚜 Refactor | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | |
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) |
🤖 Prompt for AI Agents
In `@crates/soar-registry/CHANGELOG.md` around lines 2 - 11, Changelog for 0.2.0
must explicitly document the breaking changes: add a "⚠️ Breaking changes"
subsection under the 0.2.0 header that lists the removed/renamed public fields
on the RemotePackage struct—rank, pkg, and version_upstream—explaining that
these public fields are no longer available (or were renamed) and instructing
downstream consumers to update usages accordingly; if there are direct
replacements or new field names, include those mappings and a short migration
note (e.g., find-and-replace guidance or example call sites) so consumers can
adapt their code.
6791b2f to
45e68f3
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@crates/soar-package/CHANGELOG.md`:
- Around line 2-14: Add a breaking-change note to the v0.2.0 changelog entry
explaining that the public function signatures integrate_package and
formats::common::integrate_package had their parameter count increased from 7 to
8; state that callers must update their call sites to pass the new argument
(describe what the new parameter represents), mention this is an intentional
semver-major-incompatible change when upgrading from 0.1.1 to 0.2.0, and provide
a short migration hint (e.g., example of the extra argument or where to find its
type) so downstream users can update implementations.
♻️ Duplicate comments (1)
crates/soar-db/CHANGELOG.md (1)
2-8: Document the breaking changes in the changelog.The version bump from 0.2.0 to 0.3.0 indicates breaking changes, but only refactors are listed. Per the PR objectives, cargo-semver-checks detected:
version_upstreamfield removed/renamed fromNewPackage,PackageListing, andPackagestructsversion_upstreammissing from schema metadataThis was already flagged in a previous review. Please add a breaking changes section to help users understand the migration impact.
🧹 Nitpick comments (1)
CHANGELOG.md (1)
9-9: Minor: "github" should be capitalized as "GitHub".The official spelling uses a capital "H". Since this is auto-generated from commit messages, consider updating the source commit message convention or accept as-is.
📝 Suggested fix
-- *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) +- *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (17)
CHANGELOG.mdCargo.tomlcrates/soar-cli/Cargo.tomlcrates/soar-config/CHANGELOG.mdcrates/soar-config/Cargo.tomlcrates/soar-core/CHANGELOG.mdcrates/soar-core/Cargo.tomlcrates/soar-db/CHANGELOG.mdcrates/soar-db/Cargo.tomlcrates/soar-dl/CHANGELOG.mdcrates/soar-dl/Cargo.tomlcrates/soar-package/CHANGELOG.mdcrates/soar-package/Cargo.tomlcrates/soar-registry/CHANGELOG.mdcrates/soar-registry/Cargo.tomlcrates/soar-utils/CHANGELOG.mdcrates/soar-utils/Cargo.toml
✅ Files skipped from review due to trivial changes (1)
- crates/soar-registry/Cargo.toml
🚧 Files skipped from review as they are similar to previous changes (6)
- crates/soar-registry/CHANGELOG.md
- crates/soar-config/Cargo.toml
- crates/soar-cli/Cargo.toml
- crates/soar-core/Cargo.toml
- crates/soar-utils/Cargo.toml
- crates/soar-db/Cargo.toml
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2026-01-15T14:54:00.116Z
Learnt from: QaidVoid
Repo: pkgforge/soar PR: 142
File: crates/soar-core/src/package/release_source.rs:146-183
Timestamp: 2026-01-15T14:54:00.116Z
Learning: In `crates/soar-core/src/package/release_source.rs`, the `version` parameter in release resolution is not equivalent to a git `tag`. The code correctly fetches all releases and uses normalization logic to match versions with tags, rather than assuming version can be directly passed as a tag parameter to fetch_releases.
Applied to files:
crates/soar-package/Cargo.tomlcrates/soar-dl/Cargo.tomlcrates/soar-core/CHANGELOG.md
📚 Learning: 2026-01-09T16:14:21.516Z
Learnt from: QaidVoid
Repo: pkgforge/soar PR: 137
File: crates/soar-cli/src/apply.rs:149-153
Timestamp: 2026-01-09T16:14:21.516Z
Learning: In crates/soar-cli/src/apply.rs, for URL packages, passing non-installed records (is_installed=false) as existing_install is intentional. The query filters by repo_name, pkg_name, and pkg_id, ensuring the record is for the same package. This allows resuming partial installs and preserving settings (portable paths, profile) from previous installs.
Applied to files:
CHANGELOG.mdcrates/soar-core/CHANGELOG.md
🪛 LanguageTool
crates/soar-config/CHANGELOG.md
[uncategorized] ~8-~8: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
crates/soar-package/CHANGELOG.md
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
CHANGELOG.md
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
crates/soar-core/CHANGELOG.md
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: test
- GitHub Check: lint
- GitHub Check: coverage
🔇 Additional comments (9)
crates/soar-package/Cargo.toml (1)
3-3: LGTM!The version bump from 0.1.1 to 0.2.0 is appropriate given the breaking API changes (increased parameter count for
integrate_package). The workspace dependency references are correctly maintained.CHANGELOG.md (1)
2-22: LGTM!The changelog entry for version 0.9.2 is well-structured with appropriate categorization of features, bug fixes, and refactors. The links to commits and PRs are properly formatted.
crates/soar-dl/Cargo.toml (1)
3-3: LGTM!The patch version bump from 0.7.1 to 0.7.2 is appropriate for API-compatible changes. Workspace dependency references are properly maintained.
crates/soar-utils/CHANGELOG.md (1)
2-10: LGTM!The new 0.2.0 changelog entry is well-structured with proper commit references and PR links. The formatting follows the established convention.
crates/soar-dl/CHANGELOG.md (1)
2-14: LGTM!The 0.7.2 changelog entry properly documents the feature addition, bug fix, and refactor with valid commit references.
crates/soar-config/CHANGELOG.md (1)
2-10: LGTM!The 0.2.0 changelog entry comprehensively documents the new features including system-wide package management, entrypoint options, GitHub/GitLab sources, hooks/build/sandbox support, and remote URL package updates.
Cargo.toml (2)
51-57: LGTM!Workspace dependency versions are correctly updated to match the new release versions. The version bumps align with the breaking changes indicated in the PR summary (0.x.y → 0.x+1.0 for API-breaking changes, patch bumps for compatible changes).
61-67: New workspace dependencies added.The new dependencies (
toml,toml_edit,tracing,ureq,url,xattr,zstd) are added with pinned versions which aids reproducibility. These appear to support the new features (TOML config handling, HTTP requests, extended attributes, compression).crates/soar-core/CHANGELOG.md (1)
2-21: LGTM!The 0.11.0 changelog entry thoroughly documents a significant release with multiple features (GHCR packages, system-wide management, landlock sandboxing, GitHub/GitLab sources), bug fixes, and refactors. All commit and PR references are properly linked.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
crates/soar-package/CHANGELOG.md
Outdated
| ## [0.2.0](https://github.com/pkgforge/soar/compare/soar-package-v0.1.1...soar-package-v0.2.0) - 2026-01-15 | ||
|
|
||
| ### ⛰️ Features | ||
|
|
||
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | ||
| - *(cli)* Add system-wide package management ([#141](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | ||
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | ||
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | ||
|
|
||
| ### 🚜 Refactor | ||
|
|
||
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | ||
|
|
There was a problem hiding this comment.
Document the breaking API change in the changelog.
According to the PR objectives, cargo-semver-checks detected a breaking change in this crate: integrate_package (and formats::common::integrate_package) parameter count increased from 7 to 8. This should be documented to help downstream users understand the migration impact when upgrading from 0.1.1 to 0.2.0.
📝 Suggested addition
## [0.2.0](https://github.com/pkgforge/soar/compare/soar-package-v0.1.1...soar-package-v0.2.0) - 2026-01-15
+### ⚠️ Breaking Changes
+
+- *(api)* `integrate_package` function signature changed - parameter count increased from 7 to 8
+
### ⛰️ Features📝 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.2.0](https://github.com/pkgforge/soar/compare/soar-package-v0.1.1...soar-package-v0.2.0) - 2026-01-15 | |
| ### ⛰️ Features | |
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | |
| - *(cli)* Add system-wide package management ([#141](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | |
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | |
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| ### 🚜 Refactor | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | |
| ## [0.2.0](https://github.com/pkgforge/soar/compare/soar-package-v0.1.1...soar-package-v0.2.0) - 2026-01-15 | |
| ### ⚠️ Breaking Changes | |
| - *(api)* `integrate_package` function signature changed - parameter count increased from 7 to 8 | |
| ### ⛰️ Features | |
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | |
| - *(cli)* Add system-wide package management ([`#141`](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | |
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | |
| - *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| ### 🚜 Refactor | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
🤖 Prompt for AI Agents
In `@crates/soar-package/CHANGELOG.md` around lines 2 - 14, Add a breaking-change
note to the v0.2.0 changelog entry explaining that the public function
signatures integrate_package and formats::common::integrate_package had their
parameter count increased from 7 to 8; state that callers must update their call
sites to pass the new argument (describe what the new parameter represents),
mention this is an intentional semver-major-incompatible change when upgrading
from 0.1.1 to 0.2.0, and provide a short migration hint (e.g., example of the
extra argument or where to find its type) so downstream users can update
implementations.
45e68f3 to
350c0de
Compare
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@crates/soar-core/CHANGELOG.md`:
- Around line 2-23: Add a new "⚠️ Breaking Changes" subsection under the 0.11.0
release heading in CHANGELOG.md that clearly lists the API-breaking changes: the
new constructible field UrlPackage.is_ghcr; the new InstallTarget fields
entrypoint, binaries, nested_extract, extract_root, hooks, build, and sandbox;
the addition of multiple SoarError enum variants; and the removal/renaming of
the public Package.version_upstream field, with a brief migration note for each
item so downstream users know what to change when upgrading from 0.10.0 to
0.11.0.
♻️ Duplicate comments (1)
crates/soar-package/CHANGELOG.md (1)
2-14: Document the breaking API change in the changelog.According to the PR objectives, cargo-semver-checks detected a breaking change:
integrate_package(andformats::common::integrate_package) parameter count increased from 7 to 8. This should be documented with a "⚠️ Breaking Changes" section to help downstream users understand the migration impact when upgrading from 0.1.1 to 0.2.0.📝 Suggested addition
## [0.2.0](https://github.com/pkgforge/soar/compare/soar-package-v0.1.1...soar-package-v0.2.0) - 2026-01-15 +### ⚠️ Breaking Changes + +- *(api)* `integrate_package` function signature changed - parameter count increased from 7 to 8 + ### ⛰️ Features
🧹 Nitpick comments (4)
CHANGELOG.md (1)
9-9: Nit: Consider capitalizing "GitHub/GitLab" per official branding.The official names use capital letters: "GitHub" and "GitLab".
📝 Suggested fix
-- *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) +- *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))crates/soar-package/CHANGELOG.md (1)
9-9: Consider capitalizing "GitHub" for brand consistency.The official platform name uses a capital "H".
📝 Suggested fix
-- *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) +- *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))crates/soar-config/CHANGELOG.md (1)
8-8: Consider capitalizing "GitHub" for brand consistency.The official platform name uses a capital "H".
📝 Suggested fix
-- *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) +- *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))crates/soar-core/CHANGELOG.md (1)
9-9: Consider capitalizing "GitHub" for brand consistency.The official platform name uses a capital "H".
📝 Suggested fix
-- *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) +- *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))
📜 Review details
Configuration used: defaults
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (17)
CHANGELOG.mdCargo.tomlcrates/soar-cli/Cargo.tomlcrates/soar-config/CHANGELOG.mdcrates/soar-config/Cargo.tomlcrates/soar-core/CHANGELOG.mdcrates/soar-core/Cargo.tomlcrates/soar-db/CHANGELOG.mdcrates/soar-db/Cargo.tomlcrates/soar-dl/CHANGELOG.mdcrates/soar-dl/Cargo.tomlcrates/soar-package/CHANGELOG.mdcrates/soar-package/Cargo.tomlcrates/soar-registry/CHANGELOG.mdcrates/soar-registry/Cargo.tomlcrates/soar-utils/CHANGELOG.mdcrates/soar-utils/Cargo.toml
✅ Files skipped from review due to trivial changes (1)
- crates/soar-utils/Cargo.toml
🚧 Files skipped from review as they are similar to previous changes (7)
- crates/soar-db/Cargo.toml
- crates/soar-config/Cargo.toml
- crates/soar-registry/CHANGELOG.md
- crates/soar-db/CHANGELOG.md
- Cargo.toml
- crates/soar-package/Cargo.toml
- crates/soar-utils/CHANGELOG.md
🧰 Additional context used
🧠 Learnings (2)
📚 Learning: 2026-01-15T14:54:00.116Z
Learnt from: QaidVoid
Repo: pkgforge/soar PR: 142
File: crates/soar-core/src/package/release_source.rs:146-183
Timestamp: 2026-01-15T14:54:00.116Z
Learning: In `crates/soar-core/src/package/release_source.rs`, the `version` parameter in release resolution is not equivalent to a git `tag`. The code correctly fetches all releases and uses normalization logic to match versions with tags, rather than assuming version can be directly passed as a tag parameter to fetch_releases.
Applied to files:
crates/soar-cli/Cargo.tomlcrates/soar-dl/Cargo.tomlcrates/soar-core/Cargo.tomlcrates/soar-registry/Cargo.toml
📚 Learning: 2026-01-09T16:14:21.516Z
Learnt from: QaidVoid
Repo: pkgforge/soar PR: 137
File: crates/soar-cli/src/apply.rs:149-153
Timestamp: 2026-01-09T16:14:21.516Z
Learning: In crates/soar-cli/src/apply.rs, for URL packages, passing non-installed records (is_installed=false) as existing_install is intentional. The query filters by repo_name, pkg_name, and pkg_id, ensuring the record is for the same package. This allows resuming partial installs and preserving settings (portable paths, profile) from previous installs.
Applied to files:
crates/soar-core/CHANGELOG.mdCHANGELOG.md
🪛 LanguageTool
crates/soar-core/CHANGELOG.md
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
CHANGELOG.md
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
crates/soar-config/CHANGELOG.md
[uncategorized] ~8-~8: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
crates/soar-package/CHANGELOG.md
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
- GitHub Check: lint
- GitHub Check: coverage
- GitHub Check: test
🔇 Additional comments (6)
crates/soar-dl/Cargo.toml (1)
3-3: LGTM!Patch version bump from 0.7.1 to 0.7.2 is appropriate for API-compatible changes as indicated by cargo-semver-checks.
crates/soar-cli/Cargo.toml (1)
3-3: LGTM!Patch version bump from 0.9.1 to 0.9.2 aligns with the release cycle. The workspace dependencies will correctly resolve to their updated versions.
crates/soar-registry/Cargo.toml (1)
3-3: LGTM!Minor version bump from 0.1.1 to 0.2.0 correctly reflects the breaking API changes (removed/renamed public fields on
RemotePackage) as reported by cargo-semver-checks.crates/soar-core/Cargo.toml (1)
3-3: LGTM!Minor version bump from 0.10.0 to 0.11.0 correctly reflects the breaking API changes (added struct fields, new enum variants, removed/renamed public fields) as reported by cargo-semver-checks.
CHANGELOG.md (1)
2-23: LGTM!The changelog entry is well-structured with appropriate sections for features, bug fixes, and refactors. All commit and PR links are properly formatted.
crates/soar-dl/CHANGELOG.md (1)
2-15: LGTM!The changelog entry for version 0.7.2 is well-structured and appropriate for a patch release with API-compatible changes.
✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.
crates/soar-config/CHANGELOG.md
Outdated
| ## [0.2.0](https://github.com/pkgforge/soar/compare/soar-config-v0.1.1...soar-config-v0.2.0) - 2026-01-15 | ||
|
|
||
| ### ⛰️ Features | ||
|
|
||
| - *(cli)* Add system-wide package management ([#141](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | ||
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | ||
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | ||
| - *(packages)* Add hooks, build commands, and sandbox support ([#140](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) | ||
| - *(update)* Allow updating remote URL packages ([#137](https://github.com/pkgforge/soar/pull/137)) - ([af13bb6](https://github.com/pkgforge/soar/commit/af13bb637c8c4c4a89cfdac451e39b105e7ee378)) | ||
|
|
There was a problem hiding this comment.
Document the breaking API changes in the changelog.
According to the PR objectives, cargo-semver-checks detected breaking changes in this crate: constructible struct added fields on PackageOptions and ResolvedPackage (github, gitlab, asset_pattern, include_prerelease, tag_pattern, version_command, entrypoint, binaries, nested_extract, extract_root, hooks, build, sandbox, update), and ConfigError::Custom enum variant was added. These should be documented with a "
📝 Suggested addition
## [0.2.0](https://github.com/pkgforge/soar/compare/soar-config-v0.1.1...soar-config-v0.2.0) - 2026-01-15
+### ⚠️ Breaking Changes
+
+- *(api)* `PackageOptions` and `ResolvedPackage` structs now include additional fields that must be initialized when constructing
+- *(api)* `ConfigError::Custom` enum variant added
+
### ⛰️ Features📝 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.2.0](https://github.com/pkgforge/soar/compare/soar-config-v0.1.1...soar-config-v0.2.0) - 2026-01-15 | |
| ### ⛰️ Features | |
| - *(cli)* Add system-wide package management ([#141](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | |
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | |
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| - *(packages)* Add hooks, build commands, and sandbox support ([#140](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) | |
| - *(update)* Allow updating remote URL packages ([#137](https://github.com/pkgforge/soar/pull/137)) - ([af13bb6](https://github.com/pkgforge/soar/commit/af13bb637c8c4c4a89cfdac451e39b105e7ee378)) | |
| ## [0.2.0](https://github.com/pkgforge/soar/compare/soar-config-v0.1.1...soar-config-v0.2.0) - 2026-01-15 | |
| ### ⚠️ Breaking Changes | |
| - *(api)* `PackageOptions` and `ResolvedPackage` structs now include additional fields that must be initialized when constructing | |
| - *(api)* `ConfigError::Custom` enum variant added | |
| ### ⛰️ Features | |
| - *(cli)* Add system-wide package management ([`#141`](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | |
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | |
| - *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| - *(packages)* Add hooks, build commands, and sandbox support ([`#140`](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) | |
| - *(update)* Allow updating remote URL packages ([`#137`](https://github.com/pkgforge/soar/pull/137)) - ([af13bb6](https://github.com/pkgforge/soar/commit/af13bb637c8c4c4a89cfdac451e39b105e7ee378)) |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~8-~8: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
crates/soar-core/CHANGELOG.md
Outdated
| ## [0.11.0](https://github.com/pkgforge/soar/compare/soar-core-v0.10.0...soar-core-v0.11.0) - 2026-01-15 | ||
|
|
||
| ### ⛰️ Features | ||
|
|
||
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | ||
| - *(cli)* Add system-wide package management ([#141](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | ||
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | ||
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | ||
| - *(packages)* Add hooks, build commands, and sandbox support ([#140](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) | ||
| - *(sandbox)* Add landlock for sandboxing - ([32687c6](https://github.com/pkgforge/soar/commit/32687c67cce0f880d44d407376b5cb7b57b75f48)) | ||
| - *(update)* Allow updating remote URL packages ([#137](https://github.com/pkgforge/soar/pull/137)) - ([af13bb6](https://github.com/pkgforge/soar/commit/af13bb637c8c4c4a89cfdac451e39b105e7ee378)) | ||
|
|
||
| ### 🐛 Bug Fixes | ||
|
|
||
| - *(clippy)* Apply clippy suggestions - ([1b45180](https://github.com/pkgforge/soar/commit/1b45180380790576d50f5c2430038efb0ca6d3a5)) | ||
|
|
||
| ### 🚜 Refactor | ||
|
|
||
| - *(db)* Drop with_pkg_id - ([fa99208](https://github.com/pkgforge/soar/commit/fa99208ec1132c720c0065c7ab3eb235db187d34)) | ||
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | ||
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) | ||
|
|
There was a problem hiding this comment.
Document the breaking API changes in the changelog.
According to the PR objectives, cargo-semver-checks detected breaking changes in this crate: constructible struct added fields (UrlPackage.is_ghcr; InstallTarget fields: entrypoint, binaries, nested_extract, extract_root, hooks, build, sandbox), multiple SoarError enum variants were added, and the public field version_upstream was removed/renamed on Package. These should be documented with a "
📝 Suggested addition
## [0.11.0](https://github.com/pkgforge/soar/compare/soar-core-v0.10.0...soar-core-v0.11.0) - 2026-01-15
+### ⚠️ Breaking Changes
+
+- *(api)* `UrlPackage` struct now includes `is_ghcr` field that must be initialized when constructing
+- *(api)* `InstallTarget` struct now includes additional fields (entrypoint, binaries, nested_extract, extract_root, hooks, build, sandbox) that must be initialized when constructing
+- *(api)* `Package` struct field `version_upstream` removed or renamed
+- *(api)* New `SoarError` enum variants added
+
### ⛰️ Features📝 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.11.0](https://github.com/pkgforge/soar/compare/soar-core-v0.10.0...soar-core-v0.11.0) - 2026-01-15 | |
| ### ⛰️ Features | |
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | |
| - *(cli)* Add system-wide package management ([#141](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | |
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | |
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| - *(packages)* Add hooks, build commands, and sandbox support ([#140](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) | |
| - *(sandbox)* Add landlock for sandboxing - ([32687c6](https://github.com/pkgforge/soar/commit/32687c67cce0f880d44d407376b5cb7b57b75f48)) | |
| - *(update)* Allow updating remote URL packages ([#137](https://github.com/pkgforge/soar/pull/137)) - ([af13bb6](https://github.com/pkgforge/soar/commit/af13bb637c8c4c4a89cfdac451e39b105e7ee378)) | |
| ### 🐛 Bug Fixes | |
| - *(clippy)* Apply clippy suggestions - ([1b45180](https://github.com/pkgforge/soar/commit/1b45180380790576d50f5c2430038efb0ca6d3a5)) | |
| ### 🚜 Refactor | |
| - *(db)* Drop with_pkg_id - ([fa99208](https://github.com/pkgforge/soar/commit/fa99208ec1132c720c0065c7ab3eb235db187d34)) | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | |
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) | |
| ## [0.11.0](https://github.com/pkgforge/soar/compare/soar-core-v0.10.0...soar-core-v0.11.0) - 2026-01-15 | |
| ### ⚠️ Breaking Changes | |
| - *(api)* `UrlPackage` struct now includes `is_ghcr` field that must be initialized when constructing | |
| - *(api)* `InstallTarget` struct now includes additional fields (entrypoint, binaries, nested_extract, extract_root, hooks, build, sandbox) that must be initialized when constructing | |
| - *(api)* `Package` struct field `version_upstream` removed or renamed | |
| - *(api)* New `SoarError` enum variants added | |
| ### ⛰️ Features | |
| - *(apply)* Allow applying ghcr packages - ([06e2b73](https://github.com/pkgforge/soar/commit/06e2b73fce7f4189527b8868bb9adfe14d0600cc)) | |
| - *(cli)* Add system-wide package management ([`#141`](https://github.com/pkgforge/soar/pull/141)) - ([f8d4f1c](https://github.com/pkgforge/soar/commit/f8d4f1c4e0e230427cd037355ba4a23da5b28a6b)) | |
| - *(install)* Add entrypoint option and executable discovery fallbacks - ([b77cffd](https://github.com/pkgforge/soar/commit/b77cffdd6cbdfd66518c1613313d53e1c102a7a2)) | |
| - *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| - *(packages)* Add hooks, build commands, and sandbox support ([`#140`](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) | |
| - *(sandbox)* Add landlock for sandboxing - ([32687c6](https://github.com/pkgforge/soar/commit/32687c67cce0f880d44d407376b5cb7b57b75f48)) | |
| - *(update)* Allow updating remote URL packages ([`#137`](https://github.com/pkgforge/soar/pull/137)) - ([af13bb6](https://github.com/pkgforge/soar/commit/af13bb637c8c4c4a89cfdac451e39b105e7ee378)) | |
| ### 🐛 Bug Fixes | |
| - *(clippy)* Apply clippy suggestions - ([1b45180](https://github.com/pkgforge/soar/commit/1b45180380790576d50f5c2430038efb0ca6d3a5)) | |
| ### 🚜 Refactor | |
| - *(db)* Drop with_pkg_id - ([fa99208](https://github.com/pkgforge/soar/commit/fa99208ec1132c720c0065c7ab3eb235db187d34)) | |
| - *(error)* Don't override error messages - ([e44342f](https://github.com/pkgforge/soar/commit/e44342f3c23b9cdbe23df2739bcf04bde4138025)) | |
| - *(query)* Update query field icons - ([695a427](https://github.com/pkgforge/soar/commit/695a427ef6a4874cb212cdceed192f94150c5548)) |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~9-~9: The official name of this software platform is spelled with a capital “H”.
Context: ...13313d53e1c102a7a2)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
🤖 Prompt for AI Agents
In `@crates/soar-core/CHANGELOG.md` around lines 2 - 23, Add a new "⚠️ Breaking
Changes" subsection under the 0.11.0 release heading in CHANGELOG.md that
clearly lists the API-breaking changes: the new constructible field
UrlPackage.is_ghcr; the new InstallTarget fields entrypoint, binaries,
nested_extract, extract_root, hooks, build, and sandbox; the addition of
multiple SoarError enum variants; and the removal/renaming of the public
Package.version_upstream field, with a brief migration note for each item so
downstream users know what to change when upgrading from 0.10.0 to 0.11.0.
350c0de to
3b921a8
Compare
QaidVoid
force-pushed
the
release-plz-2026-01-13T13-51-31Z
branch
from
3b921a8 to
63945a8
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@CHANGELOG.md`:
- Around line 9-11: Update the changelog entry that currently reads "Add
github/gitlab as first-class package sources" to use proper capitalization
"GitHub/GitLab" (edit the bullet under the *(packages)* section that contains
the text "Add github/gitlab as first-class package sources" and change it to
"Add GitHub/GitLab as first-class package sources"); ensure the commit/PR
references remain unchanged and preserve surrounding formatting.
♻️ Duplicate comments (4)
crates/soar-package/CHANGELOG.md (1)
2-14: Document the breaking API change.The changelog is missing documentation for the breaking change detected by cargo-semver-checks:
integrate_package(andformats::common::integrate_package) parameter count increased from 7 to 8. This helps downstream users understand migration requirements when upgrading from 0.1.1.📝 Suggested addition
## [0.2.0](https://github.com/pkgforge/soar/compare/soar-package-v0.1.1...soar-package-v0.2.0) - 2026-01-17 +### ⚠️ Breaking Changes + +- *(api)* `integrate_package` function signature changed - parameter count increased from 7 to 8 + ### ⛰️ Featurescrates/soar-registry/CHANGELOG.md (1)
2-12: Document the breaking changes.The changelog is missing documentation for breaking changes detected by cargo-semver-checks: public fields removed/renamed on
RemotePackage(rank,pkg,version_upstream). This is critical for downstream consumers to understand migration requirements.📝 Suggested addition
## [0.2.0](https://github.com/pkgforge/soar/compare/soar-registry-v0.1.1...soar-registry-v0.2.0) - 2026-01-17 +### ⚠️ Breaking Changes + +- *(RemotePackage)* Removed/renamed public fields: `rank`, `pkg`, `version_upstream` + ### ⛰️ Featurescrates/soar-config/CHANGELOG.md (1)
2-14: Add a “Breaking Changes” section for 0.2.0.
cargo-semver-checks flagged API-breaking additions (new required fields onPackageOptions/ResolvedPackage, plusConfigError::Custom). These should be called out for downstream users.📝 Suggested addition
## [0.2.0](https://github.com/pkgforge/soar/compare/soar-config-v0.1.1...soar-config-v0.2.0) - 2026-01-17 +### ⚠️ Breaking Changes + +- *(api)* `PackageOptions` and `ResolvedPackage` now include additional fields that must be initialized when constructing +- *(api)* Added `ConfigError::Custom` enum variant + ### ⛰️ Featurescrates/soar-core/CHANGELOG.md (1)
2-24: Add a “Breaking Changes” section for 0.11.0.
cargo-semver-checks reported breaking API changes (newUrlPackage.is_ghcr, newInstallTargetfields, additionalSoarErrorvariants, and removal/rename ofPackage.version_upstream/InstalledPackage.with_pkg_id). These should be documented to guide upgrades.📝 Suggested addition
## [0.11.0](https://github.com/pkgforge/soar/compare/soar-core-v0.10.0...soar-core-v0.11.0) - 2026-01-17 +### ⚠️ Breaking Changes + +- *(api)* `UrlPackage` now includes `is_ghcr` and must be initialized accordingly +- *(api)* `InstallTarget` now includes entrypoint, binaries, nested_extract, extract_root, hooks, build, and sandbox fields +- *(api)* New `SoarError` enum variants added +- *(api)* `Package.version_upstream` and `InstalledPackage.with_pkg_id` removed/renamed + ### ⛰️ Features
🧹 Nitpick comments (1)
crates/soar-package/CHANGELOG.md (1)
9-9: Consider capitalizing platform names."github/gitlab" should be "GitHub/GitLab" for consistency with their official branding.
-- *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) +- *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))
| - *(packages)* Add snapshot version support with URL placeholders - ([099f96c](https://github.com/pkgforge/soar/commit/099f96c2dea4a559b47cad6da98dd0ee10633a02)) | ||
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | ||
| - *(packages)* Add hooks, build commands, and sandbox support ([#140](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) |
There was a problem hiding this comment.
Capitalize GitHub/GitLab in the feature label.
Minor documentation polish.
✏️ Suggested edit
-- *(packages)* Add github/gitlab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))
+- *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f))📝 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.
| - *(packages)* Add snapshot version support with URL placeholders - ([099f96c](https://github.com/pkgforge/soar/commit/099f96c2dea4a559b47cad6da98dd0ee10633a02)) | |
| - *(packages)* Add github/gitlab as first-class package sources ([#142](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| - *(packages)* Add hooks, build commands, and sandbox support ([#140](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) | |
| - *(packages)* Add snapshot version support with URL placeholders - ([099f96c](https://github.com/pkgforge/soar/commit/099f96c2dea4a559b47cad6da98dd0ee10633a02)) | |
| - *(packages)* Add GitHub/GitLab as first-class package sources ([`#142`](https://github.com/pkgforge/soar/pull/142)) - ([2fc3c3b](https://github.com/pkgforge/soar/commit/2fc3c3b4f8e08dd9eac828dbf4f77128f186c91f)) | |
| - *(packages)* Add hooks, build commands, and sandbox support ([`#140`](https://github.com/pkgforge/soar/pull/140)) - ([a776d61](https://github.com/pkgforge/soar/commit/a776d61c7e7f57567a05b18c1baf683c96f08dff)) |
🧰 Tools
🪛 LanguageTool
[uncategorized] ~10-~10: The official name of this software platform is spelled with a capital “H”.
Context: ...6da98dd0ee10633a02)) - (packages) Add github/gitlab as first-class package sources (...
(GITHUB)
🤖 Prompt for AI Agents
In `@CHANGELOG.md` around lines 9 - 11, Update the changelog entry that currently
reads "Add github/gitlab as first-class package sources" to use proper
capitalization "GitHub/GitLab" (edit the bullet under the *(packages)* section
that contains the text "Add github/gitlab as first-class package sources" and
change it to "Add GitHub/GitLab as first-class package sources"); ensure the
commit/PR references remain unchanged and preserve surrounding formatting.
1 participant
🤖 New release
soar-utils: 0.1.1 -> 0.2.0 (⚠ API breaking changes)soar-config: 0.1.1 -> 0.2.0 (⚠ API breaking changes)soar-dl: 0.7.1 -> 0.7.2 (✓ API compatible changes)soar-registry: 0.1.1 -> 0.2.0 (⚠ API breaking changes)soar-db: 0.2.0 -> 0.3.0 (⚠ API breaking changes)soar-package: 0.1.1 -> 0.2.0 (⚠ API breaking changes)soar-core: 0.10.0 -> 0.11.0 (⚠ API breaking changes)soar-cli: 0.9.1 -> 0.10.0⚠
soar-utilsbreaking changes⚠
soar-configbreaking changes⚠
soar-registrybreaking changes⚠
soar-dbbreaking changes⚠
soar-packagebreaking changes⚠
soar-corebreaking changesChangelog
soar-utilssoar-configsoar-dlsoar-registrysoar-dbsoar-packagesoar-coresoar-cliThis PR was generated with release-plz.
Summary by CodeRabbit
Release Notes
New Features
Bug Fixes
Refactor
✏️ Tip: You can customize this high-level summary in your review settings.