Release 0.32

[gammazero]

Meta

• Release owner: @lidel
• Release reviewer: @gammazero
• Expected RC1 date: Wed 30th
• Expected RC2 date: Wed 6th
• 🚢 Expected final release date: Wed 13th
• Release PR: https://github.com/ipfs/kubo/pull/10563
• Accompanying PR for improving the release process: https://github.com/ipfs/kubo/pull/10564
• Internal Staging tests by Shipyard: https://www.notion.so/Kubo-0-31-0-vs-0-32-0-12f1def3428780c0acd4cbdb4b14598a
• Changelog: https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.32.md

Items In Scope

Required

• [x] https://github.com/ipfs/kubo/pull/10548
• [x] https://github.com/ipfs/kubo/pull/10521
  • as opt-in for now

Fixes for things found in RC:

• [x] https://github.com/ipfs/kubo/pull/10566
• [x] https://github.com/ipfs/kubo/security/dependabot/99
• [x] https://github.com/ipfs/kubo/pull/10569
• [x] AutoTLS:https://github.com/ipshipyard/p2p-forge/pull/4
• [x] https://github.com/ipfs/kubo/pull/10571
• [x] https://github.com/ipfs/kubo/pull/10572
• [x] https://github.com/ipfs/kubo/pull/10574
• [x] https://github.com/ipfs/kubo/pull/10578

Nice To Have (Optional)

• [x] https://github.com/ipfs/distributions/pull/1108
• [ ] AutoTLS https://github.com/ipshipyard/p2p-forge/issues/8#issuecomment-2461056901
• [ ] AutoTLS on the same port as raw TCP if we have go-ipfs release with https://github.com/libp2p/go-libp2p/issues/2684
• [ ] AutoTLS: https://github.com/ipfs/kubo/issues/10570
• [ ] AutoTLS: add flag for adding catch-all listener without touching swarm listeners in config
• [x] https://github.com/ipfs/kubo/pull/10568
• [ ] Denylist support fixes and improvements
  • [ ] https://github.com/ipfs-shipyard/nopfs/issues/40
  • [ ] https://github.com/ipfs-shipyard/nopfs/issues/34 (NOfs content filtering is not applied to bitswap)
  • [ ] https://github.com/ipfs/rainbow/issues/126 (same applies to Kubo)
  • [ ] https://github.com/ipfs/kubo/issues/10361
  • [ ] https://github.com/ipfs-shipyard/nopfs/issues/39
  • [ ] https://github.com/ipfs-shipyard/nopfs/issues/38
• [ ] https://github.com/ipfs/kubo/pull/9684 + update to v0.12.0 with GossipSub v1.2
• [ ] https://github.com/ipfs/kubo/issues/10331
• [ ] https://github.com/ipfs/boxo/pull/665 disabled by default, with opt-in variable similar to this or this
• [ ] https://github.com/ipfs/kubo/issues/10513
• [ ] https://github.com/ipfs/boxo/issues/673

Closes #9323

[lidel]

✅ Release Checklist (v0.32.0-rc1)

• [x] merge https://github.com/ipfs/kubo/pull/10562
  • [x] resolve CI issues (pinged IPDX)
• [x] Prepare the release branch and update version numbers accordingly
  using ./kuboreleaser --skip-check-before release --version vX.Y.Z(-rcN) prepare-branch or ...

  • [x] create a new branch release-vX.Y.Z
  • use master as base if Z == 0
  • use release as base if Z > 0
  • [x] update the CurrentVersionNumber in version.go in the master branch to vX.Y+1.0-dev
  • example
  • [x] update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-RCN)
  • example
  • [x] create a draft PR from release-vX.Y to release
  • example
  • [ ] Cherry-pick commits from master to the release-vX.Y.Z using git cherry-pick -x <commit>
  • [ ] Add full changelog and contributors to the changelog
  • [ ] Replace the Changelog and Contributors sections of the changelog with the stdout of ./bin/mkreleaselog. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
    • do NOT copy the stderr
  • [x] verify all CI checks on the PR from release-vX.Y to release are passing
  • [ ] Merge the PR from release-vX.Y to release 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
  • do NOT delete the release-vX.Y branch

[x] Create the release tag

using ./kuboreleaser release --version vX.Y.Z(-rcN) tag or ...

• This is a dangerous operation! Go and Docker publishing are difficult to reverse! Have the release reviewer verify all the commands marked with ⚠️!
• [x] ⚠️ tag the HEAD commit using git tag -s vX.Y.Z(-RCN) -m 'Prerelease X.Y.Z(-RCN)'
• [ ] ⚠️ tag the HEAD commit of the release branch using git tag -s vX.Y.Z -m 'Release X.Y.Z'
• [x] ⚠️ verify the tag is signed and tied to the correct commit using git show vX.Y.Z(-RCN)
• [x] ⚠️ push the tag to GitHub using git push origin vX.Y.Z(-RCN)
• do NOT use git push --tags because it pushes all your local tags

[x] Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).

[x] Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:

• [x] Publish the release to DockerHub
  using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
• [ ] Wait for Publish docker image workflow run initiated by the tag push to finish
• [ ] verify the image is available on Docker Hub
• [x] Publish the release to dist.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
• [ ] check out ipfs/distributions
• [x] create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
• [x] run ./dist.sh add-version kubo vX.Y.Z(-RCN) to add the new version to the versions file
  • usage
• [ ] create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
  • example
• [ ] wait for the CI workflow run initiated by the merge to master to finish
• [ ] verify the release is available on dist.ipfs.tech
• [x] Publish the release to NPM
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-npm (⚠️ you might need to run the command a couple of times because GHA might not be able to see the new distribution straight away due to caching) or ...
• [ ] run the Release to npm workflow
• [ ] check Release to npm workflow run logs to verify it discovered the new release
• [ ] verify the release is available on NPM
• [x] Publish the release to GitHub
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-github or ...
• [x] create a new release on GitHub
  • RC example
  • FINAL example
  • [x] use the vX.Y.Z(-RCN) tag
  • [x] link to the release issue
  • [x] link to the changelog in the description
  • [x] check the This is a pre-release checkbox
  • [ ] copy the changelog (without the header) in the description
  • [ ] do NOT check the This is a pre-release checkbox
• [x] run the sync-release-assets workflow
• [x] wait for the sync-release-assets workflow run to finish
• [x] verify the release assets are present in the GitHub release

[ ] Update Kubo staging environment, see the Running Kubo tests on staging for details.

• [ ] Test last release against the current RC
• [ ] Test last release against the current one

[x] Promote the release

using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...

• [x] create an IPFS Discourse topic
• prerelease example
• release example
• [ ] use Kubo vX.Y.Z(-RCN) is out! as the title
• [ ] use kubo and go-ipfs as topics
• [ ] 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
• [x] pin the IPFS Discourse topic globally
• you can make the topic a banner if there is no banner already
• verify the IPFS Discourse topic was copied to:
• [ ] #ipfs-chatter in IPFS Discord
• [ ] #ipfs-chatter in FIL Slack
• [ ] #ipfs-chatter:ipfs.io in Matrix
• [ ] Add the link to the IPFS Discourse topic to the GitHub Release description
• example
• [x] create an issue comment mentioning early testers on the release issue
• example
• [ ] create an issue comment linking to the release on the release issue
• example
• [ ] ask the marketing team to tweet about the release in #shared-pl-marketing-requests in FIL Slack
• example
• [ ] post the link to the GitHub Release to Reddit
• example

[ ] Test the new version with ipfs-companion (currently skipped)

using ./kuboreleaser release --version vX.Y.Z(-rcN) test-ipfs-companion or ...

• [ ] run the e2e
• use vX.Y.Z(-RCN) as the Kubo image version
• [ ] wait for the e2e workflow run to finish

[ ] Update Kubo in ipfs-desktop

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-desktop or ...

• [ ] check out ipfs/ipfs-desktop
• [ ] run npm install
• [ ] create a PR which updates package.json and package-lock.json
• [ ] add @SgtPooki as reviewer

[ ] Update Kubo docs

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...

• [ ] run the update-on-new-ipfs-tag.yml workflow
• [ ] merge the PR created by the update-on-new-ipfs-tag.yml workflow run

[ ] Create a blog entry on blog.ipfs.tech

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-blog --date YYYY-MM-DD or ...

• [ ] create a PR which adds a release note for the new Kubo version
• example
• [ ] merge the PR
• [ ] verify the blog entry was published

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

using ./kuboreleaser release --version vX.Y.Z(-rcN) merge-branch or ...

• [ ] create a new branch merge-release-vX.Y.Z from release
• [ ] create and merge a PR from merge-release-vX.Y.Z to master

[ ] Prepare for the next release

using ./kuboreleaser release --version vX.Y.Z(-rcN) prepare-next or ...

• [ ] Create the next changelog
• [ ] Link to the new changelog in the CHANGELOG.md file
• [ ] Create the next release issue

[ ] Create a dependency update PR

• [ ] check out ipfs/kubo
• [ ] go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
• [ ] run make mod_tidy
• [ ] create a PR which updates go.mod and go.sum
• [ ] add the PR to the next release milestone

[ ] Close the release issue

[lidel]

Early testers ping for v0.32.0-rc1 testing ✨ If you have spare time, and don't have /ws listener enabled yet, give AutoTLS a try.

• [ ] Charity Engine (@rytiss, @tristanolive)
• [ ] Fission (@bmann)
• [ ] Infura (@MichaelMure)
• [ ] OrbitDB (@haydenyoung)
• [ ] Pinata (@obo20)
• [ ] Shipyard (@cewood, @ns4plabs)
• [ ] Siderus (@koalalorenzo)
• [ ] Textile (@sanderpick)
• [ ] @RubenKelevra

You're getting this message because you're listed here. Please update this list if you no longer want to be included.

[lidel]

✅ Release Checklist (v0.32.0-rc2)

• [x] Prepare the release branch and update version numbers accordingly
  using ./kuboreleaser --skip-check-before release --version vX.Y.Z(-rcN) prepare-branch or ...

  • [ ] create a new branch release-vX.Y.Z
  • use master as base if Z == 0
  • use release as base if Z > 0
  • [ ] update the CurrentVersionNumber in version.go in the master branch to vX.Y+1.0-dev
  • example
  • [x] update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-rcN)
  • example
  • [ ] create a draft PR from release-vX.Y to release
  • example
  • [x] Cherry-pick commits from master to the release-vX.Y.Z using git cherry-pick -x <commit>
  • [ ] Add full changelog and contributors to the changelog
  • [ ] Replace the Changelog and Contributors sections of the changelog with the stdout of ./bin/mkreleaselog. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
    • do NOT copy the stderr
  • [x] verify all CI checks on the PR from release-vX.Y to release are passing
  • [ ] Merge the PR from release-vX.Y to release 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
  • do NOT delete the release-vX.Y branch

[x] Create the release tag

using ./kuboreleaser release --version vX.Y.Z(-rcN) tag or ...

• This is a dangerous operation! Go and Docker publishing are difficult to reverse! Have the release reviewer verify all the commands marked with ⚠️!
• [x] ⚠️ tag the HEAD commit using git tag -s vX.Y.Z(-rcN) -m 'Prerelease X.Y.Z(-rcN)'
• [ ] ⚠️ tag the HEAD commit of the release branch using git tag -s vX.Y.Z -m 'Release X.Y.Z'
• [x] ⚠️ verify the tag is signed and tied to the correct commit using git show vX.Y.Z(-rcN)
• [x] ⚠️ push the tag to GitHub using git push origin vX.Y.Z(-rcN)
• do NOT use git push --tags because it pushes all your local tags

[x] Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).

[ ] Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:

• [x] Publish the release to DockerHub
  using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
• [ ] Wait for Publish docker image workflow run initiated by the tag push to finish
• [ ] verify the image is available on Docker Hub
• [x] Publish the release to dist.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
• [ ] check out ipfs/distributions
• [ ] create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
• [ ] run ./dist.sh add-version kubo vX.Y.Z(-rcN) to add the new version to the versions file
  • usage
• [ ] create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
  • example
• [ ] wait for the CI workflow run initiated by the merge to master to finish
• [ ] verify the release is available on dist.ipfs.tech
• [x] Publish the release to NPM
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-npm (⚠️ you might need to run the command a couple of times because GHA might not be able to see the new distribution straight away due to caching) or ...
• [ ] run the Release to npm workflow
• [ ] check Release to npm workflow run logs to verify it discovered the new release
• [ ] verify the release is available on NPM
• [x] Publish the release to GitHub
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-github or ...
• [x] create a new release on GitHub
  • RC example
  • FINAL example
  • [ ] use the vX.Y.Z(-rcN) tag
  • [ ] link to the release issue
  • [ ] link to the changelog in the description
  • [ ] check the This is a pre-release checkbox
  • [ ] copy the changelog (without the header) in the description
  • [ ] do NOT check the This is a pre-release checkbox
• [x] run the sync-release-assets workflow
• [x] wait for the sync-release-assets workflow run to finish
• [x] verify the release assets are present in the GitHub release

[ ] Update Kubo staging environment, see the Running Kubo tests on staging for details.

• [ ] Test last release against the current RC
• [ ] Test last release against the current one

[x] Promote the release

using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...

• [ ] create an IPFS Discourse topic
• prerelease example
• release example
• [ ] use Kubo vX.Y.Z(-rcN) is out! as the title
• [ ] use kubo and go-ipfs as topics
• [ ] 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
• [ ] pin the IPFS Discourse topic globally
• you can make the topic a banner if there is no banner already
• verify the IPFS Discourse topic was copied to:
• [ ] #ipfs-chatter in IPFS Discord
• [ ] #ipfs-chatter in FIL Slack
• [ ] #ipfs-chatter:ipfs.io in Matrix
• [ ] Add the link to the IPFS Discourse topic to the GitHub Release description
• example
• [ ] create an issue comment mentioning early testers on the release issue
• example
• [ ] create an issue comment linking to the release on the release issue
• example
• [ ] ask the marketing team to tweet about the release in #shared-pl-marketing-requests in FIL Slack
• example
• [ ] post the link to the GitHub Release to Reddit
• example

[ ] Test the new version with ipfs-companion (currently skipped)

using ./kuboreleaser release --version vX.Y.Z(-rcN) test-ipfs-companion or ...

• [ ] run the e2e
• use vX.Y.Z(-rcN) as the Kubo image version
• [ ] wait for the e2e workflow run to finish

[ ] Update Kubo in ipfs-desktop

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-desktop or ...

• [ ] check out ipfs/ipfs-desktop
• [ ] run npm install
• [ ] create a PR which updates package.json and package-lock.json
• [ ] add @SgtPooki as reviewer

[ ] Update Kubo docs

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...

• [ ] run the update-on-new-ipfs-tag.yml workflow
• [ ] merge the PR created by the update-on-new-ipfs-tag.yml workflow run

[ ] Create a blog entry on blog.ipfs.tech

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-blog --date YYYY-MM-DD or ...

• [ ] create a PR which adds a release note for the new Kubo version
• example
• [ ] merge the PR
• [ ] verify the blog entry was published

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

using ./kuboreleaser release --version vX.Y.Z(-rcN) merge-branch or ...

• [ ] create a new branch merge-release-vX.Y.Z from release
• [ ] create and merge a PR from merge-release-vX.Y.Z to master

[ ] Prepare for the next release

using ./kuboreleaser release --version vX.Y.Z(-rcN) prepare-next or ...

• [ ] Create the next changelog
• [ ] Link to the new changelog in the CHANGELOG.md file
• [ ] Create the next release issue

[ ] Create a dependency update PR

• [ ] check out ipfs/kubo
• [ ] go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
• [ ] run make mod_tidy
• [ ] create a PR which updates go.mod and go.sum
• [ ] add the PR to the next release milestone

[ ] Close the release issue

[lidel]

0.32.0-rc2 is ready

[lidel]

✅ Release Checklist (v0.32.0)

• [x] Prepare the release branch and update version numbers accordingly
  using ./kuboreleaser --skip-check-before release --version vX.Y.Z(-rcN) prepare-branch or ...

  • [ ] create a new branch release-vX.Y.Z
  • use master as base if Z == 0
  • use release as base if Z > 0
  • [ ] update the CurrentVersionNumber in version.go in the master branch to vX.Y+1.0-dev
  • example
  • [x] update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-rcN)
  • example
  • [ ] create a draft PR from release-vX.Y to release
  • example
  • [x] Cherry-pick commits from master to the release-vX.Y.Z using git cherry-pick -x <commit>
  • [x] Add full changelog and contributors to the changelog
  • [x] Replace the Changelog and Contributors sections of the changelog with the stdout of ./bin/mkreleaselog. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
    • do NOT copy the stderr
  • [x] verify all CI checks on the PR from release-vX.Y to release are passing
  • [x] Merge the PR from release-vX.Y to release 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
  • do NOT delete the release-vX.Y branch

[x] Create the release tag

using ./kuboreleaser release --version vX.Y.Z(-rcN) tag or ...

• This is a dangerous operation! Go and Docker publishing are difficult to reverse! Have the release reviewer verify all the commands marked with ⚠️!
• [ ] ⚠️ tag the HEAD commit using git tag -s vX.Y.Z(-rcN) -m 'Prerelease X.Y.Z(-rcN)'
• [x] ⚠️ tag the HEAD commit of the release branch using git tag -s vX.Y.Z -m 'Release X.Y.Z'
• [x] ⚠️ verify the tag is signed and tied to the correct commit using git show vX.Y.Z(-rcN)
• [x] ⚠️ push the tag to GitHub using git push origin vX.Y.Z(-rcN)
• do NOT use git push --tags because it pushes all your local tags

[x] Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).

[x] Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:

• [x] Publish the release to DockerHub
  using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
• [ ] Wait for Publish docker image workflow run initiated by the tag push to finish
• [x] verify the image is available on Docker Hub
• [x] Publish the release to dist.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
• [ ] check out ipfs/distributions
• [ ] create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
• [x] run ./dist.sh add-version kubo vX.Y.Z(-rcN) to add the new version to the versions file
  • usage
• [ ] create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
  • example
• [ ] wait for the CI workflow run initiated by the merge to master to finish
• [ ] verify the release is available on dist.ipfs.tech
• [x] Publish the release to NPM
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-npm (⚠️ you might need to run the command a couple of times because GHA might not be able to see the new distribution straight away due to caching) or ...
• [ ] run the Release to npm workflow
• [ ] check Release to npm workflow run logs to verify it discovered the new release
• [ ] verify the release is available on NPM
• [x] Publish the release to GitHub
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-github or ...
• [x] create a new release on GitHub
  • RC example
  • FINAL example
  • [ ] use the vX.Y.Z(-rcN) tag
  • [ ] link to the release issue
  • [ ] link to the changelog in the description
  • [ ] check the This is a pre-release checkbox
  • [x] copy the changelog (without the header) in the description
  • [ ] do NOT check the This is a pre-release checkbox
• [ ] run the sync-release-assets workflow
• [ ] wait for the sync-release-assets workflow run to finish
• [ ] verify the release assets are present in the GitHub release

[x] Update Kubo staging environment, see the Running Kubo tests on staging for details.

• [ ] Test last release against the current RC
• [x] Test last release against the current one

[x] Promote the release

using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...

• [x] create an IPFS Discourse topic
• prerelease example
• release example
• [ ] use Kubo vX.Y.Z(-rcN) is out! as the title
• [ ] use kubo and go-ipfs as topics
• [ ] 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
• [x] pin the IPFS Discourse topic globally
• you can make the topic a banner if there is no banner already
• verify the IPFS Discourse topic was copied to:
• [ ] #ipfs-chatter in IPFS Discord
• [ ] #ipfs-chatter in FIL Slack
• [ ] #ipfs-chatter:ipfs.io in Matrix
• [x] Add the link to the IPFS Discourse topic to the GitHub Release description
• example
• [ ] create an issue comment mentioning early testers on the release issue
• example
• [x] create an issue comment linking to the release on the release issue
• example
• [ ] ask the marketing team to tweet about the release in #shared-pl-marketing-requests in FIL Slack
• example
• [x] post the link to the GitHub Release to Reddit
• example

[ ] Test the new version with ipfs-companion (currently skipped)

using ./kuboreleaser release --version vX.Y.Z(-rcN) test-ipfs-companion or ...

• [ ] run the e2e
• use vX.Y.Z(-rcN) as the Kubo image version
• [ ] wait for the e2e workflow run to finish

[x] Update Kubo in ipfs-desktop

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-desktop or ...

• [ ] check out ipfs/ipfs-desktop
• [ ] run npm install
• [ ] create a PR which updates package.json and package-lock.json
• [ ] add @SgtPooki as reviewer

[x] Update Kubo docs

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...

• [x] run the update-on-new-ipfs-tag.yml workflow
• [x] merge the PR created by the update-on-new-ipfs-tag.yml workflow run

[x] Create a blog entry on blog.ipfs.tech

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-blog --date YYYY-MM-DD or ...

• [ ] create a PR which adds a release note for the new Kubo version
• example
• [ ] merge the PR
• [ ] verify the blog entry was published

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

using ./kuboreleaser release --version vX.Y.Z(-rcN) merge-branch or ...

• [x] create a new branch merge-release-vX.Y.Z from release
• [ ] create and merge a PR from merge-release-vX.Y.Z to master

[x] Prepare for the next release

using ./kuboreleaser release --version vX.Y.Z(-rcN) prepare-next or ...

• [x] Create the next changelog
• [x] Link to the new changelog in the CHANGELOG.md file
• [x] Create the next release issue

[ ] Create a dependency update PR

• [ ] check out ipfs/kubo
• [ ] go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
• [ ] run make mod_tidy
• [ ] create a PR which updates go.mod and go.sum
• [ ] add the PR to the next release milestone

[x] Close the release issue

[lidel]

Kubo v0.32.0 is out!

[lidel]

Making patch with fix from #10581 (to restore accelerated dht client)

✅ Release Checklist v0.32.1

• [x] Prepare the release branch and update version numbers accordingly
  using ./kuboreleaser --skip-check-before release --version vX.Y.Z(-rcN) prepare-branch or ...

  • [x] create a new branch release-vX.Y.Z
  • use master as base if Z == 0
  • use release as base if Z > 0
  • [ ] update the CurrentVersionNumber in version.go in the master branch to vX.Y+1.0-dev
  • example
  • [x] update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-rcN)
  • example
  • [ ] create a draft PR from release-vX.Y to release
  • example
  • [x] Cherry-pick commits from master to the release-vX.Y.Z using git cherry-pick -x <commit>
  • [ ] Add full changelog and contributors to the changelog
  • [ ] Replace the Changelog and Contributors sections of the changelog with the stdout of ./bin/mkreleaselog. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
    • do NOT copy the stderr
  • [x] verify all CI checks on the PR from release-vX.Y to release are passing
  • [x] Merge the PR from release-vX.Y to release 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
  • do NOT delete the release-vX.Y branch

[x] Create the release tag

using ./kuboreleaser release --version vX.Y.Z(-rcN) tag or ...

• This is a dangerous operation! Go and Docker publishing are difficult to reverse! Have the release reviewer verify all the commands marked with ⚠️!
• [ ] ⚠️ tag the HEAD commit using git tag -s vX.Y.Z(-rcN) -m 'Prerelease X.Y.Z(-rcN)'
• [x] ⚠️ tag the HEAD commit of the release branch using git tag -s vX.Y.Z -m 'Release X.Y.Z'
• [x] ⚠️ verify the tag is signed and tied to the correct commit using git show vX.Y.Z(-rcN)
• [x] ⚠️ push the tag to GitHub using git push origin vX.Y.Z(-rcN)
• do NOT use git push --tags because it pushes all your local tags

[x] Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).

[ ] Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:

• [x] Publish the release to DockerHub
  using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
• [ ] Wait for Publish docker image workflow run initiated by the tag push to finish
• [ ] verify the image is available on Docker Hub
• [x] Publish the release to dist.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
• [ ] check out ipfs/distributions
• [ ] create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
• [ ] run ./dist.sh add-version kubo vX.Y.Z(-rcN) to add the new version to the versions file
  • usage
• [ ] create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
  • example
• [ ] wait for the CI workflow run initiated by the merge to master to finish
• [ ] verify the release is available on dist.ipfs.tech
• [x] Publish the release to NPM
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-npm (⚠️ you might need to run the command a couple of times because GHA might not be able to see the new distribution straight away due to caching) or ...
• [ ] run the Release to npm workflow
• [ ] check Release to npm workflow run logs to verify it discovered the new release
• [ ] verify the release is available on NPM
• [x] Publish the release to GitHub
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-github or ...
• [ ] create a new release on GitHub
  • RC example
  • FINAL example
  • [ ] use the vX.Y.Z(-rcN) tag
  • [ ] link to the release issue
  • [ ] link to the changelog in the description
  • [ ] check the This is a pre-release checkbox
  • [ ] copy the changelog (without the header) in the description
  • [ ] do NOT check the This is a pre-release checkbox
• [ ] run the sync-release-assets workflow
• [ ] wait for the sync-release-assets workflow run to finish
• [ ] verify the release assets are present in the GitHub release

[x] Update Kubo staging environment, see the Running Kubo tests on staging for details.

• [ ] Test last release against the current RC
• [x] Test last release against the current one

[x] Promote the release

using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...

• [x] create an IPFS Discourse topic
• prerelease example
• release example
• [ ] use Kubo vX.Y.Z(-rcN) is out! as the title
• [ ] use kubo and go-ipfs as topics
• [ ] 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
• [x] pin the IPFS Discourse topic globally
• you can make the topic a banner if there is no banner already
• verify the IPFS Discourse topic was copied to:
• [ ] #ipfs-chatter in IPFS Discord
• [ ] #ipfs-chatter in FIL Slack
• [ ] #ipfs-chatter:ipfs.io in Matrix
• [x] Add the link to the IPFS Discourse topic to the GitHub Release description
• example
• [ ] create an issue comment mentioning early testers on the release issue
• example
• [ ] create an issue comment linking to the release on the release issue
• example
• [ ] ask the marketing team to tweet about the release in #shared-pl-marketing-requests in FIL Slack
• example
• [x] post the link to the GitHub Release to Reddit
• example

[ ] Test the new version with ipfs-companion (currently skipped)

using ./kuboreleaser release --version vX.Y.Z(-rcN) test-ipfs-companion or ...

• [ ] run the e2e
• use vX.Y.Z(-rcN) as the Kubo image version
• [ ] wait for the e2e workflow run to finish

[ ] Update Kubo in ipfs-desktop

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-desktop or ...

• [ ] check out ipfs/ipfs-desktop
• [ ] run npm install
• [ ] create a PR which updates package.json and package-lock.json
• [ ] add @SgtPooki as reviewer

[ ] Update Kubo docs

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...

• [ ] run the update-on-new-ipfs-tag.yml workflow
• [ ] merge the PR created by the update-on-new-ipfs-tag.yml workflow run

[ ] Create a blog entry on blog.ipfs.tech

using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-blog --date YYYY-MM-DD or ...

• [ ] create a PR which adds a release note for the new Kubo version
• example
• [ ] merge the PR
• [ ] verify the blog entry was published

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

using ./kuboreleaser release --version vX.Y.Z(-rcN) merge-branch or ...

• [ ] create a new branch merge-release-vX.Y.Z from release
• [ ] create and merge a PR from merge-release-vX.Y.Z to master

[ ] Prepare for the next release

using ./kuboreleaser release --version vX.Y.Z(-rcN) prepare-next or ...

• [ ] Create the next changelog
• [ ] Link to the new changelog in the CHANGELOG.md file
• [ ] Create the next release issue

[ ] Create a dependency update PR

• [ ] check out ipfs/kubo
• [ ] go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
• [ ] run make mod_tidy
• [ ] create a PR which updates go.mod and go.sum
• [ ] add the PR to the next release milestone

[ ] Close the release issue