chore(CI): Port tweak version handling for upstream releases

[mtodor]

Description

Port #198 to release branch.

Validation

• no additional validations from what was done for PR on main branch

[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: 09e23c6d-4d52-4e0f-8c19-cba13750f2c8

📥 Commits

Reviewing files that changed from the base of the PR and between 9f8b957 and 3359694.

📒 Files selected for processing (2)

• .github/workflows/build.yml
• README.md

---

📝 Walkthrough

Summary by CodeRabbit

• Documentation

  • Updated image tag examples to use standard semantic-version tags without the v prefix.
  • Clarified the recommended format for referencing container images.

• Chores

  • Improved release image tagging to support semantic-version and release-candidate tags.
  • Stable version tags now also receive the latest image tag.
  • Release-candidate images remain available under their specific version tags.

Walkthrough

The build workflow accepts unprefixed semantic-version and release-candidate tags. It applies the latest image tag to tags without hyphens. The README documents the unprefixed image tag format.

Changes

Release tag convention

Layer / File(s)	Summary
Workflow and documentation alignment .github/workflows/build.yml, README.md	The workflow recognizes unprefixed release and release-candidate tags. The latest tag applies to tags without hyphens. The README uses the updated image tag format.

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

Suggested reviewers: janisz

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly identifies the CI version-handling change for upstream releases.
Description check	✅ Passed	The description states that the CI version-handling change ports to the release branch.
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/port-tweak-release-tags

---

_{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 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.}

[github-actions]

E2E Test Results

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

=== Evaluation Summary ===

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

Tasks:      10/11 passed (90.91%)
Assertions: 30/32 passed (93.75%)
Tokens:     ~60611 (estimate - excludes system prompt & cache)
MCP schemas: ~12562 (included in token total)
Agent used tokens:
  Input:  14350 tokens
  Output: 23605 tokens
Judge used tokens:
  Input:  32844 tokens
  Output: 31629 tokens

[coderabbitai]

Note

GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer.