Update nightlies for release-0.9 and remove release-0.7

[mguetta1]

Resolves #185

Summary

Updates nightly CI workflows for the release-0.9 release:

• Adds release-0.9 nightly workflow
• Updates global-ci.yml to support v0.9
• Updates README.md badges
• Removes release-0.7 nightly workflow

Changes

Added

• .github/workflows/nightly-release-0.9.yaml - New nightly workflow for release-0.9
  • Cron schedule: 45 4 * * * (10 minutes after release-0.8)
  • Operator tag: v0.9.0-beta.1
• Conditional blocks in global-ci.yml for v0.9 (both API and UI jobs)
• Badge row in README.md for release-0.9

Removed

• .github/workflows/nightly-release-0.7.yaml - Old workflow (2 versions back)
• Conditional blocks in global-ci.yml for v0.7
• Badge row in README.md for release-0.7

Configuration

• Version added: release-0.9
• Version removed: release-0.7
• Operator tag: v0.9.0-beta.1
• Cron schedule: 45 4 * * *
• Active releases: main, release-0.8, release-0.9

Related Issues

• Update tier workflows for release-0.9 go-konveyor-tests#385 - Update tier workflows for release-0.9

Files Changed

• .github/workflows/nightly-release-0.9.yaml (new)
• .github/workflows/nightly-release-0.7.yaml (deleted)
• .github/workflows/global-ci.yml (modified)
• README.md (modified)

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores

  • Updated CI/CD workflows for release-0.9 builds and tests (renamed nightly workflow, adjusted schedules and test inputs).
  • Added Java provider image reference to automated deployment and test workflows.

• Documentation

  • Updated Releases nightly status table to replace release-0.7 entry with a release-0.9 nightly entry.

[coderabbitai]

📝 Walkthrough

Walkthrough

CI workflows and README updated to target release-0.9: action references and condition checks for start-minikube and install-tackle advanced through release-0.7 → release-0.8 → release-0.9, java-provider-image input added to install-tackle steps, and a nightly README entry changed to release-0.9.

Changes

Cohort / File(s)	Summary
Global CI workflow ​.github/workflows/global-ci.yml	Bumped start-minikube and install-tackle action references from release-0.7 → release-0.8 → release-0.9 and updated corresponding if conditions (v0.7 → v0.8 → v0.9). Added java-provider-image input (quay.io/konveyor/java-external-provider:${{ inputs.tag }}) to install-tackle steps across public/latest flows and e2e job variants.
Nightly workflow ​.github/workflows/nightly-release-0.9.yaml	Renamed workflow to release-0.9 nightly, updated cron schedule, bumped workflow inputs (tag, operator_tag, api_tests_ref, ui_tests_ref) to release-0.9 / v0.9.0-beta.1, adjusted needs dependency and payload branch to release-0.9.
Documentation README.md	Replaced the release-0.7 nightly row with a release-0.9 nightly row in the Releases nightly status table (links/labels updated accordingly).

Sequence Diagram(s)

(omitted)

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped from seven to nine with delight,
CI wires rewired through the quiet night,
Tags and cron ticks, images tucked in place,
Nightly badge updated — a neat little trace,
I twitch my whiskers and nose the new light.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title clearly and specifically describes the main changes: updating nightly CI workflows for release-0.9 and removing release-0.7 support.
Linked Issues check	✅ Passed	The PR fully implements all coding requirements from issue #185: adds release-0.9 nightly workflow, removes release-0.7 nightly workflow, and updates CI configuration and README badges accordingly.
Out of Scope Changes check	✅ Passed	All changes are scoped to the stated objectives of adding release-0.9 nightly support and removing release-0.7, with no extraneous modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

No actionable comments were generated in the recent review. 🎉

🧹 Recent nitpick comments

.github/workflows/global-ci.yml (1)

266-268: Pre-existing: inconsistent latest condition between start-minikube and install-tackle.

start-minikube uses startsWith(inputs.operator_tag, 'latest') (Line 216) while install-tackle uses inputs.operator_tag == 'latest' (Line 268). If someone passed a tag like latest-rc1, minikube would start but konveyor wouldn't install. The same inconsistency exists in the UI job (Lines 344 vs 396). Not introduced by this PR, but worth aligning if you're already editing these blocks.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/global-ci.yml (1)

266-276: ⚠️ Potential issue | 🟡 Minor

java-provider-image missing from the API tests main/latest install-tackle block.

This PR adds java-provider-image to both the release-0.8 and release-0.9 install-tackle steps (lines 250, 262), and the UI tests' main block already has it (line 401). The API tests' main block is now the only install-tackle step without it — likely an oversight.

Proposed fix

       - name: install konveyor
         uses: konveyor/tackle2-operator/.github/actions/install-tackle@main
         if: "${{ inputs.operator_tag == 'latest'}}"
         with:
           operator-bundle-image: "quay.io/konveyor/tackle2-operator-bundle:${{ inputs.operator_tag }}"
           hub-image: "quay.io/konveyor/tackle2-hub:${{ inputs.tag }}"
           ui-image: "quay.io/konveyor/tackle2-ui:${{ inputs.tag }}"
           addon-analyzer-image: "quay.io/konveyor/tackle2-addon-analyzer:${{ inputs.tag }}"
+          java-provider-image: "quay.io/konveyor/java-external-provider:${{ inputs.tag }}"
           image-pull-policy: IfNotPresent
           analyzer-container-memory: 0
           analyzer-container-cpu: 0

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

.github/workflows/global-ci.yml (1)

242-276: ⚠️ Potential issue | 🟡 Minor

java-provider-image missing from the main/latest install-tackle block in API tests.

Lines 254–265 (release-0.9) and 243–253 (release-0.8) both specify java-provider-image, but the main/latest block at lines 266–276 does not. By contrast, the UI tests section does include java-provider-image in its main/latest block (line 401). This inconsistency means API nightly runs against latest won't pin the java provider image.

Proposed fix

       - name: install konveyor
         uses: konveyor/tackle2-operator/.github/actions/install-tackle@main
         if: "${{ inputs.operator_tag == 'latest'}}"
         with:
           operator-bundle-image: "quay.io/konveyor/tackle2-operator-bundle:${{ inputs.operator_tag }}"
           hub-image: "quay.io/konveyor/tackle2-hub:${{ inputs.tag }}"
           ui-image: "quay.io/konveyor/tackle2-ui:${{ inputs.tag }}"
           addon-analyzer-image: "quay.io/konveyor/tackle2-addon-analyzer:${{ inputs.tag }}"
+          java-provider-image: "quay.io/konveyor/java-external-provider:${{ inputs.tag }}"
           image-pull-policy: IfNotPresent
           analyzer-container-memory: 0
           analyzer-container-cpu: 0