feea7d36f · cryptotaxi247/kubo · siGit Code & Deploy

@@ -39,147 +39,142 @@ As usual, this release includes important fixes, some of which may be critical f

39

40 ## ✅ Release Checklist

41

42 -- [ ] Verify you have all the access and tools you need to perform the release

43 - - [ ] 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.

44 - - [ ] Ensure you have [admin access](https://discuss.ipfs.tech/g/admins) to [IPFS Discourse](https://discuss.ipfs.tech/). Admin access is required to globally pin posts and create banners. @2color might be able to assist you.

45 - - [ ] Access to [#bifrost](https://filecoinproject.slack.com/archives/C03MMMF606T) channel in FIL Slack might come in handy. Ask the release reviewer to invite you over.

46 - - [ ] Access to [#shared-pl-marketing-requests](https://filecoinproject.slack.com/archives/C018EJ8LWH1) channel in FIL Slack will be required to request social shares. Ask the release reviewer to invite you over.

47 - - [ ] After the release is deployed to our internal infrastructure, you're going to need read access to [IPFS network metrics](https://github.com/protocol/pldw/blob/624f47cf4ec14ad2cec6adf601a9f7b203ef770d/docs/sources/ipfs.md#ipfs-network-metrics) dashboards. Open an access request in https://github.com/protocol/pldw/issues/new/choose if you don't have it yet ([example](https://github.com/protocol/pldw/issues/158)).

48 - - [ ] You're also going to need NPM installed on your system. See [here](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) for instructions.

49 - - [ ] Install ZSH ([instructions](https://github.com/ohmyzsh/ohmyzsh/wiki/Installing-ZSH#install-and-set-up-zsh-as-default)). It is needed by the changelog creation script.

50 - - [ ] Ensure you have `kubo` checked out under `$(go env GOPATH)/src/github.com/ipfs/kubo`. This is required by the changelog creation script.

51 - - If you want your clone to live in a different location, you can symlink it to the expected location by running `mkdir -p $(go env GOPATH)/src/github.com/ipfs && ln -s $(pwd) $(go env GOPATH)/src/github.com/ipfs/kubo`.

52 -- [ ] Upgrade to the latest patch release of Go that CircleCI has published (currently used version: `1.19.1`)

53 - - See the list here: https://hub.docker.com/r/cimg/go/tags

54 - - [ipfs/distributions](https://github.com/ipfs/distributions): bump [this version](https://github.com/ipfs/distributions/blob/master/.tool-versions#L2)

55 - - [ipfs/kubo](https://github.com/ipfs/kubo): [example PR](https://github.com/ipfs/kubo/pull/8599)

56 - - [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

57 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) notify-bifrost --date YYYY-MM-DD`

58 - - [ ] Open an issue against [bifrost-infra](https://github.com/protocol/bifrost-infra) ahead of the release ([example](https://github.com/protocol/bifrost-infra/issues/2221)).

59 - - **Idealy, do this multiple days in advance of the RC** to give Bifrost the heads up that asks will be coming their way.

60 - - Spell out all that we want updated - gateways, the bootstraper and the cluster/preload nodes

61 - - Mention @protocol/bifrost-team in the issue and let them know the expected date of the release

62 - - Link it in the "Meta" section above

63 -- [ ] 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.

64 -- [ ] 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.

65 - - Link it in the "Meta" section above.

66 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) cut-branch`

67 - - [ ] Fork a new branch (`release-vX.Y.Z`) from `master`.

68 - - [ ] 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)).

69 - - [ ] Bump the version in `version.go` in the `release-vX.Y.Z` branch to `vX.Y.Z-rcN`.

70 - - [ ] 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)).

71 - - [ ] Wait for CI to run and complete PR checks. All checks should pass.

72 -- [ ] If it's not a first RC, add new commits to the `release-vX.Y.Z` branch from `master` using `git cherry-pick -x ...`

73 - - 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`

74 -- [ ] Update the [docs/changelogs/vX.Y.md](docs/changelogs) with the new commits and contributors.

75 - - [ ] Run `./bin/mkreleaselog` twice to generate the changelog and copy the output.

76 - - The first run of the script might be poluted with `git clone` output.

77 - - [ ] Paste the output into the `### Changelog` section of the changelog file inside the `<details><summary></summary></details>` block.

78 - - [ ] Commit the changelog changes.

79 - - [ ] Push the `release-vX.Y.Z` branch to GitHub (`git push origin release-vX.Y.Z`)

80 -- [ ] Mark the PR created from `release-vX.Y.Z` as ready for review.

81 - - [ ] Ensure the PR is targetting `release` branch.

82 - - [ ] Ensure that CI is green.

83 - - [ ] Have release reviewer review the PR.

84 -- [ ] Merge the PR into `release` branch using the `Create a merge commit` (do **NOT** use `Squash and merge` nor `Rebase and merge` because we need to be able to sign the merge commit).

85 - - Do not delete the `release-vX.Y.Z` branch.

86 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) tag`

87 - - [ ] Create a signed tag for the release candidate.

88 - - 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.

89 - - ⚠️ Tag HEAD `release-vX.Y.Z`/`release` commit with `vX.Y.Z(-RCN)` (`git tag -s vX.Y.Z(-RCN) -m 'Release X.Y.Z(-RCN)'`)

90 - - Run `git show vX.Y.Z(-RCN)` to ensure the tag is correct.

91 - - ⚠️ Push the `vX.Y.Z(-RCN)` tag to GitHub (`git push origin vX.Y.Z(-RCN)`; DO NOT USE `git push --tags` because it pushes all your local tags).

92 -- [ ] Wait for [Publish docker image](https://github.com/ipfs/kubo/actions/workflows/docker-image.yml) workflow run initiated by the tag push to finish.

93 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) publish-to-distributions`

94 - - [ ] Add artifacts to https://dist.ipfs.tech by making a PR against [ipfs/distributions](https://github.com/ipfs/distributions)

95 - - Clone the `ipfs/distributions` repo locally.

96 - - Create a new branch (`kubo-release-vX.Y.Z-rcn`) from `master`.

97 - - 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)).

98 - - `dist.sh` will print _WARNING: not marking pre-release kubo vX.Y.Z-rcN as the current version._.

99 - - 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)).

100 - - Ask for a review from the release reviewer.

101 - - Enable auto-merge for the PR.

102 - - PR build will build the artifacts and generate a diff in around 30 minutes

103 - - PR will be merged automatically once the diff is approved

104 - - `master` build will publish the artifacts to https://dist.ipfs.io in around 30 minutes

105 - - Ensure that the artifacts are available at https://dist.ipfs.io

106 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) publish-to-npm`

107 - - [ ] 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)

108 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) publish-to-github`

109 - - [ ] 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))

110 - - `km kubo:createGitHubRelease v0.18.0-rc1`

111 - - Use `vX.Y.Z-rcN` as the tag.

112 - - Link to the release issue in the description.

113 - - Link to the relevant [changelog](https://github.com/ipfs/kubo/blob/master/docs/changelogs/) in the description.

114 - - Copy the relevant [changelog](https://github.com/ipfs/kubo/blob/release/docs/changelogs/) into the release description.

115 - - Keep the release notes as trim as possible (e.g. remove top headers where possible, [example](https://github.com/ipfs/kubo/releases/tag/v0.17.0))

116 - - Check `This is a pre-release`.

117 - - [ ] Synchronize release artifacts by running [sync-release-assets](https://github.com/ipfs/kubo/actions/workflows/sync-release-assets.yml) workflow.

118 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) notify-bifrost --date YYYY-MM-DD`

119 - - [ ] Update the issue against [bifrost-infra](https://github.com/protocol/bifrost-infra) ([example](https://github.com/protocol/bifrost-infra/issues/2109)).

120 - - [ ] Mention @protocol/bifrost-team in the issue to let them know the release is ready

121 - - [ ] [Optional] Reply under a message about the issue in the #bifrost channel on FIL Slack once the RC is out. Send the message to the channel.

122 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) promote`

123 - - [ ] 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))

124 - - Use `Kubo vX.Y.Z-rcn Release Candidate is out!` as the title.

125 - - `km discourse:post:getTitle v0.18.0-rc1`

126 - - Use `kubo` and `go-ipfs` as topics.

127 - - Repeat the title as a heading (`##`) in the description. Link to the GitHub Release, binaries on IPNS, docker pull command and release notes in the description.

128 - - Use `Kubo vX.Y.Z Release is out!` as the title.

129 - - Use `kubo` and `go-ipfs` as topics.

130 - - Repeat the title as a heading (`##`) in the description.

131 - - Link to the GitHub Release, binaries on IPNS, docker pull command and release notes in the description.

132 - - [ ] Pin the topic globally so that it stays at the top of the category.

133 - - If there is no more important banner currently set on Discourse (e.g. IPFS Camp announcement), make the topic into a banner.

134 - - [ ] Check if Discourse post was automatically copied to:

135 - - [ ] IPFS Discord #ipfs-chatter

136 - - [ ] FIL Slack #ipfs-chatter

137 - - [ ] Matrix https://matrix.to/#/#ipfs-chatter:ipfs.io

138 - - [ ] Mention [early testers](https://github.com/ipfs/go-ipfs/tree/master/docs/EARLY_TESTERS.md) in the comment under the release issue ([example](https://github.com/ipfs/kubo/issues/9319#issuecomment-1311002478)).

139 - - [ ] Add a link to the release to this release issue as a comment.

140 - - [ ] Share the link to the GitHub release

141 - - [ ] Twitter (request in Filecoin Slack channel #shared-pl-marketing-requests; [example](https://filecoinproject.slack.com/archives/C018EJ8LWH1/p1664903524843269?thread_ts=1664885305.374909&cid=C018EJ8LWH1))

142 - - [ ] [Reddit](https://reddit.com/r/ipfs)

143 -- [ ] Add a link from release notes to Discuss post (like we did here: https://github.com/ipfs/kubo/releases/tag/v0.17.0)

42 +- [ ] Verify you have access to all the services and tools required for the release

43 + - [ ] [GPG signature](https://docs.github.com/en/authentication/managing-commit-signature-verification) configured in local git and in GitHub

44 + - [ ] [admin access to IPFS Discourse](https://discuss.ipfs.tech/g/admins)

45 + - ask the previous release owner (or @2color) for an invite

46 + - [ ] [access to #bifrost](https://filecoinproject.slack.com/archives/C03MMMF606T) channel in FIL Slack

47 + - ask the previous release owner for an invite

48 + - [ ] [access to #shared-pl-marketing-requests](https://filecoinproject.slack.com/archives/C018EJ8LWH1) channel in FIL Slack

49 + - ask the previous release owner for an invite

50 + - [ ] [access to IPFS network metrics](https://github.com/protocol/pldw/blob/624f47cf4ec14ad2cec6adf601a9f7b203ef770d/docs/sources/ipfs.md#ipfs-network-metrics) dashboards in Grafana

51 + - open an access request in the [pldw](https://github.com/protocol/pldw/issues/new/choose)

52 + - [example](https://github.com/protocol/pldw/issues/158)

53 + - [ ] [npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) installed on your system (_only if you're not using [kuboreleaser](https://github.com/ipfs/kuboreleaser)_)

54 + - [ ] [zsh](https://github.com/ohmyzsh/ohmyzsh/wiki/Installing-ZSH#install-and-set-up-zsh-as-default) installed on your system (_only if you're not using [kuboreleaser](https://github.com/ipfs/kuboreleaser)_)

55 + - [ ] [kubo](https://github.com/ipfs/kubo) checked out under `$(go env GOPATH)/src/github.com/ipfs/kubo` (_only if you're not using [kuboreleaser](https://github.com/ipfs/kuboreleaser)_)

56 + - you can also symlink your clone to the expected location by running `mkdir -p $(go env GOPATH)/src/github.com/ipfs && ln -s $(pwd) $(go env GOPATH)/src/github.com/ipfs/kubo`

57 + - [ ] [Reddit](https://www.reddit.com) account

58 +- [ ] Upgrade Go used in CI to the latest patch release available in [CircleCI](https://hub.docker.com/r/cimg/go/tags)

59 + - [ ] [ipfs/distributions](https://github.com/ipfs/distributions)

60 + - [example](https://github.com/ipfs/distributions/pull/756)

61 + - [ ] [ipfs/ipfs-docs](https://github.com/ipfs/ipfs-docs)

62 + - [example](https://github.com/ipfs/ipfs-docs/pull/1298)

63 +- [ ] Notify the bifrost team about the upcoming release using `kuboreleaser release --version vX.Y.Z(-RCN) notify-bifrost --date YYYY-MM-DD`

64 + - [ ] open an issue against [bifrost-infra](https://github.com/protocol/bifrost-infra)

65 + - [example](https://github.com/protocol/bifrost-infra/issues/2221)

66 + - [ ] link the issue in the [Meta](#meta) section

67 +- [ ] Verify there is nothing [left for release](-what-s-left-for-release)

68 +- [ ] Create a release process improvement PR

69 + - [ ] update the [release issue template](docs/RELEASE_ISSUE_TEMPLATE.md) as you go

70 + - [ ] link it in the [Meta](#meta) section

71 +- [ ] Cut the release branch and update version numbers accordingly using `kuboreleaser release --version vX.Y.Z(-RCN) cut-branch`

72 + - [ ] create a new branch `release-vX.Y` from `master`

73 + - [ ] update the `CurrentVersionNumber` in [version.go](version.go) in the `master` branch to `vX.(Y+1).0-dev`

74 + - [example](https://github.com/ipfs/kubo/pull/9305)

75 + - [ ] update the `CurrentVersionNumber` in [version.go](version.go) in the `release-vX.Y` branch to `vX.Y.Z(-RCN)`

76 + - [example](https://github.com/ipfs/kubo/pull/9394)

77 + - [ ] create a draft PR from `release-vX.Y` to `release`

78 + - [example](https://github.com/ipfs/kubo/pull/9306)

79 + - [ ] verify all CI checks on the PR from `release-vX.Y` to `release` are passing

80 +- [ ] Cherry-pick commits from `master` to the `release-vX.Y` using `git cherry-pick -x <commit>`

81 +- [ ] Add full changelog and contributors to the [changelog](docs/changelogs/vX.Y.md)

82 +- [ ] Merge the PR from `release-vX.Y` to `release` using the `Create a merge commit`

83 + - do **NOT** use `Squash and merge` nor `Rebase and merge` because we need to be able to sign the merge commit

84 + - do **NOT** delete the `release-vX.Y` branch

85 +- [ ] Create the release tag using `kuboreleaser release --version vX.Y.Z(-RCN) tag`

86 + - This is a dangerous operation! Go and Docker publishing are difficult to reverse! Have the release reviewer verify all the commands marked with ⚠️!

87 + - [ ] ⚠️ tag the HEAD commit of the `release-vX.Y` branch using `git tag -s vX.Y.Z(-RCN) -m 'Prerelease X.Y.Z(-RCN)'`

88 + - [ ] ⚠️ tag the HEAD commit of the `release` branch using `git tag -s vX.Y.Z(-RCN) -m 'Release X.Y.Z(-RCN)'`

89 + - [ ] ⚠️ verify the tag is signed and tied to the correct commit using `git show vX.Y.Z(-RCN)`

90 + - [ ] ⚠️ push the tag to GitHub using `git push origin vX.Y.Z(-RCN)`

91 + - do **NOT** use `git push --tags` because it pushes all your local tags

92 +- [ ] Wait for [Publish docker image](https://github.com/ipfs/kubo/actions/workflows/docker-image.yml) workflow run initiated by the tag push to finish

93 + - [ ] verify the image is available on [Docker Hub](https://hub.docker.com/r/ipfs/kubo/tags)

94 +- [ ] Publish the release to [ipfs.tech](https://dist.ipfs.tech) using `kuboreleaser release --version vX.Y.Z(-RCN) publish-to-distributions`

95 + - [ ] check out [ipfs/distributions](https://github.com/ipfs/distributions)

96 + - [ ] run `./dist.sh add-version kubo vX.Y.Z(-RCN)` to add the new version to the `versions` file

97 + - [usage](https://github.com/ipfs/distributions#usage)

98 + - [ ] create and merge the PR which updates `dists/kubo/versions` and `dists/go-ipfs/versions`

99 + - [example](https://github.com/ipfs/distributions/pull/760)

100 + - [ ] wait for the [CI](https://github.com/ipfs/distributions/actions/workflows/main.yml) workflow run initiated by the merge to master to finish

101 + - [ ] verify the release is available on [dist.ipfs.io](https://dist.ipfs.io/#kubo)

102 +- [ ] Publish the release to [NPM](https://www.npmjs.com/package/go-ipfs?activeTab=versions) using `kuboreleaser release --version vX.Y.Z(-RCN) publish-to-npm`

103 + - [ ] run the [Release to npm](https://github.com/ipfs/npm-go-ipfs/actions/workflows/main.yml) workflow

104 + - [ ] check [Release to npm](https://github.com/ipfs/npm-go-ipfs/actions/workflows/main.yml) workflow run logs to verify it discovered the new release

105 + - [ ] verify the release is available on [NPM](https://www.npmjs.com/package/go-ipfs?activeTab=versions)

106 +- [ ] Publish the release to [GitHub](https://github.com/ipfs/kubo/releases) using `kuboreleaser release --version vX.Y.Z(-RCN) publish-to-github`

107 + - [ ] create a new release on [GitHub](https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository#creating-a-release)

108 + - [prerelease example](https://github.com/ipfs/kubo/releases/tag/v0.17.0-rc1)

109 + - use the `vX.Y.Z(-RCN)` tag

110 + - link to the release issue

111 + - link to the changelog in the description

112 + - check the `This is a pre-release` checkbox

113 + - [release example](https://github.com/ipfs/kubo/releases/tag/v0.17.0)

114 + - use the `vX.Y.Z(-RCN)` tag

115 + - link to the release issue

116 + - copy the changelog (without the header) in the description

117 + - do **NOT** check the `This is a pre-release` checkbox

118 + - [ ] run the [sync-release-assets](https://github.com/ipfs/kubo/actions/workflows/sync-release-assets.yml) workflow

119 + - [ ] wait for the [sync-release-assets](https://github.com/ipfs/kubo/actions/workflows/sync-release-assets.yml) workflow run to finish

120 + - [ ] verify the release assets are present in the [GitHub release](https://github.com/ipfs/kubo/releases/tag/vX.Y.Z(-RCN))

121 +- [ ] Notify the bifrost team about the release using `kuboreleaser release --version vX.Y.Z(-RCN) notify-bifrost --date YYYY-MM-DD`

122 + - [ ] create an issue comment on the issue in the [bifrost-infra](https://github/com/protocol/bifrost-infra)

123 +- [ ] Promote the release using `kuboreleaser release --version vX.Y.Z(-RCN) promote`

124 + - [ ] create an [IPFS Discourse](https://discuss.ipfs.tech) topic

125 + - [prerelease example](https://discuss.ipfs.tech/t/kubo-v0-16-0-rc1-release-candidate-is-out/15248)

126 + - [release example](https://discuss.ipfs.tech/t/kubo-v0-16-0-release-is-out/15249)

127 + - use `Kubo vX.Y.Z(-RCN) is out!` as the title

128 + - use `kubo` and `go-ipfs` as topics

129 + - repeat the title as a heading (`##`) in the description

130 + - link to the GitHub Release, binaries on IPNS, docker pull command and release notes in the description

131 + - [ ] pin the [IPFS Discourse](https://discuss.ipfs.tech) topic globally

132 + - you can make the topic a banner if there is no banner already

133 + - verify the [IPFS Discourse](https://discuss.ipfs.tech) topic was copied to:

134 + - [ ] [#ipfs-chatter](https://discord.com/channels/669268347736686612/669268347736686615) in IPFS Discord

135 + - [ ] [#ipfs-chatter](https://filecoinproject.slack.com/archives/C018EJ8LWH1) in FIL Slack

136 + - [ ] [#ipfs-chatter:ipfs.io](https://matrix.to/#/#ipfs-chatter:ipfs.io) in Matrix

137 + - [ ] create an issue comment mentioning early testers on the release issue

138 + - [example](https://github.com/ipfs/kubo/issues/9319#issuecomment-1311002478)

139 + - [ ] create an issue comment linking to the release on the release issue

140 + - [example](https://github.com/ipfs/kubo/issues/9417#issuecomment-1400740975)

141 + - [ ] ask the marketing team to tweet about the release in [#shared-pl-marketing-requests](https://filecoinproject.slack.com/archives/C018EJ8LWH1) in FIL Slack

142 + - [example](https://filecoinproject.slack.com/archives/C018EJ8LWH1/p1664885305374900)

143 + - [ ] post the link to the [GitHub Release](https://github.com/ipfs/kubo/releases/tag/vX.Y.Z(-RCN)) to [Reddit](https://reddit.com/r/ipfs)

144 + - [example](https://www.reddit.com/r/ipfs/comments/9x0q0k/kubo_v0160_release_is_out/)

145 +- [ ] Add the link to the [IPFS Discourse](https://discuss.ipfs.tech) topic to the [GitHub Release](https://github.com/ipfs/kubo/releases/tag/vX.Y.Z(-RCN)) description

146 + - [example](https://github.com/ipfs/kubo/releases/tag/v0.17.0)

147 - [ ] `kuboreleaser release --version vX.Y.Z(-RCN) test-ipfs-companion`

145 - - [ ] Start kubo daemon of the version to release.

146 - - [ ] Start a fresh chromium or chrome instance using `chromium --user-data-dir=$(mktemp -d)` (macos `/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --user-data-dir=$(mktemp -d)`)

147 - - [ ] Start a fresh firefox instance using `firefox --profile $(mktemp -d)` (macos `/Applications/Firefox.app/Contents/MacOS/firefox --profile $(mktemp -d)`)

148 - - [ ] Install IPFS Companion from [vendor-specific store](https://github.com/ipfs/ipfs-companion/#readme).

149 - - [ ] Check that the comunication between Kubo daemon and IPFS companion is working properly checking if the number of connected peers changes.

150 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) update-interop`

151 - - [ ] Upgrade to the RC in [ipfs-desktop](https://github.com/ipfs-shipyard/ipfs-desktop)

152 - - [ ] Run `npm install` to update `package-lock.json`.

153 - - [ ] Push to a branch

154 - - [ ] Open a PR

155 - - [ ] Ensure CI tests pass

156 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) update-ipfs-desktop`

157 - - [ ] Upgrade to the RC in [ipfs-desktop](https://github.com/ipfs-shipyard/ipfs-desktop)

158 - - [ ] Run `npm install` to update `package-lock.json`.

159 - - [ ] Push to a branch ([example](https://github.com/ipfs/ipfs-desktop/pull/1826/commits/b0a23db31ce942b46d95965ee6fe770fb24d6bde))

160 - - [ ] Open a draft PR to track through the final release ([example](https://github.com/ipfs/ipfs-desktop/pull/1826))

161 - - [ ] Mark the PR as ready for review

162 - - [ ] Ensure CI tests pass

163 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) update-ipfs-docs`

164 - - [ ] Run https://github.com/ipfs/ipfs-docs/actions/workflows/update-on-new-ipfs-tag.yml to generate a PR to the docs repo

165 - - [ ] Merge the auto-created PR in https://github.com/ipfs/ipfs-docs/pulls ([example](https://github.com/ipfs/ipfs-docs/pull/1263))

166 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) update-ipfs-blog --date YYYY-MM-DD`

167 - - [ ] Submit a request for blog post creation using [the form](https://airtable.com/shrNH8YWole1xc70I).

168 - - Title: Just released: Kubo X.Y.Z!

169 - - Link type: Release notes

170 - - URL: https://github.com/ipfs/kubo/releases/tag/vX.Y.Z

171 - - [ ] The post is live on https://blog.ipfs.io

172 -- [ ] Infrastructure Testing (see [Kubo Gateway Release Notes](https://www.notion.so/pl-strflt/Kubo-Gateway-Release-Notes-6e0efff28ee540be9ccb8f2b85104c42) by bifrost team if you want to learn more about the process).

173 - - Check [metrics](https://protocollabs.grafana.net/d/8zlhkKTZk/gateway-slis-precomputed?orgId=1) every day.

174 - - Compare the metrics trends week over week.

175 - - If there is an unexpected variation in the trend, message the #bifrost channel on FIL Slack and ask for help investigation the cause.

176 -- [ ] `kuboreleaser release --version vX.Y.Z(-RCN) merge-branch`

177 - - [ ] Merge the `release` branch back into `master`, ignoring the changes to `version.go` (keep the `-dev` version from master).

178 -- [ ] Prepare changelog proposal in [docs/changelogs/vX.Y.md](https://github.com/ipfs/kubo/blob/master/docs/changelogs/).

179 - - Skip filling out the `### Changelog` section (the one where which lists all the commits and contributors) for now. We will populate it after the release branch is cut.

180 - - Ensure the new changelog is linked in the [CHANGELOG.md](CHANGELOG.md) file.

181 -- [ ] Create an issue using this release issue template for the _next_ release.

182 -- [ ] Close this release issue.

148 + - [ ] run the [e2e](https://github.com/ipfs/ipfs-companion/actions/workflows/e2e.yml)

149 + - use `vX.Y.Z(-RCN)` as the Kubo image version

150 + - [ ] wait for the [e2e](https://github.com/ipfs/ipfs-companion/actions/workflows/e2e.yml) workflow run to finish

151 +- [ ] Update Kubo in [interop](https://github.com/ipfs/interop) using `kuboreleaser release --version vX.Y.Z(-RCN) update-interop`

152 + - [ ] check out [ipfs/interop](https://github.com/ipfs/interop)

153 + - [ ] run `npm install`

154 + - [ ] create a PR which updates `package.json` and `package-lock.json`

155 + - [ ] merge the PR

156 +- [ ] Update Kubo in [ipfs-desktop](https://github.com/ipfs/ipfs-desktop) using `kuboreleaser release --version vX.Y.Z(-RCN) update-ipfs-desktop`

157 + - [ ] check out [ipfs/ipfs-desktop](https://github.com/ipfs/ipfs-desktop)

158 + - [ ] run `npm install`

159 + - [ ] create a PR which updates `package.json` and `package-lock.json`

160 + - [ ] merge the PR

161 +- [ ] Update Kubo docs using `kuboreleaser release --version vX.Y.Z(-RCN) update-ipfs-docs`

162 + - [ ] run the [update-on-new-ipfs-tag.yml](https://github.com/ipfs/ipfs-docs/actions/workflows/update-on-new-ipfs-tag.yml) workflow

163 + - [ ] merge the PR created by the [update-on-new-ipfs-tag.yml](https://github.com/ipfs/ipfs-docs/actions/workflows/update-on-new-ipfs-tag.yml) workflow run

164 +- [ ] Create a blog entry on [ipfs.tech](https://blog.ipfs.tech) `kuboreleaser release --version vX.Y.Z(-RCN) update-ipfs-blog --date YYYY-MM-DD`

165 + - [ ] create a PR which adds a release note for the new Kubo version

166 + - [example](https://github.com/ipfs/ipfs-blog/pull/529)

167 + - [ ] merge the PR

168 + - [ ] verify the blog entry was published

169 +- [ ] Keep checking the [metrics](https://protocollabs.grafana.net/d/8zlhkKTZk/gateway-slis-precomputed?orgId=1) until the release issue is closed

170 + - [release notes](https://www.notion.so/pl-strflt/Kubo-Gateway-Release-Notes-6e0efff28ee540be9ccb8f2b85104c42)

171 + - post in the [#bifrost](https://filecoinproject.slack.com/archives/C018EJ8LWH1) channel in FIL Slack if there is a problem

172 +- [ ] Merge the [release](https://github.com/ipfs/kubo/tree/release) back into [master](https://github.com/ipfs/kubo/tree/master) using `kuboreleaser release --version vX.Y.Z(-RCN) merge-branch`

173 + - ignore the changes to [version.go](version.go) (keep the `-dev` version)

174 +- [ ] Create the next [changelog](https://github.com/ipfs/kubo/blob/master/docs/changelogs/vX.(Y+1).md)

175 + - link to the new changelog in the [CHANGELOG.md](CHANGELOG.md) file

176 +- [ ] Create the next release issue

177 +- [ ] Close the release issue

178

179 ## How to contribute?

180

chore: reword release checklist