Release 0.20

[guseggert]

Meta

• Release owner: ???
• Release engineer: @hacdias
• Release reviewer: @galargh
• Expected RC1 date: 2023-04-06
• Expected RC2 date: 2023-04-25
• 🚢 Expected final release date: 2023-04-13 2023-04-27
• Accompanying PR for improving the release process: (example: docs: release process updates from v0.17.0 #9391)
• Accompanying Issue for updating the infra: (example: https://github.com/protocol/bifrost-infra/issues/2221)

See 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

• Release v0.8.0 boxo#250
  • fix from fix(gateway): panic on path without enough components boxo#272 was not present in boxo 0.8.0, we may need a patch release with it
  • similar, traceparent header support on gateway from feat: boxo tracing and traceparent support #9811
• Allow injecting custom path resolvers. #9750
• @guseggert new kad-dht with Optimistic Provide libp2p/go-libp2p-kad-dht#783 and feat: add experimental optimistic provide #9753

🔦 Highlights

< top highlights for this release notes. For ANY version (final or RCs) >

• Release v0.8.0 boxo#250 - boxo 0.8 with repo consolidation and major gateway refactor
• COE action items from DHT events, especially around accelerated DHT client like Move AcceleratedDHTClient from being experimental #9703
• https://github.com/libp2p/go-libp2p/releases/tag/v0.27.0 - libp2p v0.27.0

✅ Release Checklist

Labels

If an item should be executed for a specific release type, it should be labeled with one of the following labels:

• execute ONLY when releasing a Release Candidate
• execute ONLY when releasing a Final Release

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:

• do NOT execute when releasing a Patch Release

Before the release

This section covers tasks to be done ahead of the release.

• Verify you have access to all the services and tools required for the release
  • GPG signature configured in local git and in GitHub
  • admin access to IPFS Discourse
    • ask the previous release owner (or @2color) for an invite
  • access to #shared-pl-marketing-requests channel in FIL Slack
    • ask the previous release owner for an invite
  • access to IPFS network metrics dashboards in Grafana
    • open an access request in the pldw
    • example
  • kuboreleaser checked out on your system (only if you're using kuboreleaser)
  • docker installed on your system (only if you're using kuboreleaser)
  • npm installed on your system (only if you're NOT using kuboreleaser)
  • zsh installed on your system
  • kubo checked out under $(go env GOPATH)/src/github.com/ipfs/kubo
    • you can also symlink your clone to the expected location by running mkdir -p $(go env GOPATH)/src/github.com/ipfs && ln -s $(pwd) $(go env GOPATH)/src/github.com/ipfs/kubo
  • Reddit account
• Upgrade Go used in CI to the latest patch release available in CircleCI in:
  • ipfs/distributions
    • example
  • ipfs/ipfs-docs
    • example
• Verify there is nothing left for release
• Create a release process improvement PR
  • update the release issue template as you go
  • link it in the Meta section

The release

This section covers tasks to be done during each release.

• Prepare the release branch and update version numbers accordingly
  using kuboreleaser release --version v0.20.0(-rcN) prepare-branch or ...

  • create a new branch release-v0.20.0
    • use master as base if Z == 0
    • use release as base if Z > 0
  • update the CurrentVersionNumber in version.go in the master branch to v0.21.0-dev
    • example
  • update the CurrentVersionNumber in version.go in the release-v0.20 branch to v0.20.0(-RCN)
    • example
  • create a draft PR from release-v0.20 to release
    • example
  • Cherry-pick commits from master to the release-v0.20.0 using git cherry-pick -x <commit>
  • Add full changelog and contributors to the changelog
    • Replace the Changelog and Contributors sections of the changelog with the stdout of ./bin/mkreleaselog
      • do NOT copy the stderr
  • verify all CI checks on the PR from release-v0.20 to release are passing
  • Merge the PR from release-v0.20 to release using the Create a merge commit
    • do NOT use Squash and merge nor Rebase and merge because we need to be able to sign the merge commit
    • do NOT delete the release-v0.20 branch
• Create the release tag
  using kuboreleaser release --version v0.20.0(-rcN) tag or ...

  • This is a dangerous operation! Go and Docker publishing are difficult to reverse! Have the release reviewer verify all the commands marked with ⚠️!
  • ⚠️ tag the HEAD commit using git tag -s v0.20.0(-RCN) -m 'Prerelease 0.20.0(-RCN)'
  • ⚠️ tag the HEAD commit of the release branch using git tag -s v0.20.0(-RCN) -m 'Release 0.20.0(-RCN)'
  • ⚠️ verify the tag is signed and tied to the correct commit using git show v0.20.0(-RCN)
  • ⚠️ push the tag to GitHub using git push origin v0.20.0(-RCN)
    • do NOT use git push --tags because it pushes all your local tags
• Publish the release to DockerHub
  using kuboreleaser --skip-check-before --skip-run release --version v0.20.0(-rcN) publish-to-dockerhub or ...

  • Wait for Publish docker image workflow run initiated by the tag push to finish
  • verify the image is available on Docker Hub
• Publish the release to ipfs.tech
  using kuboreleaser release --version v0.20.0(-rcN) publish-to-distributions or ...

  • check out ipfs/distributions
  • run ./dist.sh add-version kubo v0.20.0(-RCN) to add the new version to the versions file
    • usage
  • create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current_version and dists/go-ipfs/current_version)
    • example
  • wait for the CI workflow run initiated by the merge to master to finish
  • verify the release is available on dist.ipfs.io
• Publish the release to NPM
  using kuboreleaser release --version v0.20.0(-rcN) publish-to-npm or ...

  • run the Release to npm workflow
  • check Release to npm workflow run logs to verify it discovered the new release
  • verify the release is available on NPM
• Publish the release to GitHub
  using kuboreleaser release --version v0.20.0(-rcN) publish-to-github or ...

  • create a new release on GitHub
    • RC example
    • FINAL example
    • use the v0.20.0(-RCN) tag
    • link to the release issue
    • link to the changelog in the description
    • check the This is a pre-release checkbox
    • copy the changelog (without the header) in the description
    • do NOT check the This is a pre-release checkbox
  • run the sync-release-assets workflow
  • wait for the sync-release-assets workflow run to finish
  • verify the release assets are present in the GitHub release
• Promote the release
  using kuboreleaser release --version v0.20.0(-rcN) promote or ...

  • create an IPFS Discourse topic
    • prerelease example
    • release example
    • use Kubo v0.20.0(-RCN) is out! as the title
    • use kubo and go-ipfs as topics
    • repeat the title as a heading (##) in the description
    • link to the GitHub Release, binaries on IPNS, docker pull command and release notes in the description
  • pin the IPFS Discourse topic globally
    • you can make the topic a banner if there is no banner already
  • verify the IPFS Discourse topic was copied to:
    • #ipfs-chatter in IPFS Discord
    • #ipfs-chatter in FIL Slack
    • #ipfs-chatter:ipfs.io in Matrix
  • Add the link to the IPFS Discourse topic to the GitHub Release description
    • example
  • create an issue comment mentioning early testers on the release issue
    • example
  • create an issue comment linking to the release on the release issue
    • example
  • ask the marketing team to tweet about the release in #shared-pl-marketing-requests in FIL Slack
    • example
  • post the link to the GitHub Release to Reddit
    • example
• Test the new version with ipfs-companion
  using kuboreleaser release --version v0.20.0(-rcN) test-ipfs-companion or ...

  • run the e2e
    • use v0.20.0(-RCN) as the Kubo image version
  • wait for the e2e workflow run to finish
• Update Kubo in interop
  using kuboreleaser release --version v0.20.0(-rcN) update-interop or ...

  • check out ipfs/interop
  • run npm install
  • create a PR which updates package.json and package-lock.json
  • merge the PR
• Update Kubo in ipfs-desktop
  using kuboreleaser release --version v0.20.0(-rcN) update-ipfs-desktop or ...

  • check out ipfs/ipfs-desktop
  • run npm install
  • create a PR which updates package.json and package-lock.json
  • add @SgtPooki and @whizzzkid as reviewers
• Update Kubo docs
  using kuboreleaser release --version v0.20.0(-rcN) update-ipfs-docs or ...

  • run the update-on-new-ipfs-tag.yml workflow
  • merge the PR created by the update-on-new-ipfs-tag.yml workflow run
• Create a blog entry on ipfs.tech
  using kuboreleaser release --version v0.20.0(-rcN) update-ipfs-blog --date YYYY-MM-DD or ...

  • create a PR which adds a release note for the new Kubo version
    • example
  • merge the PR
  • verify the blog entry was published
• Merge the release branch back into master, ignoring the changes to version.go (keep the -dev) version,
  using kuboreleaser release --version v0.20.0(-rcN) merge-branch or ...

  • create a new branch merge-release-v0.20.0 from release
  • create and merge a PR from merge-release-v0.20.0 to master
• Prepare for the next release
  using kuboreleaser release --version v0.20.0(-rcN) prepare-next or ...

  • Create the next changelog
  • Link to the new changelog in the CHANGELOG.md file
  • Create the next release issue
• Create a dependency update PR
  • check out ipfs/kubo
  • run go get -u in root directory
  • run go mod tidy in root directory
  • run go mod tidy in docs/examples/kubo-as-a-library directory
  • create a PR which updates go.mod and go.sum
  • add the PR to the next release milestone
• Close the release issue

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:

• Check the issues with the help wanted label in the ipfs/kubo repo
• Join the discussion at discuss.ipfs.tech and help users finding their answers.
• See other options at https://docs.ipfs.tech/community/

[guseggert]

placeholder

[galargh]

Dependency upgrade PR: #9744

[BigLep]

I set the expected release date in the issue description.

[guseggert]

Self reminder: add notes in changelog about ipfs/boxo#202 (comment)

[BigLep]

2023-04-04 maintainer conversation:

We're still planning to do the RC on 2023-04-05

Blocking:

@guseggert

• Release v0.8.0 boxo#250
• Allow injecting custom path resolvers. #9750

@Jorropo

• Move AcceleratedDHTClient from being experimental #9703
• Provide easy/clear notification/error if falling behind reproviding #9702
• Guide users who are doing "a lot" of provides into the AcceleratedDHTClient #9704

Stretch (not blocking)

• @guseggert new kad-dht with Optimistic Provide libp2p/go-libp2p-kad-dht#783 and feat: add experimental optimistic provide #9753
• @Jorropo Pinner changes and if can't make it in give a statement to the contributor pin: follow async pinner changes, use directly CoreApi.Pin.Verify #9692

[marten-seemann]

Would be great if #9796 could be included.

[galargh]

Early testers ping for v0.20.0-rc1 testing 😄.

• Charity Engine (@Rytiss, @tristanolive)
• Fission (@bmann)
• Infura (@MichaelMure)
• OrbitDB (@aphelionz)
• pacman.store (@RubenKelevra)
• Pinata (@obo20)
• PL EngRes bifrost (@gmasgras)
• RTrade (@postables)
• Siderus (@koalalorenzo)
• Textile (@sanderpick)

You're getting this message because you're listed here. Please update this list if you no longer want to be included.

[BigLep]

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:

1. It hits the gateway codepaths which we know needs some additional updates from RC2
2. Save maintainer time for more IPFS Thing prep

We do still need to land the 0.20 changelog: #9799

Dates in the issue description have been updated.

[BigLep]

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

[BigLep]

2023-04-19 conversation of remaining steps to close out the relse

• @hacdias Tag Boxo release: chore: version 0.8.1 boxo#284
• @hacdias Upgrade Kubo to use it chore: bump to boxo 0.8.1 #9836
• @hacdias / @galargh Get the latest go-libp2p release that is in master
• @Jorropo to check on "no-fetch" gateway functionality still working and potentially create missing test.
  • "I checked it works and we have a test, I have no idea why my server is broken there but it's not that. It's good for release."
• @hacdias Changelog reminder for "https://github.com/ipfs/kubo/releases#deprecation-of-the-ipfs-pubsub-commands-and-matching-http-endpoints" that it will be removed in the next one: docs: add ipfs pubsub deprecation reminder to changelog #9827
• @hacdias / @galargh Cut RC2
• @guseggert Thunderdome test of RC2

[hacdias]

Early testers ping for v0.20.0-rc2 testing 😄.

• Charity Engine (@Rytiss, @tristanolive)
• Fission (@bmann)
• Infura (@MichaelMure)
• OrbitDB (@aphelionz)
• pacman.store (@RubenKelevra)
• Pinata (@obo20)
• PL EngRes bifrost (@gmasgras)
• RTrade (@postables)
• Siderus (@koalalorenzo)
• Textile (@sanderpick)

You're getting this message because you're listed here. Please update this list if you no longer want to be included.

[BigLep]

2023-05-04 status update before we release:

1. Review Thunderdome results
2. Get 0.20.0-rc2: rc1 & rc2 fail to boot up with WebTransport in Addresses.Announce  #9838 addressed
3. Address v0.20.0-rc2: cannot build plugins #9839

Expected release date from what I can see is 2023-05-08.

[BigLep]

Thunderdome run info https://filecoinproject.slack.com/archives/C04M8232QRW/p1683224362858909 and https://protocollabs.grafana.net/d/GE2JD7ZVz/experiment-timeline?orgId=1&from=1683205486396&to=1683224204494

[BigLep]

We are all clear for the release. It will happen 2023-05-09.

[marten-seemann]

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.

[BigLep]

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:

1. We're already behind schedule on the release. It's been a team goal not to stick to the schedule as much as possible and not get stalled by waiting to fit more in.
2. This isn't a 0.20 (or even 0.19) regression.

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).

[marten-seemann]

Here it is: #9862

[hacdias]

🎉 Kubo v0.20.0 is out!

[BigLep]

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

Repository	Title	Status	Theme
protocol/ipfs-vulnerabilities	Exploitable Memory Leak in the go-bitswap server allows an attacker to OOM any lotus or kubo node with public libp2p swarm ports	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	Daemon ignores filters and trigger NetScan abuse	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	DHT announcements are not happening when using a large blockstore	🎉 Done	⚠️ Critical fix or improvement
libp2p/go-libp2p-routing-helpers	feat: zero timeout on composed routers should disable timeout	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	0.16.0-rc1: AcceleratedDHTClient possible issue?	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	chore: deprecate remaining dht query command	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	Unable to initialize libp2p due to conflicting limit configuration	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	chore: deprecate the pubsub api	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	fix: deadlock while racing ipfs dag import and ipfs repo gc	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	0.20.0-rc2: rc1 & rc2 fail to boot up with WebTransport in Addresses.Announce	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	v0.20.0-rc2: cannot build plugins	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	fix: use default HTTP routers when FullRT DHT client is used	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	fix: deadlock on retrieving WebTransport addresses	🎉 Done	⚠️ Critical fix or improvement
ipfs/kubo	ipfs : panic: expected chan in accept muxer	🎉 Done	⚠️ Critical fix or improvement
	⬇️⬇️⬇️ Security/Operational Incidents ⬇️⬇️⬇️		⚠️ Critical fix or improvement
	⬇️⬇️⬇️ Other Items ⬇️⬇️⬇️		⚠️ Critical fix or improvement
	⬇️⬇️⬇️ Needs Triage ⬇️⬇️⬇️		⚠️ Critical fix or improvement
ipfs/specs	Publish specifications to specs.ipfs.tech	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/boxo	fix: ensure (dag)-cbor/json codecs are registered	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/specs	Publish IPIPs to specs.ipfs.tech	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/specs	Define the loose/minimal IPFS definition	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/spec-generator	Further Improvements	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/spec-generator	feat: support for relatedIssues frontmatter field	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/ipfs-blog	Blog post on implementations and principles	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/specs	IPFS Principles	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/specs	Improvements to the specifications website	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/specs	Put architecture/meta up top	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/spec-generator	Specs should link back to GitHub	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/spec-generator	feat: add history and feedback links	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/specs	feat: add links to history and repository	🎉 Done	🧑🏻‍⚖️ Governance/Specs
ipfs/specs	IPIP-351: IPNS Signed Records Response Format on HTTP Gateways	🎉 Done	🌉 Gateways and Clients
ipfs/bifrost-gateway	refactor: more informative error on /api/v0/dht/get failure	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	gateway: migrate sharness tests from Kubo	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	Refactor Gateway API so can extract out the request layer	🎉 Done	🌉 Gateways and Clients
ipfs/specs	docs: return 400 Bad Request on Invalid CIDs	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	feat: remove writable gateway	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	feat: refactor gateway api to operate on higher level semantics	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	gateway: return 400 on /ipfs/invalid-cid	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	feat: return 400 on /ipfs/invalid-cid	🎉 Done	🌉 Gateways and Clients
ipfs/go-cid	feat: wrap parsing errors into ErrInvalidCid	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	feat(gateway): invalid CID returns 400 Bad Request	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	fix(gateway): 500 on panic, recover on WithHostname	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	Missing Access-Control-Allow-Origin Headers on Redirects	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	fix: apply API.HTTPHeaders to /webui redirect	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	Remove Writable Gateway	🎉 Done	🌉 Gateways and Clients
ipfs/bifrost-gateway	fix: ensure (dag)-cbor/json codecs are registered	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	refactor(gateway): consistent tracing names	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	feat(gateway): trace context header support	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	feat: set default OTel propagator	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	refactor(examples): proxy gateway to use exchange	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	ci(gateway): enable subdomain conformance	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	refactor(gateway): use a single path struct internally	🎉 Done	🌉 Gateways and Clients
ipfs/ipfs-docs	Update gateways info	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	ci: gateway sharness points to Kubo master	🎉 Done	🌉 Gateways and Clients
ipfs/bifrost-gateway	panic on staging: runtime error: slice bounds out of range [:-1]	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	feat: support OTel tracing in gateway with correct propagators	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	feat(tracing): use OTEL_PROPAGATORS as per OTel spec	🎉 Done	🌉 Gateways and Clients
ipfs/boxo	feat(routing): allow-offline with routing put	🎉 Done	🌉 Gateways and Clients
ipfs/kubo	test: deterministic ipns fixtures during sharness gateway tests	🎉 Done	🌉 Gateways and Clients
ipfs/specs	IPIP-402: Partial CAR Support on Trustless Gateways	🔎 In Review	🌉 Gateways and Clients
ipfs/boxo	feat(gateway): redirect ipns b58mh to cid	🔎 In Review	🌉 Gateways and Clients
ipfs/kubo	fix: do not use b58mh peer id for ipns test	🔎 In Review	🌉 Gateways and Clients
ipfs/kubo	Gateway support for signed IPNS records doesn't work with raw base58 PeerIDs	🔎 In Review	🌉 Gateways and Clients
ipfs/boxo	feat(gateway)!: new trustless mode, and by default	🔎 In Review	🌉 Gateways and Clients
ipfs/kubo	feat(gw): configurable trusted mode	🔎 In Review	🌉 Gateways and Clients
ipfs/specs	Create IPIP with Gateway spec for partial CAR exports	🏃‍♀️ In Progress	🌉 Gateways and Clients
ipfs/bifrost-gateway	Support Trace Context HTTP headers	🏃‍♀️ In Progress	🌉 Gateways and Clients
	👀 bifrost-gateway Project Board		🌉 Gateways and Clients
ipfs/kubo	[Tracking issue] http delegated routing used in production	🎉 Done	🔀 Content Routing/Providing
ipfs/specs	feat: rename Delegated Routing HTTP API to Routing v1 HTTP API	🎉 Done	🔀 Content Routing/Providing
ipfs/kubo	feat: add experimental optimistic provide	🎉 Done	🔀 Content Routing/Providing
libp2p/go-libp2p-kad-dht	Optimistic Provide	🎉 Done	🔀 Content Routing/Providing
ipfs/kubo	feat: add client-side metrics for routing-v1 client	🎉 Done	🔀 Content Routing/Providing
ipfs/kubo	fix: remove timeout on default DHT operations	🎉 Done	🔀 Content Routing/Providing
ipfs/kubo	feat: add changelog entry for router timeouts for v0.19.1	🎉 Done	🔀 Content Routing/Providing
ipfs/specs	Routing v1: Add support for multiple routers	🔎 In Review	🔀 Content Routing/Providing
libp2p/go-libp2p-kad-dht	Don't add unresponsive DHT servers to the RT	🏃‍♀️ In Progress	🔀 Content Routing/Providing
	⬇️⬇️⬇️ Closeout from Reframe → HTTP Delegated Routing ⬇️⬇️⬇️		🔀 Content Routing/Providing
	⬇️⬇️⬇️ Other ⬇️⬇️⬇️		🔀 Content Routing/Providing
ipfs/kubo	cannot reserve inbound connection: resource limit exceeded	🎉 Done	♿️ Other Initiative
ipfs/boxo	Document the planned import scope and order of ipfs repos	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Rename go-libipfs to boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/go-merkledag	Update README.md and added CODEOWNERS	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Release v0.8.0	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	feat: mega migration	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	[Design/discussion/decision] Whether to migrate" or "copy" repos into go-libipfs"	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	feat: Über Migration (and Boxo rename)	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/go-ipfs-cmds	chore: change go-libipfs to boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	chore: migrate go-libipfs to boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Document how existing migrated repo consumers update to go-libipfs	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Document the release process	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	Consolidate IPFS Repositories	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Tooling to minimize impact on those updating to boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Added FAQ and README updates	🎉 Done	👷🏾 Maintainer/Contributor Experience
filecoin-project/lotus	chore: boxo: migrate from go-libipfs to boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Migrate go-namesys	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: port peering test from sharness to Go	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/go-datastore	CI is red	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	feat: bump bitswap message package to v1	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: port remote pinning tests to Go	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	Migrate t0139-swarm-rcmgr.sh to the new test framework	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	docs: use fx.Decorate instead of fx.Replace in examples	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: port routing DHT tests to Go	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: increase max wait time for peering assertion	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	chore: upgrade OpenTelemetry dependencies	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: fix Docker tests in GH Actions	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	feat: add heap allocs to 'ipfs diag profile'	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	docs: add note in README that go-libipfs is not comprehensive	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/go-ipfs-http-client	chore: migrate to boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Add coverage note to README	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: skip flaky pubsub test	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: cancel workflows on same branch when new commit is added	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: fix flaky content routing over HTTP test	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Rename migration tool to boxo-migrate, tidy up, and add docs	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	chore: remove libp2pio.car	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/go-ipfs-api	chore: upgrade to boxo	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	docs: fix jaeger command	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: port multinode test to Go	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	chore: set kubo-maintainers as default code owners	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	test: port twonode test to Go, remove multinode test	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	refactor: remove badger, leveldb dependencies	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/kubo	docs: add Customizing Kubo" doc"	🎉 Done	👷🏾 Maintainer/Contributor Experience
ipfs/go-ipfs-cmds	chore: upgrade to boxo v0.8.0	🔎 In Review	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	[Milestone] Getting boxo over the hump""	🏃‍♀️ In Progress	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	Handle relationship between boxo and go-car and go-merkledag	🏃‍♀️ In Progress	👷🏾 Maintainer/Contributor Experience
ipfs/boxo	[Tracking issue] Release for the over the hump" copy repo consolidation"	🏃‍♀️ In Progress	👷🏾 Maintainer/Contributor Experience
	⬇️⬇️⬇️ go-libipfs: getting over the hump / 🦆 🦆 🦆 ⬇️⬇️⬇️		👷🏾 Maintainer/Contributor Experience
	Ensure others have access to https://github.com/hsanjuan/ipfs-lite		👷🏾 Maintainer/Contributor Experience
	⬇️⬇️⬇️ Other⬇️⬇️⬇️		👷🏾 Maintainer/Contributor Experience
ipfs/kubo	ipfs swarm peers --enc=json --identify	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	Remove the alpha software warning in assets/init-doc/readme	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	feat!: make --empty-repo default	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	Make ipfs init --empty-repo=true the default	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	test: fix autoclient flakiness	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	Allow injecting custom path resolvers.	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	feat: boxo tracing and traceparent support	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	deps: bump go-libp2p to v0.27.1	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	feat: webui@3.0.0	🎉 Done	🤞 Best Effort Improvement
ipfs/kubo	Feat/add deduplication ratio stat	🔎 In Review	🤞 Best Effort Improvement
ipfs/kubo	Release 0.19	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	docs: 0.19 changelog	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Release 0.19.1	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Release 0.20	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	docs: preparing 0.20 changelog for release	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/boxo	docs: add RELEASE.md	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Process Improvement: v0.18.0	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Move off CircleCI to GitHub Actions	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Fix release template issues/gaps (v0.11 edition)	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	chore: update deps after v0.19.0 release	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/boxo	chore: release v0.8.0-rc1	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/boxo	chore: bump to 0.8.0-rc4	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/boxo	Release v0.8.0	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/go-ipfs-api	chore: release v0.6.0	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	fix(ci): speed up docker build	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	docs: add ipfs pubsub deprecation reminder to changelog	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Release 0.19.2	🎉 Done	🚅 Release Process, Artifacts, CI/CD
ipfs/go-ipfs-priv	ci: enable access to any private gh repo	🔎 In Review	🚅 Release Process, Artifacts, CI/CD
ipfs/distributions	fix: unify build matrix for amd64-v2 and v3	🔎 In Review	🚅 Release Process, Artifacts, CI/CD
ipfs/distributions	perf: remove amd64 microarchitecture levels from the template	🔎 In Review	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Automate Kubo release process	🏃‍♀️ In Progress	🚅 Release Process, Artifacts, CI/CD
ipfs/boxo	Enforce changelog updates in CI	🛑 Blocked	🚅 Release Process, Artifacts, CI/CD
ipfs/boxo	Use CHANGELOG.md to drive releases	🥞 Todo	🚅 Release Process, Artifacts, CI/CD
ipfs/boxo	Tag releases with CHANGELOG.md	🥞 Todo	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	Windows arm64 native support	🥞 Todo	🚅 Release Process, Artifacts, CI/CD
ipfs/distributions	Add Universal Mac OS build	🥞 Todo	🚅 Release Process, Artifacts, CI/CD
ipfs/kubo	chore: upgrade to go-libp2p-kad-dht@v0.23.0	🎉 Done	❓ Unsure