Conversation
📝 WalkthroughWalkthroughThis pull request performs a coordinated version release across multiple crates and the workspace root. Cargo.toml manifests are updated with version bumps for each crate and workspace-level dependencies. Corresponding changelog entries are added to document new features (apply, install, sandbox, update operations and entrypoint options) and refactoring (error message and query icon handling). Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 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: 2
🤖 Fix all issues with AI agents
In @crates/soar-db/CHANGELOG.md:
- Around line 2-7: Update the CHANGELOG entry for 0.3.0 to explicitly document
the breaking API changes: note that items under
soar_db::schema::metadata::packages::{dsl, columns, version_upstream} are no
longer importable (struct_missing) and that the version_upstream field was
removed/renamed on NewPackage, PackageListing, and Package
(struct_pub_field_missing); for each breaking change include the affected symbol
names, a short description of the change, the impact on users, and a suggested
migration (e.g., the new field name or alternative API to use) so consumers know
how to update their code.
In @crates/soar-utils/CHANGELOG.md:
- Line 6: The CHANGELOG entry contains a placeholder commit hash "0000000" which
is invalid; update the line in CHANGELOG.md (the entry "- Update Cargo.toml
dependencies - ([0000000](...))") to reference the real commit hash for the
Cargo.toml dependency update (or remove the link if the commit cannot be
determined), ensuring the markdown link uses the actual 7+ character Git commit
SHA for the repository so the changelog points to a valid commit.
📜 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.mdcrates/soar-registry/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 (15)
crates/soar-core/Cargo.toml (1)
3-3: LGTM!Version bump to 0.10.1 is consistent with the API-compatible changes designation. Patch increment follows semantic versioning correctly.
crates/soar-registry/Cargo.toml (1)
3-3: LGTM!Version bump to 0.2.0 correctly reflects the breaking API changes (removed/renamed fields on
RemotePackage). Minor version increment for breaking changes in pre-1.0 crates follows semantic versioning.crates/soar-package/Cargo.toml (1)
3-3: LGTM!Version bump to 0.2.0 correctly reflects the breaking API change (
integrate_packagefunction parameter count changed from 7 to 8). Minor version increment for breaking changes in pre-1.0 crates follows semantic versioning.crates/soar-dl/Cargo.toml (1)
3-3: LGTM!Version bump to 0.7.2 is consistent with the API-compatible changes designation. Patch increment follows semantic versioning correctly.
crates/soar-utils/Cargo.toml (1)
3-3: LGTM!Version bump to 0.1.2 is consistent with the API-compatible changes designation. Patch increment follows semantic versioning correctly.
crates/soar-cli/Cargo.toml (1)
3-3: LGTM! Version bump aligns with release plan.The patch version bump from 0.9.1 to 0.9.2 is appropriate for this release, consistent with the PR objectives indicating API-compatible changes.
crates/soar-db/Cargo.toml (1)
3-3: LGTM!Version bump from 0.2.0 to 0.3.0 is appropriate given the breaking changes reported by cargo-semver-checks (removal of
version_upstreamfield from multiple structs and schema path changes).crates/soar-package/CHANGELOG.md (1)
2-11: LGTM!Changelog entry for 0.2.0 is well-structured with proper compare URL, categorized features and refactors, and commit references. The version bump aligns with the breaking change in
integrate_packagefunction signature (7 to 8 parameters).crates/soar-core/CHANGELOG.md (1)
2-14: LGTM!Changelog entry for 0.10.1 comprehensively documents the new features (ghcr package support, entrypoint option, Landlock sandboxing, remote URL updates) and refactors. The patch version bump correctly reflects API-compatible changes.
crates/soar-dl/CHANGELOG.md (1)
2-10: LGTM!Changelog entry for 0.7.2 follows the established format and documents the ghcr package feature and error handling refactor. Patch version bump is appropriate for API-compatible changes.
crates/soar-config/CHANGELOG.md (1)
2-7: LGTM!Changelog entry for 0.2.0 properly documents the new features. The minor version bump is appropriate given the breaking changes (new fields
entrypointandupdateadded toPackageOptionsandResolvedPackage, and newConfigError::Customvariant).crates/soar-config/Cargo.toml (1)
3-3: Version bump looks correct for breaking changes.The bump from
0.1.1to0.2.0aligns with the semver-breaking changes reported by cargo-semver-checks (new fields onPackageOptions,ResolvedPackage, and newConfigError::Customvariant).crates/soar-registry/CHANGELOG.md (1)
2-12: Changelog entry is well-structured.The new 0.2.0 entry follows the project's established changelog format with proper compare links and commit references. The features and refactors documented align with the release scope.
CHANGELOG.md (1)
2-15: Comprehensive changelog entry for 0.9.2 release.The entry documents the key features (GHCR package support, entrypoint options, Landlock sandboxing, remote URL updates) and refactors included in this release. Format is consistent with the project's changelog conventions.
Cargo.toml (1)
51-57: Workspace dependency versions are consistent across all crates.All internal crate versions in the workspace match their individual Cargo.toml declarations:
- Breaking changes (0.x → 0.x+1):
soar-config(0.2.0),soar-db(0.3.0),soar-package(0.2.0),soar-registry(0.2.0)- Compatible changes (patch):
soar-core(0.10.1),soar-dl(0.7.2),soar-utils(0.1.2)
| ## [0.3.0](https://github.com/pkgforge/soar/compare/soar-db-v0.2.0...soar-db-v0.3.0) - 2026-01-13 | ||
|
|
||
| ### 🚜 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 breaking API changes in the changelog.
The 0.3.0 release contains breaking changes (as indicated by the minor version bump and cargo-semver-checks failures mentioned in the PR objectives), but the changelog only lists refactors. According to the PR objectives, the following breaking changes occurred:
struct_missing: items undersoar_db::schema::metadata::packages::{dsl,columns,version_upstream}no longer importablestruct_pub_field_missing:version_upstreamfield removed/renamed onNewPackage,PackageListing, andPackage
Users upgrading to 0.3.0 need explicit documentation of these breaking changes to update their code accordingly.
🤖 Prompt for AI Agents
In @crates/soar-db/CHANGELOG.md around lines 2 - 7, Update the CHANGELOG entry
for 0.3.0 to explicitly document the breaking API changes: note that items under
soar_db::schema::metadata::packages::{dsl, columns, version_upstream} are no
longer importable (struct_missing) and that the version_upstream field was
removed/renamed on NewPackage, PackageListing, and Package
(struct_pub_field_missing); for each breaking change include the affected symbol
names, a short description of the change, the impact on users, and a suggested
migration (e.g., the new field name or alternative API to use) so consumers know
how to update their code.
|
|
||
| ### ⚙️ Miscellaneous Tasks | ||
|
|
||
| - Update Cargo.toml dependencies - ([0000000](https://github.com/pkgforge/soar/commit/0000000)) |
There was a problem hiding this comment.
❓ Verification inconclusive
Script executed:
cat crates/soar-utils/CHANGELOG.mdRepository: pkgforge/soar
Repository: pkgforge/soar
Exit code: 0
stdout:
## [0.1.2](https://github.com/pkgforge/soar/compare/soar-utils-v0.1.1...soar-utils-v0.1.2) - 2026-01-13
### ⚙️ Miscellaneous Tasks
- Update Cargo.toml dependencies - ([0000000](https://github.com/pkgforge/soar/commit/0000000))
## [0.1.1](https://github.com/pkgforge/soar/compare/soar-utils-v0.1.0...soar-utils-v0.1.1) - 2025-12-28
### 🐛 Bug Fixes
- *(install)* Use deterministic hash for package without checksum - ([7a7a060](https://github.com/pkgforge/soar/commit/7a7a06049c61ba38a52921c51cb90b57aee4b809))
## [0.1.0] - 2025-12-26
### ⛰️ Features
- *(crate)* Init soar-utils crate ([#92](https://github.com/pkgforge/soar/pull/92)) - ([26a9d92](https://github.com/pkgforge/soar/commit/26a9d92237d419946186bf084f8b45fad21cc4a1))
Script executed:
# Check if 0000000 is a real commit in this repository
git rev-parse 0000000 2>&1
# Search for commits related to Cargo.toml updates in soar-utils
git log --oneline --all -- crates/soar-utils/Cargo.toml | head -20Repository: pkgforge/soar
Repository: pkgforge/soar
Exit code: 0
stdout:
fatal: ambiguous argument '0000000': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
0000000
7be0d8f chore: release
1d90648 chore: release (#130)
062a587 chore: release (#124)
3ef7b12 chore(crate): downgrade crates to ready for publishing
914e37a chore(deps): move all dependencies to workspace
2d340e5 refactor(integration): integrate soar with modular crates (#123)
26a9d92 feat(crate): init soar-utils crate (#92)
Script executed:
# Check the git log for "Update Cargo.toml" related commits
git log --oneline --all | grep -i "cargo\|dependencies" | head -20Repository: pkgforge/soar
Repository: pkgforge/soar
Exit code: 0
stdout:
914e37a chore(deps): move all dependencies to workspace
9f3b4c1 chore(deps): update dependencies
9419ee5 chore(deps): update dependencies
7d77003 chore(deps): update dependencies
b5a6c04 chore(deps): update dependencies
8e5dc91 chore(deps): update dependencies
ad18d0c chore(cargo): update cargo manifest
26e3a0e chore(deps): update dependencies
e17258e chore(workflow|cargo): auto-assign issues/PRs, update repo url
381dd66 chore(cargo): update package name
Replace placeholder commit hash with actual commit.
The commit hash 0000000 is invalid and does not exist in the repository. This is a bug in the release automation tooling that must be corrected to maintain a usable changelog.
🤖 Prompt for AI Agents
In @crates/soar-utils/CHANGELOG.md at line 6, The CHANGELOG entry contains a
placeholder commit hash "0000000" which is invalid; update the line in
CHANGELOG.md (the entry "- Update Cargo.toml dependencies - ([0000000](...))")
to reference the real commit hash for the Cargo.toml dependency update (or
remove the link if the commit cannot be determined), ensuring the markdown link
uses the actual 7+ character Git commit SHA for the repository so the changelog
points to a valid commit.
1 participant
🤖 New release
soar-utils: 0.1.1 -> 0.1.2 (✓ API compatible 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.10.1 (✓ API compatible changes)soar-cli: 0.9.1 -> 0.9.2⚠
soar-configbreaking changes⚠
soar-registrybreaking changes⚠
soar-dbbreaking changes⚠
soar-packagebreaking changesChangelog
soar-utilssoar-configsoar-dlsoar-registrysoar-dbsoar-packagesoar-coresoar-cliThis PR was generated with release-plz.
Summary by CodeRabbit
New Features
Refactor
✏️ Tip: You can customize this high-level summary in your review settings.