-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 0.20 #9694
Comments
placeholder |
Dependency upgrade PR: #9744 |
I set the expected release date in the issue description. |
Self reminder: add notes in changelog about ipfs/boxo#202 (comment) |
2023-04-04 maintainer conversation: We're still planning to do the RC on 2023-04-05 Blocking:
Stretch (not blocking)
|
Would be great if #9796 could be included. |
Preparing 0.20.md for 0.20 release: #9694
Early testers ping for v0.20.0-rc1 testing π.
You're getting this message because you're listed here. Please update this list if you no longer want to be included. |
2023-04-11 maintainer conversation: We are not going to do a final release on 2023-04-13 (before IPFS Thing). We want to do a Boxo release to bubble up some gateway fixes, and there is likely more metrics that need to be plumbed through due to the refactor. Even if did all that before IPFS Thing, maintainers want to mitigate risk of being distracted during the event due to any issues in the release. As a result, we'll do an RC2 shortly after IPFS Thing 2023-04-25 (best guess currently) and the final release after that (2023-04-27 optimistic guess). We're not going to do the Thunderdome testing now because:
We do still need to land the 0.20 changelog: #9799 Dates in the issue description have been updated. |
Preparing 0.20.md for 0.20 release: #9694
This wasn't present during the intial RC, but the changelog has been filled in now: https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.20.md |
2023-04-19 conversation of remaining steps to close out the relse
|
Early testers ping for v0.20.0-rc2 testing π.
You're getting this message because you're listed here. Please update this list if you no longer want to be included. |
2023-05-04 status update before we release:
Expected release date from what I can see is 2023-05-08. |
We are all clear for the release. It will happen 2023-05-09. |
The libp2p team will try to cut another patch release fixing libp2p/go-libp2p#2259 (which is #9693 on the Kubo side) before noon European time tomorrow. We'll bubble the release up here. |
Release engineers (@hacdias @galargh ): if libp2p/go-libp2p#2259 is merged and a go-libp2p release is made by the time you are doing the 0.20 release, then please include, otherwise, please proceed. My rationale for proceeding without it is:
If it doesn't make it in, we'll absolutely get it in the next release (0.20.1 or 0.21 - whichever comes first). |
Here it is: #9862 |
π Kubo v0.20.0 is out! |
Here was the status of the 0.20 iteration before moving on to 0.21: https://github.com/orgs/ipfs/projects/16/views/1?filterQuery=iteration%3A%22kubo+0.20%22
|
Meta
2023-04-132023-04-27See the Kubo release process for more info.
Kubo 0.20.0 Release
We're happy to announce Kubo 0.20.0!
As usual, this release includes important fixes, some of which may be critical for security. Unless the fix addresses a bug being exploited in the wild, the fix will not be called out in the release notes. Please make sure to update ASAP. See our security fix policy for details.
πΊ What's left for release
traceparent
header support on gateway from feat: boxo tracing and traceparent supportΒ #9811π¦ Highlights
< top highlights for this release notes. For ANY version (final or RCs) >
β Release Checklist
Labels
If an item should be executed for a specific release type, it should be labeled with one of the following labels:
Otherwise, it means it should be executed for ALL release types.
Patch releases should follow the same process as
.0
releases. If some item should NOT be executed for a Patch Release, it should be labeled with:Before the release
This section covers tasks to be done ahead of the release.
$(go env GOPATH)/src/github.com/ipfs/kubo
mkdir -p $(go env GOPATH)/src/github.com/ipfs && ln -s $(pwd) $(go env GOPATH)/src/github.com/ipfs/kubo
The release
This section covers tasks to be done during each release.
using
kuboreleaser release --version v0.20.0(-rcN) prepare-branch
or ...release-v0.20.0
master
as base ifZ == 0
release
as base ifZ > 0
CurrentVersionNumber
in version.go in themaster
branch tov0.21.0-dev
CurrentVersionNumber
in version.go in therelease-v0.20
branch tov0.20.0(-RCN)
release-v0.20
torelease
master
to therelease-v0.20.0
usinggit cherry-pick -x <commit>
Changelog
andContributors
sections of the changelog with the stdout of./bin/mkreleaselog
release-v0.20
torelease
are passingrelease-v0.20
torelease
using theCreate a merge commit
Squash and merge
norRebase and merge
because we need to be able to sign the merge commitrelease-v0.20
branchusing
kuboreleaser release --version v0.20.0(-rcN) tag
or ...git tag -s v0.20.0(-RCN) -m 'Prerelease 0.20.0(-RCN)'
release
branch usinggit tag -s v0.20.0(-RCN) -m 'Release 0.20.0(-RCN)'
git show v0.20.0(-RCN)
git push origin v0.20.0(-RCN)
git push --tags
because it pushes all your local tagsusing
kuboreleaser --skip-check-before --skip-run release --version v0.20.0(-rcN) publish-to-dockerhub
or ...using
kuboreleaser release --version v0.20.0(-rcN) publish-to-distributions
or ..../dist.sh add-version kubo v0.20.0(-RCN)
to add the new version to theversions
filedists/kubo/versions
anddists/go-ipfs/versions
( anddists/kubo/current_version
anddists/go-ipfs/current_version
)using
kuboreleaser release --version v0.20.0(-rcN) publish-to-npm
or ...using
kuboreleaser release --version v0.20.0(-rcN) publish-to-github
or ...v0.20.0(-RCN)
tagThis is a pre-release
checkboxThis is a pre-release
checkboxusing
kuboreleaser release --version v0.20.0(-rcN) promote
or ...Kubo v0.20.0(-RCN) is out!
as the titlekubo
andgo-ipfs
as topics##
) in the descriptionipfs-companion
using
kuboreleaser release --version v0.20.0(-rcN) test-ipfs-companion
or ...v0.20.0(-RCN)
as the Kubo image versionusing
kuboreleaser release --version v0.20.0(-rcN) update-interop
or ...npm install
package.json
andpackage-lock.json
using
kuboreleaser release --version v0.20.0(-rcN) update-ipfs-desktop
or ...npm install
package.json
andpackage-lock.json
using
kuboreleaser release --version v0.20.0(-rcN) update-ipfs-docs
or ...using
kuboreleaser release --version v0.20.0(-rcN) update-ipfs-blog --date YYYY-MM-DD
or ...-dev
) version,using
kuboreleaser release --version v0.20.0(-rcN) merge-branch
or ...merge-release-v0.20.0
fromrelease
merge-release-v0.20.0
tomaster
using
kuboreleaser release --version v0.20.0(-rcN) prepare-next
or ...go get -u
in root directorygo mod tidy
in root directorygo mod tidy
indocs/examples/kubo-as-a-library
directorygo.mod
andgo.sum
How to contribute?
Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:
help wanted
label in the ipfs/kubo repoThe text was updated successfully, but these errors were encountered: