-
Notifications
You must be signed in to change notification settings - Fork 12
chore: release #148
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
base: main
Are you sure you want to change the base?
chore: release #148
Conversation
📝 WalkthroughWalkthroughThis pull request performs coordinated version bumps across the workspace's package ecosystem, updating package versions in individual crate manifests and the root workspace file, alongside corresponding changelog entries documenting feature additions and dependency updates. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
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 |
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.
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.
| ## [0.3.2](https://github.com/pkgforge/soar/compare/soar-db-v0.3.1...soar-db-v0.3.2) - 2026-01-18 | ||
|
|
||
| ### ⚙️ Miscellaneous Tasks | ||
|
|
||
| - Updated the following local packages: soar-registry - ([0000000](https://github.com/pkgforge/soar/commit/0000000)) |
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.
Replace the placeholder commit link before release.
The 0000000 commit hash will render as a dead link in the changelog. Please update it to the actual commit SHA for this release entry.
🤖 Prompt for AI Agents
In `@crates/soar-db/CHANGELOG.md` around lines 2 - 6, The changelog entry for
version [0.3.2] contains a placeholder commit reference "0000000"; update the
commit SHA in that entry so both the visible link text and the URL in the
markdown list item under the "### ⚙️ Miscellaneous Tasks" section are replaced
with the real commit hash for this release (i.e., change
"([0000000](.../commit/0000000))" to the actual SHA in both places).
| ## [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)) |
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.
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.
| ## [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.
🤖 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.3soar-registry: 0.2.1 -> 0.2.2soar-db: 0.3.1 -> 0.3.2soar-package: 0.2.1 -> 0.2.2⚠
soar-configbreaking changes⚠
soar-corebreaking changesChangelog
soar-configsoar-coresoar-clisoar-registrysoar-dbsoar-packageThis PR was generated with release-plz.
Summary by CodeRabbit
New Features
Chores
✏️ Tip: You can customize this high-level summary in your review settings.