-
Notifications
You must be signed in to change notification settings - Fork 11
chore: release #130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: release #130
Conversation
π WalkthroughWalkthroughBumps workspace and crate package versions and adds changelog entries across multiple crates documenting four bug fixes (apply/install: URL package version tracking, deterministic hash for packages without checksum, install selection behavior, force reinstall cleanup/resume corruption). No public API or source-code logic changes detected. Changes
Estimated code review effortπ― 2 (Simple) | β±οΈ ~10 minutes Poem
Pre-merge checks and finishing touchesβ Failed checks (1 inconclusive)
β Passed checks (2 passed)
β¨ Finishing touchesπ§ͺ Generate unit tests (beta)
π Recent review detailsConfiguration used: defaults Review profile: CHILL Plan: Pro β Files ignored due to path filters (1)
π Files selected for processing (17)
β Files skipped from review due to trivial changes (1)
π§ Files skipped from review as they are similar to previous changes (12)
π Additional comments (3)
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 |
Codecov Reportβ All modified and coverable lines are covered by tests. π’ Thoughts on this report? Let us know! |
0cf1614 to
9331cba
Compare
There was a problem hiding this 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
π 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 (11)
CHANGELOG.mdCargo.tomlcrates/soar-cli/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-registry/CHANGELOG.mdcrates/soar-registry/Cargo.toml
β Files skipped from review due to trivial changes (3)
- crates/soar-dl/CHANGELOG.md
- crates/soar-dl/Cargo.toml
- crates/soar-core/CHANGELOG.md
π§ Files skipped from review as they are similar to previous changes (2)
- CHANGELOG.md
- crates/soar-cli/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 (5)
crates/soar-core/Cargo.toml (1)
3-3: Version bump looks appropriate.The minor version bump from 0.9.0 to 0.10.0 aligns with the breaking API changes mentioned in the PR objectives (parameter count change in
remove_old_versions).crates/soar-registry/Cargo.toml (1)
3-3: LGTM!Patch version bump is appropriate for the dependency update noted in the changelog.
crates/soar-db/Cargo.toml (1)
3-3: Version bump is appropriate.The minor version bump from 0.1.0 to 0.2.0 correctly reflects the breaking API changes mentioned in the PR objectives (parameter count increases in CoreRepository methods).
crates/soar-db/CHANGELOG.md (1)
2-7: Changelog entry looks good.The entry is well-formatted with a valid commit reference and clear description of the bug fix.
Cargo.toml (1)
51-55: Workspace dependencies properly coordinated.All version updates correctly match the individual crate version bumps, maintaining workspace consistency.
bdbdcec to
fc06264
Compare
There was a problem hiding this 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
β»οΈ Duplicate comments (1)
crates/soar-registry/CHANGELOG.md (1)
6-6: Placeholder commit hash persists.The commit reference "0000000" is still a placeholder and needs to be replaced with the actual commit hash. This issue was previously flagged but the placeholder remains in the current diff.
π 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 (4)
- crates/soar-dl/CHANGELOG.md
- crates/soar-config/Cargo.toml
- crates/soar-utils/CHANGELOG.md
- crates/soar-package/Cargo.toml
π§ Files skipped from review as they are similar to previous changes (6)
- crates/soar-cli/Cargo.toml
- crates/soar-registry/Cargo.toml
- crates/soar-core/CHANGELOG.md
- crates/soar-dl/Cargo.toml
- CHANGELOG.md
- crates/soar-core/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: coverage
- GitHub Check: test
π Additional comments (5)
crates/soar-package/CHANGELOG.md (1)
2-6: Changelog entry looks good.The new version entry is well-documented with a valid commit reference.
crates/soar-db/CHANGELOG.md (1)
2-6: Changelog entry is properly formatted.The new version entry correctly documents the bug fix with a valid commit reference.
Cargo.toml (1)
50-56: Workspace dependency versions are consistent with crate manifests.All seven crates have matching versions between the workspace Cargo.toml and their individual manifest files.
crates/soar-db/Cargo.toml (1)
3-3: Version bump to 0.2.0 is correctly declared across the workspace.The crate version in
crates/soar-db/Cargo.tomland the workspace dependency in the rootCargo.tomlboth declare0.2.0consistently. Dependent crates (soar-cli and soar-core) properly reference this through workspace inheritance.crates/soar-utils/Cargo.toml (1)
3-3: Version bump to 0.1.1 is appropriate and workspace dependencies are consistent.Workspace dependency version matches crate version (0.1.1), and the change is limited to miscellaneous dependency updates, which is appropriate for a patch-level bump.
|
|
||
| ### βοΈ Miscellaneous Tasks | ||
|
|
||
| - Updated the following local packages: soar-utils - ([0000000](https://github.com/pkgforge/soar/commit/0000000)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
π§© Analysis chain
π Script executed:
# First, let's check the actual content of the CHANGELOG.md file around line 6
cat -n crates/soar-config/CHANGELOG.md | head -15Repository: pkgforge/soar
Length of output: 617
π Script executed:
# Find the actual commit that updated soar-utils dependency in soar-config
git log --oneline -20 --follow -- crates/soar-config/Cargo.tomlRepository: pkgforge/soar
Length of output: 79
π Script executed:
# Also search for references to soar-utils in recent commits to the CHANGELOG
git log --oneline -30 | grep -i "soar-utils\|config"Repository: pkgforge/soar
Length of output: 39
π Script executed:
# Check recent commits to soar-utils crate
git log --oneline -30 -- crates/soar-utils/Repository: pkgforge/soar
Length of output: 79
π Script executed:
# Check the commit that updated soar-config version/dependencies
git log --oneline -10 --all | head -20Repository: pkgforge/soar
Length of output: 614
π Script executed:
# Look at the current HEAD and see what commit is there
git rev-parse HEAD && git log --oneline -1Repository: pkgforge/soar
Length of output: 120
π Script executed:
# Check what's in the release commit that might update soar-utils
git show --stat fc06264 | head -50Repository: pkgforge/soar
Length of output: 2946
π Script executed:
# Look for commits that actually modified soar-utils crate files
git log --oneline --all -- crates/soar-utils/ | head -20Repository: pkgforge/soar
Length of output: 486
π Script executed:
# Check the Cargo.toml to see if soar-utils version is referenced
cat crates/soar-config/Cargo.toml | grep -A 5 -B 5 soar-utilsRepository: pkgforge/soar
Length of output: 324
Replace placeholder commit hash with actual commit reference.
The commit reference "0000000" is a placeholder and should be replaced with the actual commit hash. Based on recent commits, this should likely reference commit fc06264 (the release commit) or whichever commit actually bumped the soar-utils dependency version for this release.
π€ Prompt for AI Agents
In crates/soar-config/CHANGELOG.md around line 6, the changelog entry uses a
placeholder commit hash "0000000"; replace that placeholder with the actual
commit hash that updated the soar-utils dependency (e.g., fc06264 if that is the
release/bump commit). Update the markdown link text and URL to point to the real
commit (https://github.com/pkgforge/soar/commit/<actual-hash>) so the changelog
references the correct commit.
fc06264 to
ffb56fb
Compare
π€ New release
soar-utils: 0.1.0 -> 0.1.1 (β API compatible changes)soar-dl: 0.7.0 -> 0.7.1 (β API compatible changes)soar-registry: 0.1.0 -> 0.1.1 (β API compatible changes)soar-db: 0.1.0 -> 0.2.0 (β API breaking changes)soar-package: 0.1.0 -> 0.1.1 (β API compatible changes)soar-core: 0.9.0 -> 0.10.0 (β API breaking changes)soar-cli: 0.9.0 -> 0.9.1soar-config: 0.1.0 -> 0.1.1β
soar-dbbreaking changesβ
soar-corebreaking changesChangelog
soar-utilssoar-dlsoar-registrysoar-dbsoar-packagesoar-coresoar-clisoar-configThis PR was generated with release-plz.
Summary by CodeRabbit
New Features
Bug Fixes
Chores
βοΈ Tip: You can customize this high-level summary in your review settings.