chore: add v0.42.0 bundle to main branch

[akurinnoy]

Summary

• Copies OLM release and release-digest catalog entries from the 0.42.x release branch to main
• Adds devworkspace-operator.v0.42.0 channel entries and bundle files to both olm-catalog/release/ and olm-catalog/release-digest/

This is the standard post-release step per release docs. See PR #1222 for a previous example.

Summary by CodeRabbit

• New Features
  • Added devworkspace-operator version v0.42.0 to the release channels.
  • Updated the upgrade path so this version replaces v0.41.0, making it available through the fast and release channels.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 32a549ec-06b9-4812-b559-18dd6760168f

📥 Commits

Reviewing files that changed from the base of the PR and between e2c9d9b and 25752f7.

📒 Files selected for processing (4)

• olm-catalog/release-digest/channel.yaml
• olm-catalog/release-digest/devworkspace-operator.v0.42.0.bundle.yaml
• olm-catalog/release/channel.yaml
• olm-catalog/release/devworkspace-operator.v0.42.0.bundle.yaml

---

📝 Walkthrough

Walkthrough

The release channel metadata adds devworkspace-operator.v0.42.0 and links it to v0.41.0 in the upgrade chain.

Changes

OLM release channel bump

Layer / File(s)	Summary
Channel entry update olm-catalog/release/channel.yaml, olm-catalog/release-digest/channel.yaml	Both manifests add devworkspace-operator.v0.42.0 with replaces: devworkspace-operator.v0.41.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• devfile/devworkspace-operator#1624: Updates the same OLM channel manifests with a new devworkspace-operator release entry and replaces relationship.
• devfile/devworkspace-operator#1629: Also adjusts the devworkspace-operator release chain by adding a v0.42.0 channel entry.
• devfile/devworkspace-operator#1632: Modifies the same channel YAML files to extend the upgrade path with a new version entry.

Suggested labels

lgtm, approved

Suggested reviewers

• ibuziuk
• rohanKanojia
• btjd

Poem

A tiny hop through YAML green,
v0.42.0 joins the scene. 🐇
From v0.41.0 the path is bright,
One more carrot in upgrade 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 title accurately describes the main change: adding the v0.42.0 bundle to main.
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.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch add-v0.42.0-bundle-to-main

---

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

[tolusha]

Hi! I'm che-ai-assistant — I help with your pull requests.

Available commands:

• /che-ai-assistant generate-che-doc — Generate a documentation PR based on this PR's changes
• /che-ai-assistant ok-pr-review — Run a comprehensive PR review (summary, code review, deep review, impact analysis)
• /che-ai-assistant help — Show this help message

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: akurinnoy, tolusha
Once this PR has been reviewed and has the lgtm label, please assign dkwon17 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[akurinnoy]

/retest-required