Release 0.19

[guseggert]

Meta

• Release owner: @galargh
• Release reviewer: @hacdias
• Expected RC date: week of 2023-02-23 2023-03-02 2023-03-06
• 🚢 Expected final release date: 2023-02-30 2023-03-09 2023-03-13
• Accompanying PR for improving the release process: Process Improvement: v0.18.0 #9484
• Accompanying Issue for updating the infra: https://github.com/protocol/bifrost-infra/issues/2399

See 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

• Do we need to make any changes to the infrastructure configuration?
• feat(gateway): IPNS record response format (IPIP-351) #9399
• fix: honour --ttl flag in 'ipfs name publish' #9471
• feat: ipfs-webui 2.22.0 #9597
• chore: update dependencies ahead of the v0.19 release #9619
• routing get|put: restore old JSON wire format #9638
• switch delegated HTTP routing to streaming JSON responses
• switch to go-libp2p v0.26 (once released on Thu: go-libp2p v0.26 libp2p/go-libp2p#2062)

Nice to have

• Make accelerated DHT client non-experimental (incl. config migration)

🔦 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:

• 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 #bifrost channel in FIL Slack
    • ask the previous release owner 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
• Notify the bifrost team about the upcoming release (only if it is not the day of the release yet)
  using kuboreleaser release --version v0.19.0(-RCN) notify-bifrost --date YYYY-MM-DD or ...

  • open an issue against bifrost-infra
    • example
• Link the bifrost-infra issue in the Meta section
• 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.19.0(-RCN) prepare-branch or ...

  • create a new branch release-v0.19.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.19+1.0-dev
    • example
  • update the CurrentVersionNumber in version.go in the release-v0.19 branch to v0.19.0(-RCN)
    • example
  • create a draft PR from release-v0.19 to release
    • example
  • Cherry-pick commits from master to the release-v0.19.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.19 to release are passing
  • Merge the PR from release-v0.19 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.19 branch
• Create the release tag
  using kuboreleaser release --version v0.19.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.19.0(-RCN) -m 'Prerelease 0.19.0(-RCN)'
  • ⚠️ tag the HEAD commit of the release branch using git tag -s v0.19.0(-RCN) -m 'Release 0.19.0(-RCN)'
  • ⚠️ verify the tag is signed and tied to the correct commit using git show v0.19.0(-RCN)
  • ⚠️ push the tag to GitHub using git push origin v0.19.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.19.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.19.0(-RCN) publish-to-distributions or ...

  • check out ipfs/distributions
  • run ./dist.sh add-version kubo v0.19.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.19.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.19.0(-RCN) publish-to-github or ...

  • create a new release on GitHub
    • RC example
    • FINAL example
    • use the v0.19.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
• Notify the bifrost team about the release
  using kuboreleaser release --version v0.19.0(-RCN) notify-bifrost --date YYYY-MM-DD or ...

  • create an issue comment on the issue in the bifrost-infra
• Promote the release
  using kuboreleaser release --version v0.19.0(-RCN) promote or ...

  • create an IPFS Discourse topic
    • prerelease example
    • release example
    • use Kubo v0.19.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.19.0(-RCN) test-ipfs-companion or ...

  • run the e2e
    • use v0.19.0(-RCN) as the Kubo image version
  • wait for the e2e workflow run to finish
• Update Kubo in interop
  using kuboreleaser release --version v0.19.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.19.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
  • merge the PR
• Update Kubo docs
  using kuboreleaser release --version v0.19.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.19.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
• Keep checking the metrics until the release issue is closed
  • release notes
  • post in the #bifrost channel in FIL Slack if there is a problem
• Merge the release branch back into master, ignoring the changes to version.go (keep the -dev) version,
  using kuboreleaser release --version v0.19.0(-RCN) merge-branch or ...

  • create a new branch merge-release-v0.19.0 from release
  • create and merge a PR from merge-release-v0.19.0 to master
• Prepare for the next release
  using kuboreleaser release --version v0.19.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

[BigLep]

2023-02-21 maintainer conversation:

Things for the RC

• Resource manager items for Kubo 0.19 (the last charge) #9650
• feat!: add and connect missing context, remove RemovePinWithMode go-ipfs-pinner#23
• feat(pinning): connect some missing go context #9557
• chore: bump go-unixfs to v0.4.3 #9643
• routing/http: feat: add streaming support boxo#18
• chore: bump go-libp2p-kad-dht to v0.21.1 #9663
• chore: update go-libp2p to v0.26 #9656
• Develop a plan for how maintainers can own their release schedule (e.g., not depend on other teams' deployments) #9574
• chore: update dependencies ahead of the v0.19 release #9619

[galargh]

Since there are still outstanding items to be completed ahead of the RC, I updated the release schedule.

[BigLep]

2023-02-28 conversation:
ipfs/boxo#18 moves to 0.20
#9619 will get covered during release

[BigLep]

I'll update this specific list later today, but #9684 should be included in the 0.19 train.

[p-shahi]

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

[MichaelMure]

Can we include ipfs/go-ipfs-pinner#24 ?

[BigLep]

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:

• Resource manager items for Kubo 0.19 (the last charge) #9650
• go-libp2p 0.26.2 update (needed for the above)

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

• Pubsub flood due to same message propagated multiple times #9665 (if this doesn't make 0.19-RC it'll be included in the final release or patch release)
• v0.18.1 panics on startup with certain routing config #9682 (will confirm 2023-03-02 that this isn't needed for the RC and can just land for the final release)
• change the Pinner interface to have async pin listing go-ipfs-pinner#24

#9619 will get handled as part of the release itself.

[Jorropo]

#9688 (a few important dependencies bumps) is needed too.

[BigLep]

Great progress was made on #9650 today. The PR #9680 needs to get merged before we can do RC though. It's not certain to me yet whether that will happen early enough tomorrow (2023-03-03) for @galargh to do the release. If we don't do the RC Friday it will happen Monday.

[galargh]

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

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

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

[BigLep]

@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:

1. Early testers should have QRI removed
2. Early testers should have PL EngRes bifrost added
3. Changelog link from https://github.com/ipfs/kubo/releases/tag/v0.19.0-rc1 doesn't resolve

[galargh]

@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:

1. Early testers should have QRI removed
2. Early testers should have PL EngRes bifrost added
3. Changelog link from https://github.com/ipfs/kubo/releases/tag/v0.19.0-rc1 doesn't resolve

Added a link to the meta section: #9484 We're reusing 0.18.

1. fceefcd <- I see you've already done it.
2. This time around we created a dedicated issue for bifrost as we used to before. I created a PR for the early testers update - docs: add bifrost to early testers #9699. I'm also going to update kuboreleaser accordingly.
3. Fixed and made the relevant change in kuboreleaser.

[BigLep]

2023-03-07 conversation:

• Bifrost has raised an issue with 0.19 (likely the same panic issue)
  • Not going to block the release, but will keep Gus focused on it: v0.18.1 panics on startup with certain routing config #9682
• Thunderdome:
  • For this release, run it
  • Tea leaf reading of the same graphs
  • ✅ Steve will ask Ian to do this: https://filecoinproject.slack.com/archives/C03FFEVK30F/p1678313046137239
• Changelog updating
  • https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.19.md
  • @Jorropo will take this: docs: 0.19 changelog #9707
• ✅ Need to tag go-libipfs and update kubo go.mod
  • @Jorropo will take this: chore: release 0.6.1 boxo#197 and chore: bump go-libipfs v0.6.1 #9701
• Gateway refactoring
  • This can land in master this week, but is not going to be included in 0.19

[BigLep]

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

Repository	Title	Status	Theme	Status Date
ipfs/kubo	chore: bump go-unixfs to v0.4.3	🎉 Done	⚠️ Critical fix or improvement	Feb 23, 2023
ipfs/kubo	Use updated pubsub time cache implementation	🎉 Done	⚠️ Critical fix or improvement	Jan 27, 2023
ipfs/kubo	feat: Pubsub.SeenMessagesStrategy	🎉 Done	⚠️ Critical fix or improvement	Jan 27, 2023
ipfs/kubo	fix: Prevent Routing.Type=auto from enabling dhtserver mode if have too low of limits	🎉 Done	⚠️ Critical fix or improvement	Jan 26, 2023
ipfs/kubo	chore: update go-libp2p to v0.25.1	🎉 Done	⚠️ Critical fix or improvement	Feb 15, 2023
ipfs/kubo	fix: honour --ttl flag in 'ipfs name publish'	🎉 Done	⚠️ Critical fix or improvement	Jan 27, 2023
ipfs/go-ipfs-http-client	Not compatible with github.com/ipfs/kubo@v0.18.1	🎉 Done	⚠️ Critical fix or improvement	Feb 10, 2023
ipfs/kubo	routing get|put: restore old JSON wire format	🎉 Done	⚠️ Critical fix or improvement	Feb 10, 2023
ipfs/kubo	v0.18.1 panics on startup with certain routing config	🎉 Done	⚠️ Critical fix or improvement	Mar 2, 2023
ipfs/kubo	feat: add autoclient" routing type"	🎉 Done	⚠️ Critical fix or improvement	Mar 9, 2023
protocol/ipfs-vulnerabilities	sev4-go-unixfs-hamt-panics	🔎 In Review	⚠️ Critical fix or improvement	Jan 26, 2023
ipfs/kubo	fix(id): ascii-only identify versions	🔎 In Review	⚠️ Critical fix or improvement	Nov 7, 2022
ipfs/kubo	chore: deprecate remaining dht query command	🔎 In Review	⚠️ Critical fix or improvement	Mar 3, 2023
protocol/ipfs-vulnerabilities	ipfs-sev3-gala-non-malicious-dht-sybil	🏃‍♀️ In Progress	⚠️ Critical fix or improvement	Jan 24, 2023
	#ipfs-sev3-dht-slowness-202301	🏃‍♀️ In Progress	⚠️ Critical fix or improvement	Jan 24, 2023
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	🏃‍♀️ In Progress	⚠️ Critical fix or improvement	Feb 15, 2023
ipfs/kubo	Pubsub flood due to same message propagated multiple times	🛑 Blocked	⚠️ Critical fix or improvement	Feb 27, 2023
	⬇️⬇️⬇️ Security/Operational Incidents ⬇️⬇️⬇️		⚠️ Critical fix or improvement
	⬇️⬇️⬇️ Other Items ⬇️⬇️⬇️		⚠️ Critical fix or improvement
ipfs/specs	IPIP-328: JSON and CBOR Response Formats on HTTP Gateways	🎉 Done	🌉 Gateways and Clients	Feb 14, 2023
ipfs/kubo	gateway: IPNS key resolution timeout should return HTTP 5xx	🎉 Done	🌉 Gateways and Clients	Feb 22, 2023
ipfs/kubo	Gateway Extraction to go-libipfs/gateway	🎉 Done	🌉 Gateways and Clients	Feb 14, 2023
ipfs/go-libipfs	gateway: post-extraction GO API cleanup	🎉 Done	🌉 Gateways and Clients	Feb 2, 2023
ipfs/kubo	refactor: use gateway from go-libipfs	🎉 Done	🌉 Gateways and Clients	Jan 31, 2023
ipfs/go-libipfs	feat(gateway): improve GO API interface, remove Writable API	🎉 Done	🌉 Gateways and Clients	Feb 2, 2023
ipfs/kubo	refactor: new go-libipfs/gateway API, deprecate Gateway.Writable	🎉 Done	🌉 Gateways and Clients	Feb 2, 2023
	Gateway binary for bifrost that asks an external client (Saturn) for immutable data and processes returned CAR files	🎉 Done	🌉 Gateways and Clients	Feb 16, 2023
ipfs/go-libipfs	fix(gateway): return HTTP 500 on namesys.ErrResolveFailed	🎉 Done	🌉 Gateways and Clients	Feb 22, 2023
ipfs/go-libipfs	gateway: create example that hosts a CAR file	🎉 Done	🌉 Gateways and Clients	Feb 2, 2023
ipfs/go-libipfs	gateway: create example that proxies to requests to ?format=raw	🎉 Done	🌉 Gateways and Clients	Feb 6, 2023
ipfs/kubo	fix(gateway): return HTTP 500 on namesys.ErrResolveFailed	🎉 Done	🌉 Gateways and Clients	Feb 22, 2023
ipfs/go-libipfs	test(gateway): migrate Go tests from Kubo	🎉 Done	🌉 Gateways and Clients	Feb 15, 2023
ipfs/go-libipfs	fix(gateway): ensure ipfs_http_gw_get_duration_seconds gets updated	🎉 Done	🌉 Gateways and Clients	Feb 15, 2023
ipfs/go-libipfs	feat(gateway): metric for implicit index.html in dirs	🎉 Done	🌉 Gateways and Clients	Feb 15, 2023
ipfs/kubo	test: remove gateway tests migrated to go-libipfs	🎉 Done	🌉 Gateways and Clients	Feb 15, 2023
ipfs/go-libipfs	gateway: run kubo's cli/go tests next to sharness	🎉 Done	🌉 Gateways and Clients	Jan 31, 2023
ipfs/go-libipfs	chore: run kubo cli gateway tests	🎉 Done	🌉 Gateways and Clients	Jan 31, 2023
ipfs/go-libipfs	gateway: migrate subdomain and dnslink code	🎉 Done	🌉 Gateways and Clients	Feb 7, 2023
ipfs/kubo	Deprecate Gateway.Writable in Kubo 0.19	🎉 Done	🌉 Gateways and Clients	Feb 2, 2023
ipfs/go-libipfs	feat: migrate subdomain and dnslink code	🎉 Done	🌉 Gateways and Clients	Feb 7, 2023
ipfs/go-libipfs	docs: add example of gateway backed by CAR file	🎉 Done	🌉 Gateways and Clients	Feb 2, 2023
ipfs/go-libipfs	docs: add example of gateway that proxies to ?format=raw	🎉 Done	🌉 Gateways and Clients	Feb 6, 2023
ipfs/bifrost-gateway	Expose the same metrics as Kubo	🎉 Done	🌉 Gateways and Clients	Feb 11, 2023
ipfs/bifrost-gateway	Set up Github permissions and CI automation	🎉 Done	🌉 Gateways and Clients	Feb 11, 2023
ipfs/bifrost-gateway	Publish Docker images	🎉 Done	🌉 Gateways and Clients	Feb 9, 2023
ipfs/go-libipfs	gateway: add missing metrics and traces	🎉 Done	🌉 Gateways and Clients	Feb 8, 2023
ipfs/go-libipfs	feat(gateway): add TAR, IPNS Record, DAG-* histograms and spans	🎉 Done	🌉 Gateways and Clients	Feb 8, 2023
ipfs/kubo	chore: update go-libipfs for more gateway metrics	🎉 Done	🌉 Gateways and Clients	Feb 8, 2023
ipfs/go-libipfs	fix: gateway car example dnslink	🎉 Done	🌉 Gateways and Clients	Feb 8, 2023
ipfs/interface-go-ipfs-core	test: basic routing interface test	🎉 Done	🌉 Gateways and Clients	Feb 9, 2023
ipfs/kubo	feat: update routing api to match core api	🎉 Done	🌉 Gateways and Clients	Feb 8, 2023
ipfs/kubo	chore: update iface with routing tests	🎉 Done	🌉 Gateways and Clients	Feb 9, 2023
ipfs/interface-go-ipfs-core	feat!: use path.Path instead of string in routing API	🎉 Done	🌉 Gateways and Clients	Feb 8, 2023
ipfs/go-libipfs	fix: GetIPNSRecord example gateway implementation	🎉 Done	🌉 Gateways and Clients	Feb 11, 2023
ipfs/specs	IPIP-351: IPNS Signed Records Response Format on HTTP Gateways	🔎 In Review	🌉 Gateways and Clients	Nov 8, 2022
ipfs/go-libipfs	feat: refactor gateway api to operate on higher level semantics	🔎 In Review	🌉 Gateways and Clients	Feb 16, 2023
ipfs/specs	Gateway: response type for fetching signed IPNS records	🏃‍♀️ In Progress	🌉 Gateways and Clients	Oct 10, 2022
ipfs/specs	Create IPIP with Gateway spec for partial CAR exports	🏃‍♀️ In Progress	🌉 Gateways and Clients	Feb 15, 2023
ipfs/go-libipfs	Refactor Gateway API so can extract out the request layer	🏃‍♀️ In Progress	🌉 Gateways and Clients	Feb 16, 2023
ipfs/go-libipfs	gateway: migrate sharness tests from Kubo	🥞 Todo	🌉 Gateways and Clients	Feb 28, 2023
	👀 biforst-gateway Project Board		🌉 Gateways and Clients
ipfs/kubo	sharness - t0118 is broken - response for application/vnd.ipld.car SHOULD NOT include Content-Length		🌉 Gateways and Clients
ipfs/specs	IPIP-337: Delegated Content Routing HTTP API	🎉 Done	🔀 Content Routing/Providing	Feb 11, 2023
ipfs/go-delegated-routing	Updated/new HTTP API Migration	🎉 Done	🔀 Content Routing/Providing	Feb 16, 2023
ipfs/specs	feat: remove reframe	🎉 Done	🔀 Content Routing/Providing	Jan 31, 2023
ipfs/kubo	feat: set Bitswap.ProviderSearchDelay to 0s	🎉 Done	🔀 Content Routing/Providing	Feb 8, 2023
ipfs/go-libipfs	Extract Gateway Code From Kubo	🎉 Done	🔀 Content Routing/Providing	Jan 31, 2023
ipfs/kubo	[Tracking issue] http delegated routing used in production	🏃‍♀️ In Progress	🔀 Content Routing/Providing	Sep 22, 2022
ipfs/go-libipfs	routing/http: feat: add streaming support	🏃‍♀️ In Progress	🔀 Content Routing/Providing	Jan 4, 2023
ipfs/kubo	Cleanup from the move from Reframe" to "HTTP Delegated Routing""	🥞 Todo	🔀 Content Routing/Providing	Nov 8, 2022
ipfs/specs	IPIP: Streaming Delegated Content Routing	🥞 Todo	🔀 Content Routing/Providing	Oct 16, 2022
	⬇️⬇️⬇️ Closeout from Reframe → HTTP Delegated Routing ⬇️⬇️⬇️		🔀 Content Routing/Providing
	⬇️⬇️⬇️ Efforts for Decentralized Gateway ⬇️⬇️⬇️		🔀 Content Routing/Providing
	⬇️⬇️⬇️ Other ⬇️⬇️⬇️		🔀 Content Routing/Providing
	Incrementally verified CAR file imports		🚇 Data Transfer
	Build minimal data retriever leveraging go-bitswap for use in Saturn		🚇 Data Transfer
	Prototype multiprotocol multipeer sessions to that can stand in for go-bitswap (needs breaking up into more issues)		🚇 Data Transfer
ipfs/go-libipfs	Document the release process	🥞 Todo	👷🏾 Maintainer/Contributor Experience	Feb 14, 2023
ipfs/kubo	Replace flaky test/sharness/t0172-content-routing-over-http.sh with go harness	🥞 Todo	👷🏾 Maintainer/Contributor Experience	Jan 20, 2023
ipfs/kubo	Migrate t0139-swarm-rcmgr.sh to the new test framework	🥞 Todo	👷🏾 Maintainer/Contributor Experience	Jan 21, 2023
ipfs/kubo	docs: bulk spelling edits	🎉 Done	🤞 Best Effort Improvement	Feb 21, 2023
ipfs/go-ipfs-pinner	feat!: add and connect missing context, remove RemovePinWithMode	🎉 Done	🤞 Best Effort Improvement	Feb 22, 2023
ipfs/kubo	feat(pinning): connect some missing go context	🎉 Done	🤞 Best Effort Improvement	Feb 22, 2023
ipfs/go-libipfs	feat: add a logo and some basics in the README	🎉 Done	👂 Community Engagement	Jan 26, 2023
ipfs/go-libipfs	chore: add codecov PR comment	🎉 Done	👂 Community Engagement	Jan 26, 2023
ipfs/kubo	Release 0.18	🎉 Done	🚅 Release Process, Artifacts, CI/CD	Jan 27, 2023
ipfs/kubo	Release 0.18.1	🎉 Done	🚅 Release Process, Artifacts, CI/CD	Jan 31, 2023
ipfs/go-libipfs	Add coverage to PRs	🎉 Done	🚅 Release Process, Artifacts, CI/CD	Jan 26, 2023
ipfs/kubo	feat: ipfs-webui 2.22.0	🎉 Done	🚅 Release Process, Artifacts, CI/CD	Jan 28, 2023
ipfs/kubo	Release 0.18.2	🎉 Done	🚅 Release Process, Artifacts, CI/CD	Mar 7, 2023
ipfs/kubo	Release 0.19	🔎 In Review	🚅 Release Process, Artifacts, CI/CD	Nov 14, 2022
ipfs/kubo	Process Improvement: v0.18.0	🔎 In Review	🚅 Release Process, Artifacts, CI/CD	Feb 2, 2023
ipfs/go-ipfs-priv	ci: enable access to any private gh repo	🔎 In Review	🚅 Release Process, Artifacts, CI/CD	Sep 3, 2022
ipfs/distributions	fix: unify build matrix for amd64-v2 and v3	🔎 In Review	🚅 Release Process, Artifacts, CI/CD	Nov 13, 2022
ipfs/distributions	perf: remove amd64 microarchitecture levels from the template	🔎 In Review	🚅 Release Process, Artifacts, CI/CD	Jan 24, 2023
ipfs/kubo	Develop a plan for how maintainers can own their release schedule (e.g., not depend on other teams' deployments)	🏃‍♀️ In Progress	🚅 Release Process, Artifacts, CI/CD	Jan 23, 2023
ipfs/kubo	Automate Kubo release process	🏃‍♀️ In Progress	🚅 Release Process, Artifacts, CI/CD	Nov 1, 2022
ipfs/kubo	Move off CircleCI to GitHub Actions	🏃‍♀️ In Progress	🚅 Release Process, Artifacts, CI/CD	Jan 19, 2023
ipfs/kubo	Fix release template issues/gaps (v0.11 edition)	🥞 Todo	🚅 Release Process, Artifacts, CI/CD	Mar 24, 2022
ipfs/kubo	Windows arm64 native support	🥞 Todo	🚅 Release Process, Artifacts, CI/CD	Oct 10, 2022
ipfs/distributions	Add Universal Mac OS build	🥞 Todo	🚅 Release Process, Artifacts, CI/CD	Oct 28, 2022
ipfs/kubo	Resource Manager: Default limits only limit the max memory and FDs and set everything else to unlimited.	🎉 Done		Jan 30, 2023
ipfs/kubo	refactor: migrate DNSLink and subdomain gateway code to go-libipfs	🎉 Done		Feb 7, 2023
ipfs/kubo	fix: restore wire format for /api/v0/routing/get	🎉 Done		Feb 10, 2023
ipfs/kubo	chore: bump go-libp2p-routing-helpers to v0.6.1	🎉 Done		Feb 10, 2023
ipfs/go-libipfs	chore: update go-libp2p to v0.25.1	🎉 Done		Feb 11, 2023
ipfs/kubo	chore: bump go-libipfs v0.6.0	🎉 Done		Feb 18, 2023
ipfs/go-libipfs	Move out RAPIDE experiment	🎉 Done		Feb 18, 2023
ipfs/interop	fix: remove relay v1 go tests	🎉 Done		Feb 23, 2023
ipfs/kubo	chore: bump go-libp2p-kad-dht to v0.21.1	🎉 Done		Feb 24, 2023
ipfs/go-libipfs	gateway: unify root identifier resolution errors	🎉 Done		Feb 28, 2023
ipfs/kubo	test: port rcmgr sharness tests to Go	🎉 Done		Feb 28, 2023
ipfs/go-libipfs	feat: support HTTP 429 with Retry-After	🎉 Done		Mar 6, 2023
	Fleek: monitor per-node provide limits	🏃‍♀️ In Progress		Feb 21, 2023
	Fleek: ensure Fleek reenables libp2p resource manager	🛑 Blocked		Feb 21, 2023
	Wire up libipfs routing/v1 client metrics to Kubo	🛑 Blocked		Feb 21, 2023

[BigLep]

2023-03-09 maintainer conversation

Remaining things before 0.19 final release

• Validate Bifrost unblocked: https://github.com/protocol/bifrost-infra/pull/2356
• Get the pubsub RPC commands deprecation notice in. This is tracked as a task in Deprecate then Remove /api/v0/pubsub/* RPC API and ipfs pubsub Commands #9717
• Thunderdome passes: https://www.notion.so/pl-strflt/2023-03-10-ProbeLab-SitRep-a41cbbb2ef564c1298d81061a49e7480?pvs=4#234ff4063f2b4809b3c109774f17009a

[BigLep]

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

[BigLep]

@galargh : we can do the final release on 2023-03-16 if:

1. chore: deprecate the pubsub api #9718 gets merged
2. Unable to initialize libp2p due to conflicting limit configuration #9695 is determined to be non blocking (or if it is blocking has a fix merged)
   @Jorropo is PoC for both the above.

[Jorropo]

This needs to be merged to fix #9723 #9695.
Once merge the release can be made.

[BigLep]

Maintainers will discuss shortly, but we're likely holding up the release until libp2p/go-libp2p#2188 is addressed.

[BigLep]

Status on the 0.19 release:

1. @hacdias : We're going to let fix(gateway): 500 on panic, recover on WithHostname boxo#199 get merged and bubbled up.
2. Need to understand the path forward concerning Bitswap problems over websocket transport since switch to nhooyr websocket libp2p/go-libp2p#2188
   This puts us at a release of 2023-03-20 at the earliest.

[p-shahi]

The new release is out: https://github.com/libp2p/go-libp2p/releases/tag/v0.26.3

[BigLep]

@galargh : we are good to go on doing the 0.19 release on Monday.
As part of this, please ensure that go-libp2p is updated to 0.26.3 if this hasn't been done already.
Thank you!

[BigLep]

Doh - I'm seeing the 0.19 changelog hasn't been merged: #9707

So two open things:

1. Update go-libp2p to 0.26.3: https://github.com/ipfs/kubo/blob/master/go.mod#L70
2. Merge docs: 0.19 changelog #9707

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

[galargh]

🎉 Kubo v0.19.0 is out!

[galargh]

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