-
You need to be a member of tektoncd-cli OWNERS to be able to push the new branch.
-
You need to have your own tekton cluster under
minikube,gcpor other means. -
Start reading this README, and you can start a new release with the release.sh script.
-
Update the main README.md, and change the version number in there (i.e:
v0.5.0) to the version you are releasing. Make a PR and get it merged ASAP. -
When the release is done in https://github.com/tektoncd/cli/releases, edit the release and change it from pre-release as released.
-
When it's released, you can build the rpm according to this README. Make sure you have done the PREREQ to be able to upload it to the copr repository. This could take some time if copr builder is busy.
-
You need to edit the Changelog according to the other templates in there. Usually you may want to do this in hackmd so you can have other cli maintainers do this with you. You can see an example here.
-
Get someone with OSX to test the
brew install tektoncd/cli/tektoncd-cli -
Get someone with Fedora to test the RPM:
dnf makecache
dnf upgrade tektoncd-cli-
Make an update for homebrew-core for tektoncd-cli formula, and make sure you get the proper
sha256sumand update it like this: -
Make an update to the
test-runnerimage in the plumbing repo (the image where we run the CI on pipeline which usestkn) to increase the version here:https://github.com/tektoncd/plumbing/blob/master/tekton/images/test-runner/Dockerfile#L51
-
Announce and spread the love on twitter. Make sure you tag @tektoncd account so you get retweeted and perhaps add the major new features in the tweet. See here for an example. Do not fear to add a bunch of emojis 🎉🥳. Ask @vdemeester for tips 🤣.
-
Notify the cli channel on slack.