Upgrade ruff to 0.16.5 and address new rules - #448
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ruff 0.16 stabilized this rule. We do not want a copyright header on every source file. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. 📝 WalkthroughWalkthroughThe Ruff lint configuration now ignores ChangesRuff configuration
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This change disables Ruff's per-file copyright-header check as intended, without altering application behavior or deployment behavior. No merge-blocking risk remains. 🚥 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. A rabbit checks the linting gate Comment |
Dependabot's ruff 0.16 bump fails CI because 0.16 stabilized new rules and started formatting Python fences in Markdown. This PR bumps ruff and addresses the failures.
uv.lock. The dependabot PR closes when this merges.CPY001(missing-copyright-notice). We do not want a copyright header on every file.Each change is its own commit.
STF-1328
🤖 Generated with Claude Code
Summary by CodeRabbit