[SHIP-0038] Use Release Branches for Releasing

adambkaplan commented 7 months ago

Is there an existing feature request for this?

[X] I have searched the existing feature requests

Is your feature request related to a problem or use-case? Please describe.

Per SHIP-0038, we are changing our release process to ship official releases from a release branch, rather than from main.

Describe the solution that you would like.

CI and release scripts can be run on a release branch (with release-v* pattern)
Release workflows must use an appropriate release branch and/or git reference (cannot blindly use latest commit from main)
Tagging should be part of the release script process (currently must be done manually by a maintainer).

Describe alternatives you have considered.

See SHIP-0038 for discussion

Anything else?

Part of https://github.com/shipwright-io/community/issues/85

qu1queee commented 7 months ago

@adambkaplan how long does this issue needs to be open? what is missing?

adambkaplan commented 6 months ago

I guess this is missing a definition of done - I recommend we close this when we are able to demonstrate that we can release the CLI via a respective release branch (v0.13 as candidate).

adambkaplan commented 5 months ago

/close

Released v0.13.0 with the branching mechanism!

openshift-ci[bot] commented 5 months ago

@adambkaplan: Closing this issue.

In response to [this](https://github.com/shipwright-io/cli/issues/238#issuecomment-2112652137): >/close > >Released v0.13.0 with the branching mechanism! Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.

shipwright-io / cli