Skip to content

ROX-36040: Move fields to release plan - #231

Merged
mtodor merged 1 commit into
release-0.2from
mtodor/port-ROX-36040-move-fields-to-release-plan
Sep 2, 2026
Merged

ROX-36040: Move fields to release plan#231
mtodor merged 1 commit into
release-0.2from
mtodor/port-ROX-36040-move-fields-to-release-plan

Conversation

@mtodor

@mtodor mtodor commented Sep 1, 2026

Copy link
Copy Markdown
Collaborator

Description

Port #230 to release 0.2 branch.

Validation

  • checks from original PR

@mtodor
mtodor requested a review from janisz as a code owner September 1, 2026 16:46
@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown

E2E Test Results

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

=== Evaluation Summary ===

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

Tasks:      11/11 passed (100.00%)
Assertions: 31/32 passed (96.88%)
Tokens:     ~52582 (estimate - excludes system prompt & cache)
MCP schemas: ~12562 (included in token total)
Agent used tokens:
  Input:  13238 tokens
  Output: 20656 tokens
Judge used tokens:
  Input:  20145 tokens
  Output: 23152 tokens

@codecov-commenter

codecov-commenter commented Sep 1, 2026

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 132 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 132 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.

@coderabbitai

coderabbitai Bot commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

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: 352e885e-d741-4992-b286-070392363cec

📥 Commits

Reviewing files that changed from the base of the PR and between 3d217e0 and efe5dae.

📒 Files selected for processing (2)
  • scripts/prepare-release.sh
  • scripts/templates/release-resource.yaml

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


📝 Walkthrough

Summary by CodeRabbit

  • New Features

    • Release resources now include a direct link to the corresponding GitHub release.
    • Release note references are automatically updated to the computed release version.
  • Improvements

    • Simplified release note metadata by removing redundant synopsis, topic, description, and solution fields.

Walkthrough

Release generation now replaces matching release-notes references with the computed version. The release resource removes unused release-notes fields and adds a GitHub release URL.

Changes

Release resource generation

Layer / File(s) Summary
Release notes template and version substitution
scripts/prepare-release.sh, scripts/templates/release-resource.yaml
The script substitutes the computed release version in release-notes references. The template removes synopsis, topic, description, and solution fields and adds the version-specific GitHub release URL.

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

Merge Risk: ⚪ Minimal · up to efe5d

This PR makes a small release-plan field update, and no actionable merge-blocking risk remains beyond normal checks and review.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 1 files. (1 skipped: 1 … Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly identifies the main change: moving fields to the release plan. It matches the pull request objectives and the resource changes.
Description check ✅ Passed The description identifies the port to the release-0.2 branch and references the validation checks. It relates to the pull request objectives and changeset.
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.
Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 1 files. (1 skipped: 1 unsupported.)

  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch mtodor/port-ROX-36040-move-fields-to-release-plan

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

@mtodor
mtodor merged commit 5945002 into release-0.2 Sep 2, 2026
10 checks passed
@mtodor
mtodor deleted the mtodor/port-ROX-36040-move-fields-to-release-plan branch September 2, 2026 10:15
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.

3 participants