Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initial Release Instructions #223

Merged

Conversation

adambkaplan
Copy link
Member

Changes

This is an initial guide on how to release the Shipwright operator. It provides guidance on how to create a release candidate build with GitHub actions, and adds release verification instructions to the OLM development guide.

Future updates to this guide will include instructions on how to publish the new bundle to OperatorHub.

Related to #132

/kind documentation

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

This is an initial guide on how to release the Shipwright
operator. It provides guidance on how to create a release
candidate build with GitHub actions, and adds release
verification instructions to the OLM development guide.

Future updates to this guide will include instructions on
how to publish the new bundle to OperatorHub.

Signed-off-by: Adam Kaplan <[email protected]>
@pull-request-size pull-request-size bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jun 24, 2024
@openshift-ci openshift-ci bot added the kind/documentation Categorizes issue or PR as related to documentation. label Jun 24, 2024
@qu1queee qu1queee added this to the release-v0.14.0 milestone Jun 27, 2024
@qu1queee qu1queee requested review from SaschaSchwarze0 and removed request for coreydaley June 27, 2024 06:42
Copy link

@qu1queee qu1queee left a comment

Choose a reason for hiding this comment

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

/lgtm


Find the draft release. Edit the release as follows:

- Add a leading `v` suffix to the generated tag and release name. Ex: `0.13.0-rc0` becomes `v0.13.0-rc0`.

Choose a reason for hiding this comment

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

Could we avoid the need for this manual step?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes - I'll create an issue for follow-up.

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jun 27, 2024
@adambkaplan
Copy link
Member Author

/approve

Self-approval (PR submitted by maintainer)

Copy link
Contributor

openshift-ci bot commented Jun 27, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: adambkaplan

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

The pull request process is described here

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-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 27, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit ebc4b09 into shipwright-io:main Jun 27, 2024
5 checks passed
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. kind/documentation Categorizes issue or PR as related to documentation. lgtm Indicates that a PR is ready to be merged. release-note-none size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants