Move derive -> crates/derive#6264
Conversation
WalkthroughWorkspace configuration updated: the Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Possibly related PRs
Suggested reviewers
Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro 📒 Files selected for processing (1)
🔇 Additional comments (1)
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 review |
✅ Actions performedReview triggered.
|
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yml
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
Cargo.toml(1 hunks)jit/Cargo.toml(1 hunks)
🔇 Additional comments (1)
Cargo.toml (1)
154-154: Migration verified—no issues remain.The crate relocation is complete and correct:
- ✓
crates/derive/Cargo.tomlexists with valid structure- ✓ No stale
path = "derive"references found- ✓ All consumers (
jit,pylib,stdlib,vm) useworkspace = true- ✓ Root
Cargo.tomlline 154 correctly referencespath = "crates/derive"- ✓ Workspace glob pattern
crates/*captures the moved crate- ✓
derive-impl(separate crate at root level) correctly remains an explicit member
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
ref: #6214
Summary by CodeRabbit