✨ Add kai solution server to release pipeline

[fabianvf]

Closes #448

Summary by CodeRabbit

• Chores
  • Integrated the kai-solution-server component into the release, build, and test workflows, ensuring it is included in automated releases and changelog generation.

[coderabbitai]

Walkthrough

The .github/workflows/create-release.yml workflow was updated to integrate the konveyor/kai repository and its Docker image into the release, build, and test automation. This includes extending job matrices, adding release and validation steps, updating bundle builds, and including konveyor/kai in changelog aggregation.

Changes

File(s)	Summary of Changes
.github/workflows/create-release.yml	Added konveyor/kai and its Docker image to release, build, and test jobs; updated job matrices, steps, and changelog aggregation.

Assessment against linked issues

Objective	Addressed	Explanation
Include Kai solution server in release automation pipeline (#448)	✅
Add Kai solution server to build pipeline and bundle updates (#448)	✅

Poem

A new friend joins the release parade,
With kai-solution-server, our plans are well-laid.
Bundles now bigger, changelogs more bright,
Docker images ready, everything’s right!
In YAML we trust, as the workflows expand—
Another smooth launch, just as we planned.
🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e809c11 and 108a282.

📒 Files selected for processing (1)

• .github/workflows/create-release.yml (3 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• .github/workflows/create-release.yml

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: build-operator-bundle

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between af596c8 and e809c11.

📒 Files selected for processing (1)

• .github/workflows/create-release.yml (4 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: build-operator-bundle

🔇 Additional comments (3)

.github/workflows/create-release.yml (3)

127-142: kai release added in release-bases ‑ looks correct by itself
The step follows the established pattern for other base images (create-release + wait-for-image) – nice and consistent.

---

239-239: Verify the composite action supports the new kai input
./operator/.github/actions/make-bundle previously accepted a fixed set of image arguments. If that action’s inputs: block hasn’t been updated to include kai, the job will fail with
Unexpected input(s) 'kai'.

Please double-check the composite action, or update it accordingly.

---

356-357: Changelog aggregation extended – LGTM
Including konveyor/kai here keeps the release notes complete.

[djzager]

Probably also need to look at updating our config in release tools to get kai and editor-extensions repo in line with the rest of konveyor.

https://github.com/konveyor/release-tools/tree/main/pkg/config

[djzager]

ACK