Repository navigation
chore: add v1.1.0 bundle to main branch - #1737
Conversation
Sync the OLM bundle and channel entries generated by the v1.1.0 release from the 1.1.x branch to main: - olm-catalog/release/channel.yaml - olm-catalog/release/devworkspace-operator.v1.1.0.bundle.yaml - olm-catalog/release-digest/channel.yaml - olm-catalog/release-digest/devworkspace-operator.v1.1.0.bundle.yaml Validated with `opm validate` for both the release and release-digest catalogs. Assisted-by: Claude Opus 4.8 Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Signed-off-by: Badre Tejado-Imam <btejado@redhat.com>
Walkthrough
Pre-merge checks:
|
|
/retest |
1 similar comment
|
/retest |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: btjd, dkwon17, rohanKanojia The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What does this PR do?
Post-release sync for v1.1.0: copies the OLM bundle and channel entries generated on the
1.1.xrelease branch back tomain, completing the release process (per docs/release).Files synced from
1.1.x(the[release]and[post-release]commits):olm-catalog/release/channel.yaml(addsv1.1.0, replacesv1.0.0)olm-catalog/release/devworkspace-operator.v1.1.0.bundle.yamlolm-catalog/release-digest/channel.yaml(addsv1.1.0)olm-catalog/release-digest/devworkspace-operator.v1.1.0.bundle.yamlValidation
opm validate olm-catalog/release/→ passedopm validate olm-catalog/release-digest/→ passedRelease artifacts (already published)
v1.1.0quay.io/devfile:devworkspace-controller,project-clone,project-backup,devworkspace-operator-bundle(:v1.1.0, multi-arch), index:release/:release-digest🤖 Generated with Claude Code
Summary by CodeRabbit