chore(release): 0.7.0-beta.1 - #66
Conversation
|
Caution The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughSummary by CodeRabbit
WalkthroughThe CLI package version was bumped to ChangesRelease and validation
Estimated code review effort: 3 (Moderate) | ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 19-23: Update the two CLI references in the changelog entries to
use the documented code-intel prefix: change impact --staleness advisory and
edit.ast-grep-plan should both be written as code-intel commands, without
altering the surrounding release-note text.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 2020cca8-9def-47c5-a0ad-6eb0fdc2006a
⛔ Files ignored due to path filters (1)
Cargo.lockis excluded by!**/*.lock
📒 Files selected for processing (3)
.sentrux/baseline.jsonCHANGELOG.mdcrates/code-intel-cli/Cargo.toml
| - Write-time workflow support: the Skill now triggers for implementation, | ||
| refactoring, and fixes; `change impact --staleness advisory` provides | ||
| explicitly non-gating guidance while a working tree is changing. | ||
| - Deterministic, non-mutating `edit.ast-grep-plan` previews, backed by an | ||
| internalized and CI-pinned ast-grep toolchain. |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Prefix new CLI command references with code-intel.
Use code-intel change impact --staleness advisory and code-intel edit.ast-grep-plan so the release notes follow the repository’s documented CLI entry point.
Proposed wording
- refactoring, and fixes; `change impact --staleness advisory` provides
+ refactoring, and fixes; `code-intel change impact --staleness advisory` provides
- Deterministic, non-mutating `edit.ast-grep-plan` previews, backed by an
+ Deterministic, non-mutating `code-intel edit.ast-grep-plan` previews, backed by an📝 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.
| - Write-time workflow support: the Skill now triggers for implementation, | |
| refactoring, and fixes; `change impact --staleness advisory` provides | |
| explicitly non-gating guidance while a working tree is changing. | |
| - Deterministic, non-mutating `edit.ast-grep-plan` previews, backed by an | |
| internalized and CI-pinned ast-grep toolchain. | |
| - Write-time workflow support: the Skill now triggers for implementation, | |
| refactoring, and fixes; `code-intel change impact --staleness advisory` provides | |
| explicitly non-gating guidance while a working tree is changing. | |
| - Deterministic, non-mutating `code-intel edit.ast-grep-plan` previews, backed by an | |
| internalized and CI-pinned ast-grep toolchain. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@CHANGELOG.md` around lines 19 - 23, Update the two CLI references in the
changelog entries to use the documented code-intel prefix: change impact
--staleness advisory and edit.ast-grep-plan should both be written as code-intel
commands, without altering the surrounding release-note text.
Source: Coding guidelines
What changed
0.7.0-beta.1v0.6.0Why
Cloud
mainnow includes the write path, structural hardening, and three-platform release packaging. Publish these changes as a prerelease first instead of cutting stablev0.7.0.Validation
python tests/test_repository_layout.py -vpython tests/test_skill_package.py -vcargo fmt -p code-intel -- --checkcargo check --lockedcargo test -p code-intel --locked --quietcargo build -p code-intel --release --lockedcode-intel sentrux check .code-intel sentrux gate .run execute) completed with exit code 0