Conversation
📝 WalkthroughWalkthroughThis PR extends STIG version metadata across 16 product configurations by adding new version entries with release dates, introduces a new Amazon Linux 2023 product entry, and publishes a comprehensive RKE2 v2r5 security benchmark XML file with 668 lines of hardening guidance. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. 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 |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@products/ol7/product.toml`:
- Around line 39-40: Remove the non-existent STIG table [stigs.v3r5] and its
release_date entry from the TOML file; specifically delete the [stigs.v3r5]
section (including the release_date = 2026-01-23 line) so only valid STIG
versions (e.g., v3r3) remain.
In `@products/sle12/product.toml`:
- Around line 25-26: Add a new STIG entry for v3r3 to restore version
continuity: insert a new TOML table [stigs.v3r3] and set release_date =
2025-05-14 near the existing [stigs.v3r4] block in product.toml so the sequence
v3r2 → v3r3 → v3r4 is represented.
Summary by CodeRabbit
Release Notes
✏️ Tip: You can customize this high-level summary in your review settings.