@cryptotaxi247 / kubo / commits / 928105865

Apply suggestions from code review

Piotr Galar committed Dec 5, 2022 at 10:02 UTC 928105865c31239d0412e1c53d4fd77651d67da5
1 file changed +3 -3
docs/RELEASE_ISSUE_TEMPLATE.md
+3 -3
@@ -85,7 +85,7 @@ Checklist:
85 - [ ] Clone the `ipfs/distributions` repo locally.
86 - [ ] Create a new branch (`kubo-release-vX.Y.Z-rcn`) from `master`.
87 - [ ] Run `./dist.sh add-version kubo vX.Y.Z-rcN` to add the new version to the `versions` file ([instructions](https://github.com/ipfs/distributions#usage)).
88 - - `dist.sh` will print _WARNING: not marking pre-release kubo vX.Y.Z-rcNn as the current version._.
88 + - `dist.sh` will print _WARNING: not marking pre-release kubo vX.Y.Z-rcN as the current version._.
89 - [ ] Push the `kubo-release-vX.Y.Z-rcn` branch to GitHub and create a PR from that branch ([example](https://github.com/ipfs/distributions/pull/760)).
90 - [ ] Ask for a review from the release reviewer.
91 - [ ] Enable auto-merge for the PR.
@@ -94,14 +94,14 @@ Checklist:
94 - `master` build will publish the artifacts to https://dist.ipfs.io in around 30 minutes
95 - [ ] Ensure that the artifacts are available at https://dist.ipfs.io
96 - [ ] Publish the RC to [the NPM package](https://www.npmjs.com/package/go-ipfs?activeTab=versions) by running https://github.com/ipfs/npm-go-ipfs/actions/workflows/main.yml (it happens automatically but it is safe to speed up the process and kick of a run manually)
97 - - [ ] Cut a pre-release on [GitHub](https://github.com/ipfs/kubo/releases) ([instructions](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release), [example](https://github.com/ipfs/kubo/releases/tag/vX.Y.Z-rcN))
97 + - [ ] Cut a pre-release on [GitHub](https://github.com/ipfs/kubo/releases) ([instructions](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release), [example](https://github.com/ipfs/kubo/releases/tag/v0.17.0-rc1))
98 - Use `vX.Y.Z-rcN` as the tag.
99 - Link to the release issue in the description.
100 - Link to the relevant [changelog](https://github.com/ipfs/kubo/blob/master/docs/changelogs/) in the description.
101 - Check `This is a pre-release`.
102 - [ ] Synchronize release artifacts by running [sync-release-assets](https://github.com/ipfs/kubo/actions/workflows/sync-release-assets.yml) workflow.
103 - [ ] Announce the RC
104 - - [ ] Create a new post on [IPFS Discourse](https://discuss.ipfs.tech). ([example](https://discuss.ipfs.tech/t/kubo-v0-16-0-rcN-release-candidate-is-out/15248))
104 + - [ ] Create a new post on [IPFS Discourse](https://discuss.ipfs.tech). ([example](https://discuss.ipfs.tech/t/kubo-v0-16-0-rc1-release-candidate-is-out/15248))
105 - Use `Kubo vX.Y.Z-rcn Release Candidate is out!` as the title.
106 - Use `kubo` and `go-ipfs` as topics.
107 - Repeat the title as a heading (`##`) in the description.