docs: enrich release issue template with initial set of mage commands
Piotr Galar committed
Dec 13, 2022 at 10:58 UTC
1ca3ea4a53a7d9857cbfe7c23d0cf9b0cdf29639
1 file changed
+6
docs/RELEASE_ISSUE_TEMPLATE.md
+6
@@ -46,6 +46,7 @@ Checklist:
46
- [ ] Mention @protocol/bifrost-team in the issue and let them know the expected date of the release
47
- Issue link:
48
- [ ] Ensure that the `What's left for release` section has all the checkboxes checked. If that's not the case, discuss the open items with Kubo maintainers and update the release schedule accordingly.
49
+ - `go run main.go kubo:issue:checkOutstandingTasks v0.18.0`
50
- [ ] Create `docs-release-vX.Y.Z` branch, open a draft PR and keep updating `docs/RELEASE_ISSUE_TEMPLATE.md` on that branch as you go.
51
- [ ] Link it in the "Meta" section above.
52
- [ ] Ensure you have a [GPG key generated](https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key) and [added to your GitHub account](https://docs.github.com/en/authentication/managing-commit-signature-verification/adding-a-gpg-key-to-your-github-account). This will enable you to created signed tags.
@@ -69,13 +70,18 @@ Checklist:
70
- [ ] [ipfs/kubo](https://github.com/ipfs/kubo): [example PR](https://github.com/ipfs/kubo/pull/8599)
71
- [ ] [ipfs/ipfs-docs](https://github.com/ipfs/ipfs-docs): [example PR](https://github.com/ipfs/ipfs-docs/pull/1298) - only if the major version changed
72
- [ ] Fork a new branch (`release-vX.Y.Z`) from `master`.
73
+ - `go run main.go kubo:release:cutReleaseBranch v0.18.0`
74
- [ ] Bump the version in `version.go` in the `master` branch to `vX.(Y+1).0-dev` via a PR ([example](https://github.com/ipfs/kubo/pull/9305)).
75
+ - `go run main.go kubo:main:updateVersion v0.18.0`
76
- [ ] **Stage 2 - Release Candidate** - _if any [non-trivial](docs/releases.md#footnotes) changes need to be included in the release, return to this stage_
77
- [ ] If it's not a first RC, add new commits to the `release-vX.Y.Z` branch from `master` using `git cherry-pick -x ...`
78
- Note: `release-*` branches are protected. You can do all needed updates on a separated branch (e.g. `wip-release-vX.Y.Z`) and when everything is settled push to `release-vX.Y.Z`
79
- [ ] Bump the version in `version.go` in the `release-vX.Y.Z` branch to `vX.Y.Z-rcN`.
80
+ - `go run main.go kubo:release:updateReleaseVersion v0.18.0-rc1`
81
- [ ] If it's a first RC, create a draft PR targetting `release` branch if it doesn't exist yet ([example](https://github.com/ipfs/kubo/pull/9306)).
82
+ - `go run main.go kubo:release:createReleasePR v0.18.0`
83
- [ ] Wait for CI to run and complete PR checks. All checks should pass.
84
+ - `go run main.go kubo:release:checkCI v0.18.0`
85
- [ ] Create a signed tag for the release candidate.
86
- [ ] This is a dangerous operation, as it is difficult to reverse due to Go modules and automated Docker image publishing. Remember to verify the commands you intend to run for items marked with ⚠️ with the release reviewer.
87
- [ ] ⚠️ Tag HEAD `release-vX.Y.Z` commit with `vX.Y.Z-rcN` (`git tag -s vX.Y.Z-rcN -m 'Pre-release X.Y.Z-rcn'`)