-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Open
Description
🗺 What's left for release
🔦 Highlights
#3384 separates out go-libp2p/core as a separate module. This allows libraries to build against the core interfaces rather than a specific version of go-libp2p.
#3386 shows an outline of how customize a go-libp2p host, and only bring the parts one needs.
Changelog
git log --pretty=format:"%h %s %an <%ae>" v0.44.0..v0.45.0
✅ Release Checklist
- Stage 0 - Finishing Touches
- Go through relevant libp2p repos looking for unreleased changes that should make it into the release. If you find any, cut releases.
- Run
go get -u ./...
to see if there are any out-of-date deps that look important. If there are, bubble them. Try to avoid directly updating indirect deps in go-libp2p'sgo.mod
when possible.
- Stage 1 - Release
- Publish the release through the GitHub UI, adding the release notes. Some users rely on this to receive notifications of new releases.
- Announce the release on the discuss.libp2p.io.
- Stage 2 - Update Upstream
- Update the examples to the final release
- Update the upstream dependencies to the final release and create PRs.
- filecoin-project/lotus
- go-libp2p-kad-dht
- go-libp2p-pubsub (In case of breaking changes.)
- ipfs/kubo
- Add new release to interop tester in test-plans
- Make required changes to the release process.
M1chlCZ
Metadata
Metadata
Assignees
Labels
No labels