-
-
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.19 #9502
Comments
placeholder |
Since there are still outstanding items to be completed ahead of the RC, I updated the release schedule. |
2023-02-28 conversation: |
I'll update this specific list later today, but #9684 should be included in the 0.19 train. |
This issue libp2p/go-libp2p#2155 was also raised by @Jorropo as something to include in this kubo release. If so, it can be released as a part go-libp2p 0.26.2 |
Can we include ipfs/go-ipfs-pinner#24 ? |
Update on where we're at with the 0.19 release... The key blocker right now is the resource manager updates as we are in an out-of-date state with our docs and think its better to finish the simplification than documenting more of the current complexity:
Unfortunately there is likely going to be some back and forth this week to fully get the resource manager issue completed. After that, we should be cutting the release. It's a bonus for whatever else has made it in beforehand...
#9619 will get handled as part of the release itself. |
#9688 (a few important dependencies bumps) is needed too. |
Early testers ping for v0.19.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. |
@galargh : I didn't see a "improve 0.19 release process PR" to comment on. Let me know if there is one and I can move comments there:
|
Added a link to the meta section: #9484 We're reusing 0.18.
|
2023-03-07 conversation:
|
Here was the state of the board as part of closing up this release: https://github.com/orgs/ipfs/projects/16/views/1?filterQuery=iteration%3A%22kubo+0.19%22&sortedBy%5Bdirection%5D=desc&sortedBy%5BcolumnId%5D=Status&groupedBy%5BcolumnId%5D=22190186
|
2023-03-09 maintainer conversation Remaining things before 0.19 final release
|
Big thanks to @iand and the Probelab Thunderdom project for the comparisons between 0.19 with 0.18.1: https://www.notion.so/pl-strflt/2023-03-10-ProbeLab-SitRep-a41cbbb2ef564c1298d81061a49e7480?pvs=4#234ff4063f2b4809b3c109774f17009a @galargh : we should be good to do the final release once we get the public rpc command deprecation notice is (tracked in #9717 ). |
@galargh : we can do the final release on 2023-03-16 if:
|
Maintainers will discuss shortly, but we're likely holding up the release until libp2p/go-libp2p#2188 is addressed. |
Status on the 0.19 release:
|
The new release is out: https://github.com/libp2p/go-libp2p/releases/tag/v0.26.3 |
@galargh : we are good to go on doing the 0.19 release on Monday. |
Doh - I'm seeing the 0.19 changelog hasn't been merged: #9707 So two open things:
@galargh : I don't want you be blocked any longer on this release. If @Jorropo hasn't handled #9707 by when you start on this, feel free to resolve/merge. Worst case scenario we come back in later and remove the pubsub comments if the the changelog if they're incorrect. |
🎉 Kubo v0.19.0 is out! |
We should look into the failing Kubo update PR in interop - ipfs/interop#597. All the other steps of the release have been completed successfully. I'll close the issue now. See you again in #9694 |
Meta
2023-02-232023-03-022023-03-062023-02-302023-03-092023-03-13See the Kubo release process for more info.
Kubo 0.19.0 Release
We're happy to announce Kubo 0.19.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
<List of items with PRs and/or Issues to be considered for this release>
Required
Nice to have
🔦 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
using
kuboreleaser release --version v0.19.0(-RCN) notify-bifrost --date YYYY-MM-DD
or ...The release
This section covers tasks to be done during each release.
using
kuboreleaser release --version v0.19.0(-RCN) prepare-branch
or ...release-v0.19.0
master
as base ifZ == 0
release
as base ifZ > 0
CurrentVersionNumber
in version.go in themaster
branch tov0.19+1.0-dev
CurrentVersionNumber
in version.go in therelease-v0.19
branch tov0.19.0(-RCN)
release-v0.19
torelease
master
to therelease-v0.19.0
usinggit cherry-pick -x <commit>
Changelog
andContributors
sections of the changelog with the stdout of./bin/mkreleaselog
release-v0.19
torelease
are passingrelease-v0.19
torelease
using theCreate a merge commit
Squash and merge
norRebase and merge
because we need to be able to sign the merge commitrelease-v0.19
branchusing
kuboreleaser release --version v0.19.0(-RCN) tag
or ...git tag -s v0.19.0(-RCN) -m 'Prerelease 0.19.0(-RCN)'
release
branch usinggit tag -s v0.19.0(-RCN) -m 'Release 0.19.0(-RCN)'
git show v0.19.0(-RCN)
git push origin v0.19.0(-RCN)
git push --tags
because it pushes all your local tagsusing
kuboreleaser --skip-check-before --skip-run release --version v0.19.0(-RCN) publish-to-dockerhub
or ...using
kuboreleaser release --version v0.19.0(-RCN) publish-to-distributions
or ..../dist.sh add-version kubo v0.19.0(-RCN)
to add the new version to theversions
filedists/kubo/versions
anddists/go-ipfs/versions
(dists/kubo/current_version
anddists/go-ipfs/current_version
)using
kuboreleaser release --version v0.19.0(-RCN) publish-to-npm
or ...using
kuboreleaser release --version v0.19.0(-RCN) publish-to-github
or ...v0.19.0(-RCN)
tagThis is a pre-release
checkboxThis is a pre-release
checkboxusing
kuboreleaser release --version v0.19.0(-RCN) notify-bifrost --date YYYY-MM-DD
or ...using
kuboreleaser release --version v0.19.0(-RCN) promote
or ...Kubo v0.19.0(-RCN) is out!
as the titlekubo
andgo-ipfs
as topics##
) in the descriptionipfs-companion
using
kuboreleaser release --version v0.19.0(-RCN) test-ipfs-companion
or ...v0.19.0(-RCN)
as the Kubo image versionusing
kuboreleaser release --version v0.19.0(-RCN) update-interop
or ...npm install
package.json
andpackage-lock.json
using
kuboreleaser release --version v0.19.0(-RCN) update-ipfs-desktop
or ...npm install
package.json
andpackage-lock.json
using
kuboreleaser release --version v0.19.0(-RCN) update-ipfs-docs
or ...using
kuboreleaser release --version v0.19.0(-RCN) update-ipfs-blog --date YYYY-MM-DD
or ...-dev
) version,using
kuboreleaser release --version v0.19.0(-RCN) merge-branch
or ...merge-release-v0.19.0
fromrelease
merge-release-v0.19.0
tomaster
using
kuboreleaser release --version v0.19.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: