Plan coordinated updates across dependent packages
Plans coordinated updates across R package dependencies with timeline and blockers.
/plugin marketplace add Data-Wise/rforge/plugin install data-wise-rforge@Data-Wise/rforgeOptional version or change descriptionPlan coordinated updates across your R package ecosystem dependencies.
Uses the rforge_cascade_plan MCP tool to:
# Plan cascade for current changes
/rforge:cascade
# Plan for version bump
/rforge:cascade "medfit 2.2.0"
# Detailed cascade plan
/rforge:cascade --detailed
Returns cascade plan with:
š CASCADE PLAN: medfit 2.1.0 ā 2.2.0
Phase 1: Core (Week 1)
1. medfit
ā Update version
ā Run tests
ā Update NEWS.md
ā± 2 hours
Phase 2: Implementations (Week 2)
2. probmed
⢠Update medfit dependency
⢠Re-run tests
ā± 1 hour
3. medsim
⢠Update medfit dependency
⢠Update vignette
ā± 2 hours
Phase 3: Meta (Week 2)
4. mediationverse
⢠Update all dependencies
ā± 30 min
Total time: 5.5 hours over 2 weeks
ā ļø CASCADE PLAN: Breaking API change
Phase 1: Preparation (Week 1)
1. Add deprecation warnings
2. Update all docs
3. Create migration guide
ā± 4 hours
Phase 2: Core Package (Week 2)
1. medfit ā 3.0.0 (major bump)
⢠Implement breaking changes
⢠Update all tests
ā± 8 hours
Phase 3: Dependent Updates (Weeks 3-4)
2-4. Update all dependents
Each: API migration + tests
ā± 12 hours total
Phase 4: Meta Package (Week 5)
5. mediationverse version alignment
ā± 1 hour
Total: ~25 hours over 5 weeks
Blockers: Need CRAN approval for medfit first
/rforge:impact - See affected packages/rforge:release - CRAN submission order/rforge:deps - Understand dependencies