Repository navigation
chore: update rhiza to v1.9.0 - #812
Conversation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (11)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe PR adds a pull request template, updates reusable workflow references and secret forwarding, and revises Conda recipe generation with a pinned grayskull version and new retry checks. ChangesContribution Template
Automation Updates
Priority: ➖ Normal Estimated code review effort: 3 (Moderate) | ~20 minutes Change: Other Merge Risk: ⚪ Minimal · up to This template sync bumps workflow versions, forwards secrets explicitly, and pins grayskull for release recipe generation. No actionable merge-blocking risk was found. The workflows were not run as part of this change. Architecture SummaryArchitecture risk: 🔵 Low · up to The changed surface does not map to a changed system, dependency edge, entrypoint, or external dependency. Changed systems: None identified. Architecture concerns Review detailsBefore / after behavior
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Update rhiza template: v1.8.0 → v1.9.0
Template repo:
jebel-quant/rhizaThe sync changed 11 files (10 template files plus
.rhiza/template.lock). There were no conflicts, and nothing was left unstaged in the working tree..github/workflows/rhiza_release.yml: fixes the conda recipe job (fix(release): retry grayskull on a missing recipe, not on its exit code Jebel-Quant/rhiza#1702). The job now pinsgrayskull==3.2.0and passes--no-use-v1-format, so grayskull writesmeta.yamlagain. It also fails immediately on a real grayskull error instead of retrying it as PyPI lag. This is the failure in the v2.3.4 release run: https://github.com/tschm/pyhrp/actions/runs/36538348782/job/109308115664.github/PULL_REQUEST_TEMPLATE.md: new file.rhiza_*.ymlworkflows get small updates from the template.No gates were run. Run
/rhiza:qualityfor a scorecard.🤖 Generated with Claude Code
Summary by CodeRabbit