Release 0.24

[BigLep]

Meta

• Release owner: @hacdias
• Release reviewer: @Jorropo
• Code freeze date: 2023-10-27
• Expected RC date: 2023-11-01 ✅
• 🚢 Expected final release date: 2023-11-08
• Accompanying PR for improving the release process (example):
• Accompanying Issue for updating the infra (example):

Changelog

https://github.com/ipfs/kubo/blob/master/docs/changelogs/v0.24.md (in progress)

Items in scope

https://github.com/orgs/ipfs/projects/16/views/3?filterQuery=iteration%3A%22kubo+0.24%22

Required

• fix(gw): duplicate blocks and range etags boxo#486
• chore: migrate peering to ipfs/boxo #10157
• chore: migrate bootstrap to ipfs/boxo #10158
• Update to https://github.com/libp2p/go-libp2p/releases/tag/v0.32.0 (go-libp2p v0.32.0 and WebRTC Direct #10197)
• Experimental support for WebRTC Direct (part of Enable WebRTC Transport #9724 ) (go-libp2p v0.32.0 and WebRTC Direct #10197)
• go-libp2p 0.32.1

Optional

• feat: path consolidation  #10063
• refactor: namesys cleanup, gateway /ipns/ ttl #10115
• feat: built-in content blocking based on IPIP-383 #10161
• Boxo implementation for skip-raw-block
• Minimally Functional Modular DHT probe-lab/zikade#17

[BigLep]

A few changes this time around...

1. Really going to try an enforce that whatever is in master/main when we hit the RC date is what makes it into the release.
2. Release day is now Wednesday instead of Thursday
3. We have a light "code freeze" a few days before the RC. We aren't opening new PRs at that point, and any open PRs that aren't merged yet should be very close to landing. (This is squishy and we'll be playing it be ear, but point is to set ourselves up to not try and land more functionality the last few days before the RC date.)

[BigLep]

Doh! I hadn't saved the targeted dates for the release in the issue. I have done so now.

The Kubo release process document has also received some updates: https://pl-strflt.notion.site/Kubo-Release-Process-5a5d066264704009a28a79cff93062c4?pvs=4

[BigLep]

For anyone watching, maintainers are still planing to enter code freeze end of day today (2023-10-27) with some minimal extra landing next week before working on the RC on 2023-11-01.

[hacdias]

0.24.0-rc1 Checlist

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)
  • Thunderdome checked out on your system and configured (see the Thunderdome release docs for setup)
  • 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 --skip-check-before release --version vX.Y.Z(-rcN) prepare-branch or ...

  • create a new branch release-vX.Y.Z
    • 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 vX.Y+1.0-dev
    • example
  • update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-RCN)
    • example
  • create a draft PR from release-vX.Y to release
    • example
  • Cherry-pick commits from master to the release-vX.Y.Z 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-vX.Y to release are passing
  • Merge the PR from release-vX.Y 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-vX.Y branch
• Run Thunderdome testing, see the Thunderdome release docs for details
  • create a PR and merge the experiment config into Thunderdome
• Create the release tag
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-RCN) -m 'Prerelease X.Y.Z(-RCN)'
  • ⚠️ tag the HEAD commit of the release branch using git tag -s vX.Y.Z(-RCN) -m 'Release X.Y.Z(-RCN)'
  • ⚠️ verify the tag is signed and tied to the correct commit using git show vX.Y.Z(-RCN)
  • ⚠️ push the tag to GitHub using git push origin vX.Y.Z(-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 vX.Y.Z(-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 dist.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...

  • check out ipfs/distributions
  • run ./dist.sh add-version kubo vX.Y.Z(-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 vX.Y.Z(-rcN) publish-to-npm (⚠️ you might need to run the command a couple of times because GHA might not be able to see the new distribution straight away due to caching) 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 vX.Y.Z(-rcN) publish-to-github or ...

  • create a new release on GitHub
    • RC example
    • FINAL example
    • use the vX.Y.Z(-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 vX.Y.Z(-rcN) promote or ...

  • create an IPFS Discourse topic
    • prerelease example
    • release example
    • use Kubo vX.Y.Z(-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 vX.Y.Z(-rcN) test-ipfs-companion or ...

  • run the e2e
    • use vX.Y.Z(-RCN) as the Kubo image version
  • wait for the e2e workflow run to finish
• Update Kubo in ipfs-desktop
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-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
• Ask Brave to update Kubo in Brave Desktop
  • use this link to create an issue for the new Kubo version
    • basic example, example with additional notes
  • post link to the issue in #shared-pl-brave for visibility
• Create a blog entry on blog.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-rcN) merge-branch or ...

  • create a new branch merge-release-vX.Y.Z from release
  • create and merge a PR from merge-release-vX.Y.Z to master
• Prepare for the next release
  using ./kuboreleaser release --version vX.Y.Z(-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

[hacdias]

Early testers ping for v0.24.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-11-02 conversation:

• New RC with latest libp2p and WebRTC direct as non default
• Then start on Thunderdome
• Given this is an RC, fine to do on Friday 2023-11-03

[hacdias]

0.24.0-rc2 Checklist

This section covers tasks to be done during each release.

• Prepare the release branch and update version numbers accordingly
  using ./kuboreleaser --skip-check-before release --version vX.Y.Z(-rcN) prepare-branch or ...

  • create a new branch release-vX.Y.Z
    • 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 vX.Y+1.0-dev
    • example
  • update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-RCN)
    • example
  • create a draft PR from release-vX.Y to release
    • example
  • Cherry-pick commits from master to the release-vX.Y.Z 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-vX.Y to release are passing
  • Merge the PR from release-vX.Y 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-vX.Y branch
• Run Thunderdome testing, see the Thunderdome release docs for details
  • create a PR and merge the experiment config into Thunderdome
• Create the release tag
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-RCN) -m 'Prerelease X.Y.Z(-RCN)'
  • ⚠️ tag the HEAD commit of the release branch using git tag -s vX.Y.Z(-RCN) -m 'Release X.Y.Z(-RCN)'
  • ⚠️ verify the tag is signed and tied to the correct commit using git show vX.Y.Z(-RCN)
  • ⚠️ push the tag to GitHub using git push origin vX.Y.Z(-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 vX.Y.Z(-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 dist.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...

  • check out ipfs/distributions
  • run ./dist.sh add-version kubo vX.Y.Z(-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 vX.Y.Z(-rcN) publish-to-npm (⚠️ you might need to run the command a couple of times because GHA might not be able to see the new distribution straight away due to caching) 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 vX.Y.Z(-rcN) publish-to-github or ...

  • create a new release on GitHub
    • RC example
    • FINAL example
    • use the vX.Y.Z(-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 vX.Y.Z(-rcN) promote or ...

  • create an IPFS Discourse topic
    • prerelease example
    • release example
    • use Kubo vX.Y.Z(-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 (broken: e2e Tests are broken ipfs-companion#1300)
  using ./kuboreleaser release --version vX.Y.Z(-rcN) test-ipfs-companion or ...

  • run the e2e
    • use vX.Y.Z(-RCN) as the Kubo image version
  • wait for the e2e workflow run to finish
• Update Kubo in ipfs-desktop
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-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
• Ask Brave to update Kubo in Brave Desktop
  • use this link to create an issue for the new Kubo version
    • basic example, example with additional notes
  • post link to the issue in #shared-pl-brave for visibility
• Create a blog entry on blog.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-rcN) merge-branch or ...

  • create a new branch merge-release-vX.Y.Z from release
  • create and merge a PR from merge-release-vX.Y.Z to master
• Prepare for the next release
  using ./kuboreleaser release --version vX.Y.Z(-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

[hacdias]

Early testers ping for v0.24.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.

[hacdias]

0.24.0 Checklist

This section covers tasks to be done during each release.

• Prepare the release branch and update version numbers accordingly
  using ./kuboreleaser --skip-check-before release --version vX.Y.Z(-rcN) prepare-branch or ...

  • create a new branch release-vX.Y.Z
    • 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 vX.Y+1.0-dev
    • example
  • update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-RCN)
    • example
  • create a draft PR from release-vX.Y to release
    • example
  • Cherry-pick commits from master to the release-vX.Y.Z 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-vX.Y to release are passing
  • Merge the PR from release-vX.Y 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-vX.Y branch
• Run Thunderdome testing, see the Thunderdome release docs for details
  • create a PR and merge the experiment config into Thunderdome
• Create the release tag
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-RCN) -m 'Prerelease X.Y.Z(-RCN)'
  • ⚠️ tag the HEAD commit of the release branch using git tag -s vX.Y.Z(-RCN) -m 'Release X.Y.Z(-RCN)'
  • ⚠️ verify the tag is signed and tied to the correct commit using git show vX.Y.Z(-RCN)
  • ⚠️ push the tag to GitHub using git push origin vX.Y.Z(-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 vX.Y.Z(-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 dist.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...

  • check out ipfs/distributions
  • run ./dist.sh add-version kubo vX.Y.Z(-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 vX.Y.Z(-rcN) publish-to-npm (⚠️ you might need to run the command a couple of times because GHA might not be able to see the new distribution straight away due to caching) 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 vX.Y.Z(-rcN) publish-to-github or ...

  • create a new release on GitHub
    • RC example
    • FINAL example
    • use the vX.Y.Z(-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 vX.Y.Z(-rcN) promote or ...

  • create an IPFS Discourse topic
    • prerelease example
    • release example
    • use Kubo vX.Y.Z(-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 (broken: e2e Tests are broken ipfs-companion#1300)
  using ./kuboreleaser release --version vX.Y.Z(-rcN) test-ipfs-companion or ...

  • run the e2e
    • use vX.Y.Z(-RCN) as the Kubo image version
  • wait for the e2e workflow run to finish
• Update Kubo in ipfs-desktop
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-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
• Ask Brave to update Kubo in Brave Desktop
  • use this link to create an issue for the new Kubo version
    • basic example, example with additional notes
  • post link to the issue in #shared-pl-brave for visibility
• Create a blog entry on blog.ipfs.tech
  using ./kuboreleaser release --version vX.Y.Z(-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 vX.Y.Z(-rcN) merge-branch or ...

  • create a new branch merge-release-vX.Y.Z from release
  • create and merge a PR from merge-release-vX.Y.Z to master
• Prepare for the next release
  using ./kuboreleaser release --version vX.Y.Z(-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

[hacdias]

🎉 Kubo v0.24.0 is out!

[BigLep]

Hre was the status of the 0.24 iteration at the end:

board link

Table form (missing some info)

Repository	Title	Status	Theme	Assignees	Reviewers	Status Date
ipfs/distributions	Duplicate DNSLink TXT record	🎉 Done	⚠️ Critical fix or improvement	lidel		Nov 9, 2023
	📌 Standup callouts (last updated 2023-08-20)	🏃‍♀️ In Progress	⚠️ Critical fix or improvement			Aug 3, 2023
ipfs/kubo	Outdated Version Notice	🥞 Todo	⚠️ Critical fix or improvement			Jul 4, 2023
ipfs/kubo	Routing-v1 gateway endpoint not returning enough information	🥞 Todo	⚠️ Critical fix or improvement	hacdias		Nov 4, 2023
	⬇️⬇️⬇️ Security/Operational Incidents ⬇️⬇️⬇️		⚠️ Critical fix or improvement
	⬇️⬇️⬇️ Other Items ⬇️⬇️⬇️		⚠️ Critical fix or improvement
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		⚠️ Critical fix or improvement
ipfs/specs	Publish existing Bitswap specs at specs.ipfs.tech	🎉 Done	🧑🏻‍⚖️ Governance/Specs	lidel	achingbrain, aschmahmann, hannahhoward, lidel, mxinden	Oct 19, 2023
ipfs/specs	feat(gateway): add specification for running the gateway over libp2p	🎉 Done	🧑🏻‍⚖️ Governance/Specs	aschmahmann	hacdias, lidel	Oct 6, 2023
ipfs/specs	Publish UnixFS specifications at specs.ipfs.tech	🔎 In Review	🧑🏻‍⚖️ Governance/Specs	hacdias, lidel	2color, ajnavarro, alanshaw, aschmahmann, ElPaisano, John-LittleBearLabs, lidel, marten-seemann, thibmeu, willscott	Nov 3, 2022
ipfs/specs	Update UnixFS specification	🏃‍♀️ In Progress	🧑🏻‍⚖️ Governance/Specs	Jorropo		Oct 4, 2022
ipfs/spec-generator	Escaping of quotes and <> in code blocks is broken	🥞 Todo	🧑🏻‍⚖️ Governance/Specs	hacdias		Nov 7, 2023
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		🧑🏻‍⚖️ Governance/Specs
ipfs/boxo	feat!: namesys refactor, ipns TTL bubbled up to gateway	🎉 Done	🌉 Gateways and Clients	hacdias	lidel	Oct 18, 2023
ipfs/gateway-conformance	Tests for /ipns paths and Cache-Control HTTP header	🎉 Done	🌉 Gateways and Clients	hacdias	lidel	Oct 10, 2023
ipfs/kubo	refactor: namesys cleanup, gateway /ipns/ ttl	🎉 Done	🌉 Gateways and Clients	hacdias	lidel	Oct 18, 2023
ipfs/kubo	Point users at canonical kubo/client/rpc library	🎉 Done	🌉 Gateways and Clients			Oct 13, 2023
ipfs/boxo	fix(gw): duplicate blocks and range etags	🎉 Done	🌉 Gateways and Clients	hacdias	hacdias, lidel	Oct 31, 2023
ipfs/helia-delegated-routing-v1-http-api	fix!: conform to Delegated Routing V1 HTTP spec	🎉 Done	🌉 Gateways and Clients	hacdias	achingbrain, lidel	Oct 26, 2023
ipfs/boxo	Gateway: max-age, ETag for /ipns requests	🎉 Done	🌉 Gateways and Clients	hacdias		Oct 18, 2023
ipfs/boxo	Consolidate IPFS Path libraries under boxo/path	🎉 Done	🌉 Gateways and Clients	hacdias		Oct 6, 2023
ipfs/go-ipfs-http-client	Archive this repo and move remaining issues to ipfs/kubo	🎉 Done	🌉 Gateways and Clients			Oct 5, 2023
ipfs/boxo	fix(gw): frugal DNSLink lookups on subdomains	🎉 Done	🌉 Gateways and Clients		aschmahmann, hacdias, hsanjuan	Oct 19, 2023
ipfs/boxo	gateway: implement ipip-0445	🔎 In Review	🌉 Gateways and Clients	Jorropo	aschmahmann	Nov 2, 2023
ipfs/rainbow	Update README.md with logo/header	🔎 In Review	🌉 Gateways and Clients		hacdias, lidel	Nov 7, 2023
ipfs/specs	IPIP-0445: Option to Skip Raw Blocks in Gateway Responses	🏃‍♀️ In Progress	🌉 Gateways and Clients	Jorropo	hacdias, lidel, rvagg	Oct 25, 2023
ipfs/boxo	feat(gw): Ipfs-Gateway-Mode: path|trustless	🛑 Blocked	🌉 Gateways and Clients	lidel	Stebalien	Oct 30, 2023
ipfs/kubo	rpc: fix - Unix domain socket maddrs used with NewApi	🥞 Todo	🌉 Gateways and Clients		Jorropo, kubo maintainers	Sep 4, 2023
ipfs/boxo	Gateway: ensure consistent caching of DNS records	🥞 Todo	🌉 Gateways and Clients	hsanjuan		Oct 7, 2023
	👀 bifrost-gateway Project Board		🌉 Gateways and Clients	aschmahmann, hacdias, lidel
protocol/bifrost-community	Expose trustless gateway and delegated routing under new domains with certain policies		🌉 Gateways and Clients
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		🌉 Gateways and Clients
ipfs/rainbow	Performance benchmarking		🌉 Gateways and Clients
ipfs/rainbow	Run gateway-conformance checks in CI		🌉 Gateways and Clients
ipfs/rainbow	Bootstrapping and peering		🌉 Gateways and Clients	hsanjuan
ipfs/bifrost-gateway	feat!: IPNS routing based on IPIP-351 or IPIP-379	🎉 Done	🔀 Content Routing/Providing	hacdias	lidel	Oct 5, 2023
ipfs/boxo	routing/http: add more type and WithDynamicProviderInfo	🎉 Done	🔀 Content Routing/Providing	Jorropo	kubo maintainers	Oct 5, 2023
ipfs/kubo	go-libp2p v0.32.0 and WebRTC Direct	🎉 Done	🔀 Content Routing/Providing	hacdias	Jorropo	Nov 3, 2023
ipfs/specs	IPIP-0388: Routing HTTP API Support for Querying Multiple Routers	🏃‍♀️ In Progress	🔀 Content Routing/Providing	aschmahmann	lidel, masih, willscott	May 11, 2023
ipfs/boxo	routing/http/server: limit response sizes	🥞 Todo	🔀 Content Routing/Providing	hacdias		Nov 7, 2022
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		🔀 Content Routing/Providing
ipfs/boxo	New very fast unixfs implementation.	🏃‍♀️ In Progress	🚇 Data Transfer	Jorropo		Nov 2, 2023
ipfs/boxo	New Unixfs implementations	🏃‍♀️ In Progress	🚇 Data Transfer	Jorropo		Oct 5, 2023
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		🚇 Data Transfer
ipfs/kubo	feat: built-in content blocking based on IPIP-383	🎉 Done	🐙 Other Initiative	hsanjuan, lidel	hacdias, lidel	Oct 28, 2023
ipfs/kubo	IPFS filtering to allow node operators to decide on content they are willing to serve	🎉 Done	🐙 Other Initiative	hsanjuan		Oct 28, 2023
ipfs/kubo	docs: fix accelerated-dht-client	🎉 Done	🐙 Other Initiative		aschmahmann, Jorropo	Nov 6, 2023
ipfs/ipfs-docs	feat: add /how-to/detect-ipfs-on-web	🔎 In Review	🐙 Other Initiative	ElPaisano	autonome, ElPaisano, SgtPooki	Sep 26, 2023
ipfs/ipfs-docs	Article on data import options & tradeoffs	🏃‍♀️ In Progress	🐙 Other Initiative	ElPaisano		Sep 26, 2023
ipfs/kubo	fully remove mplex	🥞 Todo	🐙 Other Initiative	Jorropo		Aug 15, 2023
ipfs/kubo	Enable WebRTC Transport	🥞 Todo	🐙 Other Initiative	hacdias		Aug 23, 2023
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		🐙 Other Initiative
	Jorropo IPFS Connect talk		🐙 Other Initiative
ipfs/boxo	Routing V1 CLI Example	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	lidel	Oct 5, 2023
ipfs/boxo	feat(path)!: consolidated path libraries	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	aschmahmann, Jorropo, lidel	Oct 6, 2023
ipfs/kubo	feat: path consolidation	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	kubo maintainers, lidel	Oct 6, 2023
ipfs/boxo	How to use Boxo library or SDK for IPFS with Go language?	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias		Oct 9, 2023
ipfs/boxo	docs: how to use and create examples	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	aschmahmann, BigLep, kubo maintainers, lidel	Oct 16, 2023
ipfs/ipfs-docs	Clean Kubo Client Story and Deprecated Packages	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	2color, ElPaisano, lidel	Oct 10, 2023
ipfs/kubo	docs: clean mentions of go-ipfs-api, go-ipfs-http-api	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	BigLep, kubo maintainers, lidel	Oct 13, 2023
ipfs/ipget	chore: upgrade to Go 1.21	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	hsanjuan	Oct 18, 2023
ipfs/boxo	feat!: remove util.MultiErr	🎉 Done	👷🏾 Maintainer/Contributor Experience	hacdias	aschmahmann	Oct 17, 2023
ipfs/kubo	feat: cmd/ipfs: Make it possible to depend on cmd/ipfs	🔎 In Review	👷🏾 Maintainer/Contributor Experience	aschmahmann		Mar 31, 2023
ipfs/boxo	Flaky test: TestReprovider/many	🥞 Todo	👷🏾 Maintainer/Contributor Experience			Jun 22, 2023
ipfs/kubo	Retire kubo-as-a-library	🥞 Todo	👷🏾 Maintainer/Contributor Experience			Oct 9, 2023
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		👷🏾 Maintainer/Contributor Experience
ipfs/kubo	Document SOP for updating go version		👷🏾 Maintainer/Contributor Experience	hacdias, Jorropo
ipfs/boxo	chore: migrate bootstrap	🎉 Done	🤞 Best Effort Improvement		hacdias, Jorropo	Nov 1, 2023
ipfs/kubo	chore: migrate bootstrap to ipfs/boxo	🎉 Done	🤞 Best Effort Improvement		hacdias	Nov 1, 2023
ipfs/kubo	chore: migrate peering to ipfs/boxo	🎉 Done	🤞 Best Effort Improvement	hacdias	hacdias	Oct 31, 2023
ipfs/kubo	commands/add: return an error when using --only-hash and --to-files	🔎 In Review	🤞 Best Effort Improvement		kubo maintainers	Oct 21, 2023
ipfs/kubo	coreapi/unixfs: don't create an additional IpfsNode for --only-hash	🔎 In Review	🤞 Best Effort Improvement		kubo maintainers	Oct 21, 2023
ipfs/kubo	coreapi/unixfs: in /add, don't setup a MFS root with a mock	🔎 In Review	🤞 Best Effort Improvement		kubo maintainers	Oct 21, 2023
ipfs/kubo	feat: daemon: automatically set GOMEMLIMIT if it is unset	🥞 Todo	🤞 Best Effort Improvement	Jorropo	ajnavarro, dokterbob, kubo maintainers	Jun 29, 2023
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		🤞 Best Effort Improvement
ipfs/kubo	tests: add new helia intergration tests	🎉 Done	🚅 Release Process, Artifacts, CI/CD		kubo maintainers	Oct 20, 2023
ipfs/kubo	Release 0.23	🎉 Done	🚅 Release Process, Artifacts, CI/CD			Oct 6, 2023
ipfs/kubo	Release 0.24	🎉 Done	🚅 Release Process, Artifacts, CI/CD	hacdias		Nov 8, 2023
ipfs/kubo	Update EARLY_TESTERS.md	🎉 Done	🚅 Release Process, Artifacts, CI/CD		hacdias	Nov 3, 2023
ipfs/kuboreleaser	Kubo v0.22.0 feedback	🏃‍♀️ In Progress	🚅 Release Process, Artifacts, CI/CD	galargh		Aug 3, 2023
	⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️		🚅 Release Process, Artifacts, CI/CD
ipfs/go-graphsync	chore: bump go-libp2p to 0.32.0	🎉 Done		hacdias	Jorropo, rvagg	Nov 3, 2023
ipfs/boxo	chore: bump to [email protected]	🎉 Done		hacdias	Jorropo	Nov 3, 2023
ipfs/go-graphsync	chore: release 0.16.0	🎉 Done		hacdias	rvagg	Nov 3, 2023

List form (more info)

Repository Title Status Theme Assignees Reviewers Status Date
ipfs/distributions Duplicate DNSLink TXT record 🎉 Done ⚠️ Critical fix or improvement lidel Nov 9, 2023
📌 Standup callouts (last updated 2023-08-20) 🏃‍♀️ In Progress ⚠️ Critical fix or improvement Aug 3, 2023
ipfs/kubo Outdated Version Notice 🥞 Todo ⚠️ Critical fix or improvement Jul 4, 2023
ipfs/kubo Routing-v1 gateway endpoint not returning enough information 🥞 Todo ⚠️ Critical fix or improvement hacdias Nov 4, 2023
⬇️⬇️⬇️ Security/Operational Incidents ⬇️⬇️⬇️ ⚠️ Critical fix or improvement
⬇️⬇️⬇️ Other Items ⬇️⬇️⬇️ ⚠️ Critical fix or improvement
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ ⚠️ Critical fix or improvement
ipfs/specs Publish existing Bitswap specs at specs.ipfs.tech 🎉 Done 🧑🏻‍⚖️ Governance/Specs lidel achingbrain, aschmahmann, hannahhoward, lidel, mxinden Oct 19, 2023
ipfs/specs feat(gateway): add specification for running the gateway over libp2p 🎉 Done 🧑🏻‍⚖️ Governance/Specs aschmahmann hacdias, lidel Oct 6, 2023
ipfs/specs Publish UnixFS specifications at specs.ipfs.tech 🔎 In Review 🧑🏻‍⚖️ Governance/Specs hacdias, lidel 2color, ajnavarro, alanshaw, aschmahmann, ElPaisano, John-LittleBearLabs, lidel, marten-seemann, thibmeu, willscott Nov 3, 2022
ipfs/specs Update UnixFS specification 🏃‍♀️ In Progress 🧑🏻‍⚖️ Governance/Specs Jorropo Oct 4, 2022
ipfs/spec-generator Escaping of quotes and <> in code blocks is broken 🥞 Todo 🧑🏻‍⚖️ Governance/Specs hacdias Nov 7, 2023
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 🧑🏻‍⚖️ Governance/Specs
ipfs/boxo feat!: namesys refactor, ipns TTL bubbled up to gateway 🎉 Done 🌉 Gateways and Clients hacdias lidel Oct 18, 2023
ipfs/gateway-conformance Tests for /ipns paths and Cache-Control HTTP header 🎉 Done 🌉 Gateways and Clients hacdias lidel Oct 10, 2023
ipfs/kubo refactor: namesys cleanup, gateway /ipns/ ttl 🎉 Done 🌉 Gateways and Clients hacdias lidel Oct 18, 2023
ipfs/kubo Point users at canonical kubo/client/rpc library 🎉 Done 🌉 Gateways and Clients Oct 13, 2023
ipfs/boxo fix(gw): duplicate blocks and range etags 🎉 Done 🌉 Gateways and Clients hacdias hacdias, lidel Oct 31, 2023
ipfs/helia-delegated-routing-v1-http-api fix!: conform to Delegated Routing V1 HTTP spec 🎉 Done 🌉 Gateways and Clients hacdias achingbrain, lidel Oct 26, 2023
ipfs/boxo Gateway: max-age, ETag for /ipns requests 🎉 Done 🌉 Gateways and Clients hacdias Oct 18, 2023
ipfs/boxo Consolidate IPFS Path libraries under boxo/path 🎉 Done 🌉 Gateways and Clients hacdias Oct 6, 2023
ipfs/go-ipfs-http-client Archive this repo and move remaining issues to ipfs/kubo 🎉 Done 🌉 Gateways and Clients Oct 5, 2023
ipfs/boxo fix(gw): frugal DNSLink lookups on subdomains 🎉 Done 🌉 Gateways and Clients aschmahmann, hacdias, hsanjuan Oct 19, 2023
ipfs/boxo gateway: implement ipip-0445 🔎 In Review 🌉 Gateways and Clients Jorropo aschmahmann Nov 2, 2023
ipfs/rainbow Update README.md with logo/header 🔎 In Review 🌉 Gateways and Clients hacdias, lidel Nov 7, 2023
ipfs/specs IPIP-0445: Option to Skip Raw Blocks in Gateway Responses 🏃‍♀️ In Progress 🌉 Gateways and Clients Jorropo hacdias, lidel, rvagg Oct 25, 2023
ipfs/boxo feat(gw): Ipfs-Gateway-Mode: path|trustless 🛑 Blocked 🌉 Gateways and Clients lidel Stebalien Oct 30, 2023
ipfs/kubo rpc: fix - Unix domain socket maddrs used with NewApi 🥞 Todo 🌉 Gateways and Clients Jorropo, kubo maintainers Sep 4, 2023
ipfs/boxo Gateway: ensure consistent caching of DNS records 🥞 Todo 🌉 Gateways and Clients hsanjuan Oct 7, 2023
👀 bifrost-gateway Project Board 🌉 Gateways and Clients aschmahmann, hacdias, lidel
protocol/bifrost-community Expose trustless gateway and delegated routing under new domains with certain policies 🌉 Gateways and Clients
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 🌉 Gateways and Clients
ipfs/rainbow Performance benchmarking 🌉 Gateways and Clients
ipfs/rainbow Run gateway-conformance checks in CI 🌉 Gateways and Clients
ipfs/rainbow Bootstrapping and peering 🌉 Gateways and Clients hsanjuan
ipfs/bifrost-gateway feat!: IPNS routing based on IPIP-351 or IPIP-379 🎉 Done 🔀 Content Routing/Providing hacdias lidel Oct 5, 2023
ipfs/boxo routing/http: add more type and WithDynamicProviderInfo 🎉 Done 🔀 Content Routing/Providing Jorropo kubo maintainers Oct 5, 2023
ipfs/kubo go-libp2p v0.32.0 and WebRTC Direct 🎉 Done 🔀 Content Routing/Providing hacdias Jorropo Nov 3, 2023
ipfs/specs IPIP-0388: Routing HTTP API Support for Querying Multiple Routers 🏃‍♀️ In Progress 🔀 Content Routing/Providing aschmahmann lidel, masih, willscott May 11, 2023
ipfs/boxo routing/http/server: limit response sizes 🥞 Todo 🔀 Content Routing/Providing hacdias Nov 7, 2022
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 🔀 Content Routing/Providing
ipfs/boxo New very fast unixfs implementation. 🏃‍♀️ In Progress 🚇 Data Transfer Jorropo Nov 2, 2023
ipfs/boxo New Unixfs implementations 🏃‍♀️ In Progress 🚇 Data Transfer Jorropo Oct 5, 2023
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 🚇 Data Transfer
ipfs/kubo feat: built-in content blocking based on IPIP-383 🎉 Done 🐙 Other Initiative hsanjuan, lidel hacdias, lidel Oct 28, 2023
ipfs/kubo IPFS filtering to allow node operators to decide on content they are willing to serve 🎉 Done 🐙 Other Initiative hsanjuan Oct 28, 2023
ipfs/kubo docs: fix accelerated-dht-client 🎉 Done 🐙 Other Initiative aschmahmann, Jorropo Nov 6, 2023
ipfs/ipfs-docs feat: add /how-to/detect-ipfs-on-web 🔎 In Review 🐙 Other Initiative ElPaisano autonome, ElPaisano, SgtPooki Sep 26, 2023
ipfs/ipfs-docs Article on data import options & tradeoffs 🏃‍♀️ In Progress 🐙 Other Initiative ElPaisano Sep 26, 2023
ipfs/kubo fully remove mplex 🥞 Todo 🐙 Other Initiative Jorropo Aug 15, 2023
ipfs/kubo Enable WebRTC Transport 🥞 Todo 🐙 Other Initiative hacdias Aug 23, 2023
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 🐙 Other Initiative
Jorropo IPFS Connect talk 🐙 Other Initiative
ipfs/boxo Routing V1 CLI Example 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias lidel Oct 5, 2023
ipfs/boxo feat(path)!: consolidated path libraries 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias aschmahmann, Jorropo, lidel Oct 6, 2023
ipfs/kubo feat: path consolidation 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias kubo maintainers, lidel Oct 6, 2023
ipfs/boxo How to use Boxo library or SDK for IPFS with Go language? 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias Oct 9, 2023
ipfs/boxo docs: how to use and create examples 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias aschmahmann, BigLep, kubo maintainers, lidel Oct 16, 2023
ipfs/ipfs-docs Clean Kubo Client Story and Deprecated Packages 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias 2color, ElPaisano, lidel Oct 10, 2023
ipfs/kubo docs: clean mentions of go-ipfs-api, go-ipfs-http-api 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias BigLep, kubo maintainers, lidel Oct 13, 2023
ipfs/ipget chore: upgrade to Go 1.21 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias hsanjuan Oct 18, 2023
ipfs/boxo feat!: remove util.MultiErr 🎉 Done 👷🏾 Maintainer/Contributor Experience hacdias aschmahmann Oct 17, 2023
ipfs/kubo feat: cmd/ipfs: Make it possible to depend on cmd/ipfs 🔎 In Review 👷🏾 Maintainer/Contributor Experience aschmahmann Mar 31, 2023
ipfs/boxo Flaky test: TestReprovider/many 🥞 Todo 👷🏾 Maintainer/Contributor Experience Jun 22, 2023
ipfs/kubo Retire kubo-as-a-library 🥞 Todo 👷🏾 Maintainer/Contributor Experience Oct 9, 2023
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 👷🏾 Maintainer/Contributor Experience
ipfs/kubo Document SOP for updating go version 👷🏾 Maintainer/Contributor Experience hacdias, Jorropo
ipfs/boxo chore: migrate bootstrap 🎉 Done 🤞 Best Effort Improvement hacdias, Jorropo Nov 1, 2023
ipfs/kubo chore: migrate bootstrap to ipfs/boxo 🎉 Done 🤞 Best Effort Improvement hacdias Nov 1, 2023
ipfs/kubo chore: migrate peering to ipfs/boxo 🎉 Done 🤞 Best Effort Improvement hacdias hacdias Oct 31, 2023
ipfs/kubo commands/add: return an error when using --only-hash and --to-files 🔎 In Review 🤞 Best Effort Improvement kubo maintainers Oct 21, 2023
ipfs/kubo coreapi/unixfs: don't create an additional IpfsNode for --only-hash 🔎 In Review 🤞 Best Effort Improvement kubo maintainers Oct 21, 2023
ipfs/kubo coreapi/unixfs: in /add, don't setup a MFS root with a mock 🔎 In Review 🤞 Best Effort Improvement kubo maintainers Oct 21, 2023
ipfs/kubo feat: daemon: automatically set GOMEMLIMIT if it is unset 🥞 Todo 🤞 Best Effort Improvement Jorropo ajnavarro, dokterbob, kubo maintainers Jun 29, 2023
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 🤞 Best Effort Improvement
ipfs/kubo tests: add new helia intergration tests 🎉 Done 🚅 Release Process, Artifacts, CI/CD kubo maintainers Oct 20, 2023
ipfs/kubo Release 0.23 🎉 Done 🚅 Release Process, Artifacts, CI/CD Oct 6, 2023
ipfs/kubo Release 0.24 🎉 Done 🚅 Release Process, Artifacts, CI/CD hacdias Nov 8, 2023
ipfs/kubo Update EARLY_TESTERS.md 🎉 Done 🚅 Release Process, Artifacts, CI/CD hacdias Nov 3, 2023
ipfs/kuboreleaser Kubo v0.22.0 feedback 🏃‍♀️ In Progress 🚅 Release Process, Artifacts, CI/CD galargh Aug 3, 2023
⬆️⬆️⬆️ Items that should make it into this iteration ⬆️⬆️⬆️ 🚅 Release Process, Artifacts, CI/CD
ipfs/go-graphsync chore: bump go-libp2p to 0.32.0 🎉 Done hacdias Jorropo, rvagg Nov 3, 2023
ipfs/boxo chore: bump to [email protected] 🎉 Done hacdias Jorropo Nov 3, 2023
ipfs/go-graphsync chore: release 0.16.0 🎉 Done hacdias rvagg Nov 3, 2023