mirror of
https://github.com/ipfs/kubo.git
synced 2026-02-21 10:27:46 +08:00
Part of https://github.com/protocol/bifrost-infra/issues/2018 ensures the domain used for fetching migrations is not impacted by ipfs.io being blocked at DNS level by some ISPs.
2.0 KiB
2.0 KiB
Patch Release Checklist
This process handles patch releases from version vX.Y.Z to vX.Y.Z+1 assuming that vX.Y.Z is the latest released version of Kubo.
- Get temporary permissions to force-push to
release-*branches - Fork a new branch (
release-vX.Y.Z) fromreleaseand cherry-pick the relevant commits from master (or custom fixes) onto this branch- Use
git cherry-pick -xso that the commit message says(cherry picked from commit ...)
- Use
- Make a minimal changelog update tracking the relevant fixes to CHANGELOG, as its own commit e.g.
docs: update changelog vX.Y.Z+1 - version string in
version.gohas been updated (in therelease-vX.Y.Z+1branch), as its own commit. - Make a PR merging
release-vX.Y.Z+1into the release branch- This may be unnecessary, e.g. for backports
- Tag the merge commit in the
releasebranch withvX.Y.Z+1(ensure the tag is signed) - Upload to dist.ipfs.tech
- Build: https://github.com/ipfs/distributions#usage.
- Pin the resulting release.
- Make a PR against ipfs/distributions with the updated versions, including the new hash in the PR comment.
- Ask the infra team to update the DNSLink record for dist.ipfs.tech to point to the new distribution.
- cut a release on github and upload the result of the ipfs/distributions build in the previous step.
- Announce the Release:
- On IRC/Matrix (both #ipfs and #ipfs-dev)
- On discuss.ipfs.io
- Release published
- to dist.ipfs.tech
- to npm-go-ipfs
- to chocolatey
- to snap
- to github
- to arch (flag it out of date)
- Cut a new ipfs-desktop release
- Merge the
releasebranch back intomaster, ignoring the changes toversion.go(keep the-devversion from master).