Skip to content

fix[ci]: update create-release action with gh cli#278

Merged
openshift-merge-bot[bot] merged 1 commit intoshipwright-io:mainfrom
kaizakin:fix/update-release-workflow
Mar 12, 2026
Merged

fix[ci]: update create-release action with gh cli#278
openshift-merge-bot[bot] merged 1 commit intoshipwright-io:mainfrom
kaizakin:fix/update-release-workflow

Conversation

@kaizakin
Copy link
Contributor

@kaizakin kaizakin commented Feb 6, 2026

Changes

Fixes #166

This PR removes the use of depreceated action actions/create-release and adds gh cli to create releases

reason for choosing gh cli over another action:

  • zero install time
  • this issue of actions going unmaintained won't happen again

/kind cleanup

Submitter Checklist

  • Includes tests if functionality changed/was added
  • Includes docs if changes are user-facing
  • Set a kind label on this PR
  • Release notes block has been filled in, or marked NONE

See the contributor guide
for details on coding conventions, github and prow interactions, and the code review process.

Release Notes

NONE

@pull-request-size pull-request-size bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 6, 2026
@kaizakin
Copy link
Contributor Author

kaizakin commented Feb 6, 2026

I have tested it as well
here's the workflow run: https://github.com/kaizakin/operator/actions/workflows/test-release.yml

@adambkaplan
Copy link
Member

/ok-to-test

@openshift-ci openshift-ci bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Feb 9, 2026
@kaizakin kaizakin force-pushed the fix/update-release-workflow branch from 573be4b to aa91ccc Compare February 18, 2026 07:17
@kaizakin
Copy link
Contributor Author

Hey @IrvingMg, Suggested changes has been made and ready for review 😀

@kaizakin kaizakin requested a review from IrvingMg February 18, 2026 07:25
@IrvingMg
Copy link
Member

Thanks for the changes!

/lgtm

@openshift-ci openshift-ci bot added lgtm Indicates that a PR is ready to be merged. release-note-none and removed release-note labels Feb 18, 2026
@adambkaplan
Copy link
Member

/assign @hasanawad94

For approval

@IrvingMg
Copy link
Member

/ok-to-test

@IrvingMg
Copy link
Member

@kaizakin, could you rebase onto main and push? I guess that should retrigger the CI.

@kaizakin kaizakin force-pushed the fix/update-release-workflow branch from aa91ccc to 696fb16 Compare February 26, 2026 19:17
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 26, 2026
@IrvingMg
Copy link
Member

/ok-to-test

Copy link
Member

@IrvingMg IrvingMg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

The CI issue has been identified and not related to these changes: #280

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 4, 2026
Copy link
Contributor

@hasanawad94 hasanawad94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2026
@hasanawad94 hasanawad94 removed lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Mar 8, 2026
@hasanawad94
Copy link
Contributor

@IrvingMg can you rebase please. Lets verify if ci will pass now

@kaizakin kaizakin force-pushed the fix/update-release-workflow branch from 696fb16 to 592ec7e Compare March 8, 2026 10:17
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 8, 2026
@kaizakin
Copy link
Contributor Author

kaizakin commented Mar 8, 2026

e2e tests failed again 🥲

I suspect this is the issue i found in logs

    containerStatuses:
    - image: gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0
      imageID: ""
      lastState: {}
      name: kube-rbac-proxy
      ready: false
      restartCount: 0
      started: false
      state:
        waiting:
          message: 'Back-off pulling image "gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0":
            ErrImagePull: rpc error: code = NotFound desc = failed to pull and unpack
            image "gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0": failed to resolve reference
            "gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0": gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0:
            not found'
          reason: ImagePullBackOff

@hasanawad94

@IrvingMg
Copy link
Member

IrvingMg commented Mar 8, 2026

Yeah, I saw this issue locally as well. It seems to be related to this old image gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0.

Let's see if /lgtm move this PR forward, as the failure is not related to this change.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 8, 2026
@kaizakin
Copy link
Contributor Author

kaizakin commented Mar 8, 2026

Thanks for checking Irving

i have created an issue for the same #284

@IrvingMg @hasanawad94

@adambkaplan adambkaplan added this to the release-v0.19.0 milestone Mar 9, 2026
@adambkaplan adambkaplan moved this to In Progress in Issues Mar 9, 2026
@IrvingMg
Copy link
Member

@kaizakin could you please rebase? Since #283 has been merged, the CI should pass now.

Signed-off-by: karthik balasubramanian <karthikbalasubramanian08@gmail.com>
@kaizakin kaizakin force-pushed the fix/update-release-workflow branch from 592ec7e to 0b04273 Compare March 10, 2026 19:38
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Mar 10, 2026
@hasanawad94
Copy link
Contributor

/ok-to-test

@hasanawad94
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Mar 12, 2026
Copy link
Contributor

@hasanawad94 hasanawad94 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/LGTM
/APPROVE

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 12, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hasanawad94

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

The pull request process is described here

Details Needs approval from an approver in each of these files:

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

@openshift-merge-bot openshift-merge-bot bot merged commit 1ef64c5 into shipwright-io:main Mar 12, 2026
5 checks passed
@github-project-automation github-project-automation bot moved this from In Progress to Done in Issues Mar 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. release-note-none size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

[BUG] Release workflow uses deprecated actions

4 participants