libp2p / libp2p/go-libp2p

v0.39

Open
#3,082 0 comments 0 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

🔦 Highlights

This is a small release. The main thing is updating quic-go to v0.49.0 and enabling specific environments with the new CustomTCPDialer option.

Changelog

  • Update quic-go to v0.49.0
  • Support application provided quic.Transports
  • Support SOCKS proxy with ws(s)
  • Support CustomTCPDialer for running TCP over arbitrary user-defined proxies.

✅ 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. deferring this to keep this release small
    • 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. deferring this to keep this release small
  • 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
  • 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 unchecked items in the release checklist, especially publishing through the GitHub UI, announcing on discuss.libp2p.io, updating upstream dependencies, and adding the release to test-plans. Review the completed checklist entries and release notes to understand the expected process. Done means the release is published, announced, propagated to the listed upstream projects, and recorded in the interop tester.

Written by the indexing model from the issue text.

Assessment

Tech stack
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.