- [x] Verify your [GPG signature](https://docs.github.com/en/authentication/managing-commit-signature-verification) is configured in local git and GitHub - [x] Ensure Boxo and Kubo are checked out on your system - [x] Create a release branch called `release-vX.Y.Z` and push it * Use `master` as base if `Z == 0` * Use `release` as base if `Z > 0` - [x] Tidy the changelog and push any changelog changes to `release-vX.Y.Z` - [x] Create a draft PR merging `release-vX.Y.Z` into `release` - [x] Name it "Release vX.Y.Z" - [x] Reference this release issue - [x] If `Z > 0`, then cherry-pick the necessary commits from `master` into `release-vX.Y.Z` using `git cherry-pick -x <commit>` - [x] Ensure Boxo tests are passing - [x] Ensure Kubo tests are passing - [x] Go to Kubo dir and run `go get github.com/ipfs/boxo@<commit_hash>` using the commit hash of the `release-vX.Y.Z` branch - [x] Run `make mod_tidy` in repo root (to apply `go mod tidy` to code, tests, and examples) - [x] Commit the changes and open a draft PR in Kubo - [x] Name the PR "Upgrade to Boxo vX.Y.Z" - [x] Paste a link to the Kubo PR in the Boxo PR, so reviewers can verify the Kubo test run - [x] Verify the CI passes - [x] Add a commit in `release-vX.Y.Z` bumping the version in `version.json` to `vX.Y.Z` - [x] Add a "release" label to the Boxo PR - [x] After the release checker creates a draft release, copy-paste the changelog into the draft - [x] Wait for approval from another Boxo maintainer - [ ] Merge the PR into `release`, _using "Create a Merge Commit"_, and do not delete the `release-vX.Y.X` branch - [ ] Verify the tag is created - [x] Announce the release - [x] Click [this link](https://discuss.ipfs.tech/new-topic?title=Boxo%20vX.Y.Z%20is%20out%21&tags=boxo&category=News&body=%23%23%20Boxo%20vX.Y.Z%20is%20out%21%0A%0ASee%3A%0A-%20Code%3A%20https%3A%2F%2Fgithub.com%2Fipfs%2Fboxo%2Freleases%2Ftag%2FvX.Y.Z%0A-%20Release%20Notes%3A%20https%3A%2F%2Fgithub.com%2Fipfs%2Fboxo%2Fblob%2FvX.Y.Z%2FCHANGELOG.md) to start a new Discourse topic <!--docs: https://meta.discourse.org/t/create-a-link-to-start-a-new-topic-with-pre-filled-information/28074 --> - [x] Update `vX.Y.Z` in the title and body - [x] Create the topic - [x] Create a PR merging `release` into `main` - [ ] Name it "Merge release vX.Y.Z" - [x] Wait for approval - [x] Merge it _using "Create a Merge Commit"_, and do not delete the `release` branch - [x] Update the Kubo PR to use the newly released version, mark it as "Ready for Review", get approval, and merge into Kubo
release-vX.Y.Zand push itmasteras base ifZ == 0releaseas base ifZ > 0release-vX.Y.Zrelease-vX.Y.ZintoreleaseZ > 0, then cherry-pick the necessary commits frommasterintorelease-vX.Y.Zusinggit cherry-pick -x <commit>go get github.com/ipfs/boxo@<commit_hash>using the commit hash of therelease-vX.Y.Zbranchmake mod_tidyin repo root (to applygo mod tidyto code, tests, and examples)release-vX.Y.Zbumping the version inversion.jsontovX.Y.Zrelease, using "Create a Merge Commit", and do not delete therelease-vX.Y.XbranchvX.Y.Zin the title and bodyreleaseintomainreleasebranch