ROX-36146: Update release 0.2.0 resources

[mtodor]

Description

Set correct snapshot used to release 0.2.0.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 862d7db0-4098-42c2-82fb-824a1c736357

📥 Commits

Reviewing files that changed from the base of the PR and between f894d56 and 6433e33.

📒 Files selected for processing (2)

• releases/0.2.0/agentic-cluster-security-suite-0-2--0-2-0--prod.yaml
• releases/0.2.0/agentic-cluster-security-suite-0-2--0-2-0--stage.yaml

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Summary

Summary by CodeRabbit

• Chores
  • Updated the release snapshot identifier in production and staging configurations.

Walkthrough

The stage and production release manifests now reference agentic-cluster-security-suite-0-2-20260916-095428-000 instead of the warning placeholder.

Changes

Release snapshot configuration

Layer / File(s)	Summary
Update release snapshot references releases/0.2.0/*prod.yaml, releases/0.2.0/*stage.yaml	The stage and production manifests replace the warning placeholder with the generated snapshot identifier.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 6433e

Stage and production now reference the intended generated release snapshot, with no concrete merge-blocking risk identified.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the update to the release 0.2.0 resources.
Description check	✅ Passed	The description accurately states that the correct snapshot is set for release 0.2.0.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch mtodor/update-0-2-0-resources

---

_{Comment @coderabbitai help to get the list of available commands.}

[codecov-commenter]

❌ 2 Tests Failed:

Tests completed	Failed	Passed	Skipped
380	2	378	12

View the full list of 2 ❄️ flaky test(s)

::policy 1

Flake rate in main: 100.00% (Passed 0 times, Failed 152 times)

Stack Traces | 0s run time

- test violation 1
- test violation 2
- test violation 3

::policy 4

Flake rate in main: 100.00% (Passed 0 times, Failed 152 times)

Stack Traces | 0s run time

- testing multiple alert violation messages 1
- testing multiple alert violation messages 2
- testing multiple alert violation messages 3

To view more test analytics, go to the Test Analytics Dashboard
_{📋 Got 3 mins? Take this short survey to help us improve Test Analytics.}

[github-actions]

E2E Test Results

Commit: 6433e33
Workflow Run: View Details
Artifacts: Download test results & logs

=== Evaluation Summary ===

  ✓ cve-cluster-does-exist (assertions: 3/3)
  ✓ cve-cluster-list (assertions: 3/3)
  ✓ list-clusters (assertions: 3/3)
  ✓ cve-cluster-does-not-exist (assertions: 3/3)
  ✓ cve-detected-workloads (assertions: 3/3)
  ✓ rhsa-not-supported (assertions: 2/2)
  ✓ cve-clusters-general (assertions: 3/3)
  ✓ cve-log4shell (assertions: 3/3)
  ✗ cve-multiple (assertions: 3/3)
      one or more verification steps failed
  ✓ cve-detected-clusters (assertions: 3/3)
  ✗ cve-nonexistent (assertions: 3/3)
      one or more verification steps failed

Tasks:      9/11 passed (81.82%)
Assertions: 32/32 passed (100.00%)
Tokens:     ~50878 (estimate - excludes system prompt & cache)
MCP schemas: ~12562 (included in token total)
Agent used tokens:
  Input:  12708 tokens
  Output: 20762 tokens
Judge used tokens:
  Input:  41678 tokens
  Output: 46301 tokens