libp2p / libp2p/go-libp2p

v0.45

Open
#3,408 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
6.9k
Forks
1.3k
Avg merge
13d 21h
Merged PRs (30d)
1

Description

## 🗺 What's left for release

- [ ] #3384
- [ ] #3386
- [ ] #3407

## 🔦 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's `go.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](https://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](https://github.com/filecoin-project/lotus)
- [ ] [go-libp2p-kad-dht](https://github.com/libp2p/go-libp2p-kad-dht/)
- [ ] [go-libp2p-pubsub](https://github.com/libp2p/go-libp2p-pubsub) (In case of breaking changes.)
- [ ] [ipfs/kubo](https://github.com/ipfs/kubo)
- [ ] Add new release to interop tester in [test-plans](https://github.com/libp2p/test-plans/)
- [ ] Make required changes to the release process.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the release checklist in this issue and inspect the listed changes in #3384, #3386, and #3407. Review the changelog with the provided git log command, then check dependencies and the referenced upstream repositories. Done means the release is published and announced, examples and upstream dependencies are updated, the interop tester includes it, and required release-process changes are complete.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, github, go
Domain
release
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.