Skip to content

ROX-36146: Add release ticket to advisory - #203

Open
mtodor wants to merge 1 commit into
release-0.2from
mtodor/ROX-36146-add-ticket-to-advisory
Open

ROX-36146: Add release ticket to advisory#203
mtodor wants to merge 1 commit into
release-0.2from
mtodor/ROX-36146-add-ticket-to-advisory

Conversation

@mtodor

@mtodor mtodor commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

Description

This PR is adding release ticket to release advisory

Validation

  • Checked Jira ticket ID is correct
  • Compared format with ACS release Resource in release history

@mtodor
mtodor requested a review from janisz as a code owner August 6, 2026 13:45
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

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: 0dc3a4e8-823a-4ca0-8cc0-577eb40c98ea

📥 Commits

Reviewing files that changed from the base of the PR and between 17fdfce and eb2163c.

📒 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

📝 Walkthrough

Summary by CodeRabbit

  • Bug Fixes
    • Resolved issue ROX-36146 in the production and staging release configurations.

Walkthrough

The release notes for the production and stage manifests now reference fixed issue ROX-36146 from redhat.atlassian.net.

Changes

Release note updates

Layer / File(s) Summary
Add fixed issue metadata
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
Both manifests add a fixed issue entry for ROX-36146 with its source URL.

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

Suggested reviewers: janisz

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the Jira ticket and the release advisory change.
Description check ✅ Passed The description explains the release advisory change and records validation steps related to the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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/ROX-36146-add-ticket-to-advisory

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

@github-actions

github-actions Bot commented Aug 6, 2026

Copy link
Copy Markdown

E2E Test Results

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

=== Evaluation Summary ===

  ✓ cve-detected-workloads (assertions: 3/3)
  ✓ cve-cluster-does-exist (assertions: 3/3)
  ✓ cve-clusters-general (assertions: 3/3)
  ✓ rhsa-not-supported (assertions: 2/2)
  ✓ cve-cluster-does-not-exist (assertions: 3/3)
  ✓ cve-log4shell (assertions: 3/3)
  ~ cve-nonexistent (assertions: 2/3)
      - MaxToolCalls: Too many tool calls: expected <= 5, got 8
  ~ cve-multiple (assertions: 2/3)
      - MaxToolCalls: Too many tool calls: expected <= 6, got 8
  ✓ list-clusters (assertions: 3/3)
  ✓ cve-cluster-list (assertions: 3/3)
  ✓ cve-detected-clusters (assertions: 3/3)

Tasks:      11/11 passed (100.00%)
Assertions: 30/32 passed (93.75%)
Tokens:     ~67562 (estimate - excludes system prompt & cache)
MCP schemas: ~12562 (included in token total)
Agent used tokens:
  Input:  17170 tokens
  Output: 23896 tokens
Judge used tokens:
  Input:  72778 tokens
  Output: 64937 tokens

@codecov-commenter

Copy link
Copy Markdown

❌ 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 106 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 106 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants