Repository navigation
chore: Raise ansible-core floor to >=2.16.19 - #4707
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe ChangesDependency update
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~2 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to The project now requires patched ansible-core 2.16.19 or newer while excluding 2.17.x, with no identified merge-blocking impact. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
🧪 Generate unit tests (beta)
Comment |
daecdc4 to
98baf41
Compare
Summary
ansible-core>=2.15.0to>=2.16.19,!=2.17.*so Guardian/OSV no longer flags prod CVEs on the declared minimum.uv.lockfor the updated specifier.Test plan
prek run --all-fileslocallySummary by CodeRabbit