Closed clobrano closed 7 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: clobrano
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/lgtm
@clobrano: The following tests failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/4.12-openshift-e2e | 1c4cd22b155e834caa5bce144cc89f21d2913970 | link | true | /test 4.12-openshift-e2e |
ci/prow/4.15-openshift-e2e | 1c4cd22b155e834caa5bce144cc89f21d2913970 | link | true | /test 4.15-openshift-e2e |
Full PR test history. Your PR dashboard.
E2E tests do not test the changes of this PR. Can merge without them.
Why we need this PR
FAR CI uses the post-release workflow for building and pushing versioned bundle images, however, the workflow cannot guess the right PREVIOUS_VERSION (when it is necessary) and it would publish manifests with wrong value of the
.spec.replaces
field.Changes made
post-release
to therelease
workflow, which supports manual inputs such has PREVIOUS_VERSIONrelease
workflow with the latest version of Medik8s shared workflow to build and push community bundlesspec.replaces
field only in OKD bundleTest plan
Tested locally with nektos/act
ECOPROJECT-1579