Activity

1. lidel

   self-assigned this

   on Nov 27, 2025
2. lidel

   added

   need/triageNeeds initial labeling and prioritizationNeeds initial labeling and prioritization

   kind/featureA new featureA new feature

   need/maintainer-input

   and removed

   kind/featureA new featureA new feature

   on Nov 27, 2025
3. lidel

   pinned this issue on Nov 27, 2025
4. lidel

   added

   need/maintainers-inputNeeds input from the current maintainer(s)Needs input from the current maintainer(s)

   iteration/2026-q1On maintainer radar for Q1 2026On maintainer radar for Q1 2026

   and removed

   need/maintainer-input

   on Jan 29, 2026
5. lidel commented on Apr 12, 2026

   

   lidel

   on Apr 12, 2026

   Last edited by lidel

   ContributorAuthor

   More actions

   ✅ Release Checklist (v0.41.0-rc1)

   Release types: RC (Release Candidate)

   1. Prepare Release Branch

   • Fetch latest changes: git fetch origin master release
   • Create branch release-vX.Y.Z (base from: master if Z=0 for new minor/major, release if Z>0 for patch)
   • RC1 only: Switch to master branch and prepare for next release cycle:
     • Update version.go to vX.Y+1.0-dev (⚠️ double-check Y+1 is correct) (example PR)
     • Create ./docs/changelogs/vX.Y+1.md and add link in CHANGELOG.md
   • Switch to release-vX.Y.Z branch and update version.go to vX.Y.Z(-rcN) (⚠️ double-check Y matches release) (example)
   • Create draft PR: release-vX.Y.Z → release (example)
   • Cherry-pick commits from master into release-vX.Y.Z: git cherry-pick -x <commit> (example)
     • ⚠️ NOTE: -x flag records original commit SHA for traceability and cleaner merge history
   • Verify all CI checks on the PR are passing
   • FINAL only: Replace Changelog and Contributors sections in release-vX.Y.Z with ./bin/mkreleaselog stdout (do NOT copy stderr)
   • FINAL only: Merge PR (release-vX.Y.Z → release) using Create a merge commit
     • ⚠️ do NOT use Squash and merge nor Rebase and merge -- we want the releaser's GPG signature on the merge commit
     • ⚠️ do NOT delete the release-vX.Y.Z branch (needed for future patch releases and git history)

   2. Tag & Publish

   Create Tag

   ⚠️ POINT OF NO RETURN: Once pushed, tags trigger automatic Docker/NPM publishing and are irreversible!
   If you're making a release for the first time, do pair programming and have the release reviewer verify all commands.

   • RC: From release-vX.Y.Z branch: git tag -s vX.Y.Z-rcN -m 'Prerelease X.Y.Z-rcN'
   • FINAL: After PR merge, from release branch: git tag -s vX.Y.Z -m 'Release X.Y.Z'
   • ⚠️ Verify tag is signed and correct: git show vX.Y.Z(-rcN)
   • Push tag: git push origin vX.Y.Z(-rcN)
     • ⚠️ do NOT use git push --tags (pushes all local tags, polluting the repo with noise)
   • STOP: Wait for Docker build to complete before proceeding

   Publish Artifacts

   Parallelism: Docker and dist.ipfs.tech only depend on the pushed tag and can be started in parallel.
   NPM and GitHub Release both depend on dist.ipfs.tech completing first.

   • Docker: Verify docker-image CI passed and image is available on Docker Hub → tags
   • dist.ipfs.tech: Publish to dist.ipfs.tech
     • Check out ipfs/distributions
     • Create branch: git checkout -b release-kubo-X.Y.Z(-rcN)
     • Verify .tool-versions golang matches Kubo's CI go-version: (update if needed)
     • Run: ./dist.sh add-version kubo vX.Y.Z(-rcN) (usage)
     • Create and merge PR (updates dists/kubo/versions, FINAL also updates dists/kubo/current - example)
     • Wait for CI workflow triggered by merge
     • Verify release on dist.ipfs.tech
   • NPM: Publish to NPM
     • Manually dispatch Release to npm workflow if not auto-triggered
     • Verify release on NPM
   • GitHub Release: Publish to GitHub
     • Create release (RC example, FINAL example)
     • Use tag vX.Y.Z(-rcN)
     • Link to release issue
     • RC: Link to changelog, check This is a pre-release
     • FINAL: Copy changelog content (without header), do NOT check pre-release
     • Run sync-release-assets workflow (requires dist.ipfs.tech)
     • Verify assets are attached to the GitHub release

   3. Post-Release

   Technical Tasks

   • FINAL only: Merge release → master
     • Create branch merge-release-vX.Y.Z from release
     • Merge master to merge-release-vX.Y.Z first, and resolve conflict in version.go
       • ⚠️ NOTE: keep the -dev version from master in version.go, discard version from release
     • Create and merge PR from merge-release-vX.Y.Z to master using Create a merge commit
       • ⚠️ do NOT use Squash and merge nor Rebase and merge -- only Create a merge commit preserves commit history and audit trail of what was merged where
   • Update ipshipyard/waterworks-infra
     • Update Kubo staging environment (Running Kubo tests on staging)
       • RC: Test last release against current RC
       • FINAL: Latest release on both boxes
     • FINAL: Update collab cluster boxes to the tagged release
     • FINAL: Update libp2p bootstrappers to the tagged release
   • Update ipfs-desktop
     • Create PR updating kubo version in package.json and package-lock.json
     • Smoke test with IPFS Companion Browser Extension against the PR build
     • FINAL: Merge PR and ship new ipfs-desktop release
   • FINAL only: Update docs.ipfs.tech: run update-on-new-ipfs-tag.yml workflow and merge the PR

   Promotion

   • Create IPFS Discourse topic (RC example, FINAL example)
     • Title: Kubo vX.Y.Z(-rcN) is out!, tag: kubo
     • Use title as heading (##) in description
     • Include: GitHub release link, IPNS binaries, docker pull command, release notes
     • Pin topic globally (make banner if no existing banner)
   • Verify bot posted to #ipfs-chatter (Discord) or #ipfs-chatter:ipfs.io (Matrix)
   • RC only: Comment on release issue mentioning early testers (example)
   • FINAL only: Comment on release issue with link (example)
   • FINAL only: Create blog.ipfs.tech entry (example)
   • FINAL non-PATCH: (optional) Post on social media (bsky, x.com, Reddit)

   Final Steps

   • FINAL non-PATCH: Create dependency update PR
     • Review direct dependencies from root go.mod (⚠️ do NOT run go get -u as it will upgrade indirect dependencies which may cause problems)
     • Run make mod_tidy
     • Create PR with go.mod and go.sum updates
     • Add PR to next release milestone
   • FINAL non-PATCH: Create next release issue (example)
   • FINAL only: Close release issue
6. lidel commented on Apr 14, 2026

   

   lidel

   on Apr 14, 2026

   Last edited by lidel

   ContributorAuthor

   More actions

   Kubo v0.41.0-rc1 is out, pinging early testers:

   • Charity Engine (@Rytiss, @tristanolive)
   • Fission (@bmann)
   • Infura (@MichaelMure)
   • OrbitDB (@haydenyoung)
   • Pinata (@obo20)
   • Shipyard (@cewood, @ns4plabs)
   • Siderus (@koalalorenzo)
   • Textile (@sanderpick)
   • @RubenKelevra

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

   🎉React with 🎉1Reacted by @RubenKelevra
7. lidel commented on Apr 20, 2026

   

   lidel

   on Apr 20, 2026

   Last edited by lidel

   ContributorAuthor

   More actions

   ✅ Release Checklist (v0.41.0-rc2)

   Release types: RC (Release Candidate)

   1. Prepare Release Branch

   • Fetch latest changes: git fetch origin master release
   • Create branch release-vX.Y.Z (base from: master if Z=0 for new minor/major, release if Z>0 for patch)
   • RC1 only: Switch to master branch and prepare for next release cycle:
     • Update version.go to vX.Y+1.0-dev (⚠️ double-check Y+1 is correct) (example PR)
     • Create ./docs/changelogs/vX.Y+1.md and add link in CHANGELOG.md
   • Switch to release-vX.Y.Z branch and update version.go to vX.Y.Z(-rcN) (⚠️ double-check Y matches release) (example)
   • Create draft PR: release-vX.Y.Z → release (example)
   • Cherry-pick commits from master into release-vX.Y.Z: git cherry-pick -x <commit> (example)
     • ⚠️ NOTE: -x flag records original commit SHA for traceability and cleaner merge history
   • Verify all CI checks on the PR are passing
   • FINAL only: Replace Changelog and Contributors sections in release-vX.Y.Z with ./bin/mkreleaselog stdout (do NOT copy stderr)
   • FINAL only: Merge PR (release-vX.Y.Z → release) using Create a merge commit
     • ⚠️ do NOT use Squash and merge nor Rebase and merge -- we want the releaser's GPG signature on the merge commit
     • ⚠️ do NOT delete the release-vX.Y.Z branch (needed for future patch releases and git history)

   2. Tag & Publish

   Create Tag

   ⚠️ POINT OF NO RETURN: Once pushed, tags trigger automatic Docker/NPM publishing and are irreversible!
   If you're making a release for the first time, do pair programming and have the release reviewer verify all commands.

   • RC: From release-vX.Y.Z branch: git tag -s vX.Y.Z-rcN -m 'Prerelease X.Y.Z-rcN'
   • FINAL: After PR merge, from release branch: git tag -s vX.Y.Z -m 'Release X.Y.Z'
   • ⚠️ Verify tag is signed and correct: git show vX.Y.Z(-rcN)
   • Push tag: git push origin vX.Y.Z(-rcN)
     • ⚠️ do NOT use git push --tags (pushes all local tags, polluting the repo with noise)
   • STOP: Wait for Docker build to complete before proceeding

   Publish Artifacts

   Parallelism: Docker and dist.ipfs.tech only depend on the pushed tag and can be started in parallel.
   NPM and GitHub Release both depend on dist.ipfs.tech completing first.

   • Docker: Verify docker-image CI passed and image is available on Docker Hub → tags
   • dist.ipfs.tech: Publish to dist.ipfs.tech
     • Check out ipfs/distributions
     • Create branch: git checkout -b release-kubo-X.Y.Z(-rcN)
     • Verify .tool-versions golang matches Kubo's CI go-version: (update if needed)
     • Run: ./dist.sh add-version kubo vX.Y.Z(-rcN) (usage)
     • Create and merge PR (updates dists/kubo/versions, FINAL also updates dists/kubo/current - example)
     • Wait for CI workflow triggered by merge
     • Verify release on dist.ipfs.tech
   • NPM: Publish to NPM
     • Manually dispatch Release to npm workflow if not auto-triggered
     • Verify release on NPM
   • GitHub Release: Publish to GitHub
     • Create release (RC example, FINAL example)
     • Use tag vX.Y.Z(-rcN)
     • Link to release issue
     • RC: Link to changelog, check This is a pre-release
     • FINAL: Copy changelog content (without header), do NOT check pre-release
     • Run sync-release-assets workflow (requires dist.ipfs.tech)
     • Verify assets are attached to the GitHub release

   3. Post-Release

   Technical Tasks

   • FINAL only: Merge release → master
     • Create branch merge-release-vX.Y.Z from release
     • Merge master to merge-release-vX.Y.Z first, and resolve conflict in version.go
       • ⚠️ NOTE: keep the -dev version from master in version.go, discard version from release
     • Create and merge PR from merge-release-vX.Y.Z to master using Create a merge commit
       • ⚠️ do NOT use Squash and merge nor Rebase and merge -- only Create a merge commit preserves commit history and audit trail of what was merged where
   • Update ipshipyard/waterworks-infra
     • Update Kubo staging environment (Running Kubo tests on staging)
       • RC: Test last release against current RC
       • FINAL: Latest release on both boxes
     • FINAL: Update collab cluster boxes to the tagged release
     • FINAL: Update libp2p bootstrappers to the tagged release
   • Update ipfs-desktop
     • Create PR updating kubo version in package.json and package-lock.json
     • Smoke test with IPFS Companion Browser Extension against the PR build
     • FINAL: Merge PR and ship new ipfs-desktop release
   • FINAL only: Update docs.ipfs.tech: run update-on-new-ipfs-tag.yml workflow and merge the PR

   Promotion

   • Create IPFS Discourse topic (RC example, FINAL example)
     • Title: Kubo vX.Y.Z(-rcN) is out!, tag: kubo
     • Use title as heading (##) in description
     • Include: GitHub release link, IPNS binaries, docker pull command, release notes
     • Pin topic globally (make banner if no existing banner)
   • Verify bot posted to #ipfs-chatter (Discord) or #ipfs-chatter:ipfs.io (Matrix)
   • RC only: Comment on release issue mentioning early testers (example)
   • FINAL only: Comment on release issue with link (example)
   • FINAL only: Create blog.ipfs.tech entry (example)
   • FINAL non-PATCH: (optional) Post on social media (bsky, x.com, Reddit)

   Final Steps

   • FINAL non-PATCH: Create dependency update PR
     • Review direct dependencies from root go.mod (⚠️ do NOT run go get -u as it will upgrade indirect dependencies which may cause problems)
     • Run make mod_tidy
     • Create PR with go.mod and go.sum updates
     • Add PR to next release milestone
   • FINAL non-PATCH: Create next release issue (example)
   • FINAL only: Close release issue
8. lidel commented on Apr 22, 2026

   

   lidel

   on Apr 22, 2026

   ContributorAuthor

   More actions

   Kubo v0.41.0-rc2 is out, pinging early testers:

   • Charity Engine (@Rytiss, @tristanolive)
   • Fission (@bmann)
   • Infura (@MichaelMure)
   • OrbitDB (@haydenyoung)
   • Pinata (@obo20)
   • Shipyard (@cewood, @ns4plabs)
   • Siderus (@koalalorenzo)
   • Textile (@sanderpick)
   • @RubenKelevra

   You're getting this message because you're listed here. Please update this list if you no longer want to be included.
9. lidel commented on Apr 23, 2026

   

   lidel

   on Apr 23, 2026

   Last edited by lidel

   ContributorAuthor

   More actions

   ✅ Release Checklist (v0.41.0)

   Release types: FINAL

   1. Prepare Release Branch

   • Fetch latest changes: git fetch origin master release
   • Create branch release-vX.Y.Z (base from: master if Z=0 for new minor/major, release if Z>0 for patch)
   • RC1 only: Switch to master branch and prepare for next release cycle:
     • Update version.go to vX.Y+1.0-dev (⚠️ double-check Y+1 is correct) (example PR)
     • Create ./docs/changelogs/vX.Y+1.md and add link in CHANGELOG.md
   • Switch to release-vX.Y.Z branch and update version.go to vX.Y.Z(-rcN) (⚠️ double-check Y matches release) (example)
   • Create draft PR: release-vX.Y.Z → release (example)
   • Cherry-pick commits from master into release-vX.Y.Z: git cherry-pick -x <commit> (example)
     • ⚠️ NOTE: -x flag records original commit SHA for traceability and cleaner merge history
   • Verify all CI checks on the PR are passing
   • FINAL only: Replace Changelog and Contributors sections in release-vX.Y.Z with ./bin/mkreleaselog stdout (do NOT copy stderr)
   • FINAL only: Merge PR (release-vX.Y.Z → release) using Create a merge commit
     • ⚠️ do NOT use Squash and merge nor Rebase and merge -- we want the releaser's GPG signature on the merge commit
     • ⚠️ do NOT delete the release-vX.Y.Z branch (needed for future patch releases and git history)

   2. Tag & Publish

   Create Tag

   ⚠️ POINT OF NO RETURN: Once pushed, tags trigger automatic Docker/NPM publishing and are irreversible!
   If you're making a release for the first time, do pair programming and have the release reviewer verify all commands.

   • RC: From release-vX.Y.Z branch: git tag -s vX.Y.Z-rcN -m 'Prerelease X.Y.Z-rcN'
   • FINAL: After PR merge, from release branch: git tag -s vX.Y.Z -m 'Release X.Y.Z'
   • ⚠️ Verify tag is signed and correct: git show vX.Y.Z(-rcN)
   • Push tag: git push origin vX.Y.Z(-rcN)
     • ⚠️ do NOT use git push --tags (pushes all local tags, polluting the repo with noise)
   • STOP: Wait for Docker build to complete before proceeding

   Publish Artifacts

   Parallelism: Docker and dist.ipfs.tech only depend on the pushed tag and can be started in parallel.
   NPM and GitHub Release both depend on dist.ipfs.tech completing first.

   • Docker: Verify docker-image CI passed and image is available on Docker Hub → tags
   • dist.ipfs.tech: Publish to dist.ipfs.tech
     • Check out ipfs/distributions
     • Create branch: git checkout -b release-kubo-X.Y.Z(-rcN)
     • Verify .tool-versions golang matches Kubo's CI go-version: (update if needed)
     • Run: ./dist.sh add-version kubo vX.Y.Z(-rcN) (usage)
     • Create and merge PR (updates dists/kubo/versions, FINAL also updates dists/kubo/current - example)
     • Wait for CI workflow triggered by merge
     • Verify release on dist.ipfs.tech
   • NPM: Publish to NPM
     • Manually dispatch Release to npm workflow if not auto-triggered
     • Verify release on NPM
   • GitHub Release: Publish to GitHub
     • Create release (RC example, FINAL example)
     • Use tag vX.Y.Z(-rcN)
     • Link to release issue
     • RC: Link to changelog, check This is a pre-release
     • FINAL: Copy changelog content (without header), do NOT check pre-release
     • Run sync-release-assets workflow (requires dist.ipfs.tech)
     • Verify assets are attached to the GitHub release

   3. Post-Release

   Technical Tasks

   • FINAL only: Merge release → master
     • Create branch merge-release-vX.Y.Z from release
     • Merge master to merge-release-vX.Y.Z first, and resolve conflict in version.go
       • ⚠️ NOTE: keep the -dev version from master in version.go, discard version from release
     • Create and merge PR from merge-release-vX.Y.Z to master using Create a merge commit
       • ⚠️ do NOT use Squash and merge nor Rebase and merge -- only Create a merge commit preserves commit history and audit trail of what was merged where
   • Update ipshipyard/waterworks-infra
     • Update Kubo staging environment (Running Kubo tests on staging)
       • RC: Test last release against current RC
       • FINAL: Latest release on both boxes
     • FINAL: Update collab cluster boxes to the tagged release
     • FINAL: Update libp2p bootstrappers to the tagged release
   • Update ipfs-desktop
     • Create PR updating kubo version in package.json and package-lock.json
     • Smoke test with IPFS Companion Browser Extension against the PR build
     • FINAL: Merge PR and ship new ipfs-desktop release
   • FINAL only: Update docs.ipfs.tech: run update-on-new-ipfs-tag.yml workflow and merge the PR

   Promotion

   • Create IPFS Discourse topic (RC example, FINAL example)
     • Title: Kubo vX.Y.Z(-rcN) is out!, tag: kubo
     • Use title as heading (##) in description
     • Include: GitHub release link, IPNS binaries, docker pull command, release notes
     • Pin topic globally (make banner if no existing banner)
   • Verify bot posted to #ipfs-chatter (Discord) or #ipfs-chatter:ipfs.io (Matrix)
   • RC only: Comment on release issue mentioning early testers (example)
   • FINAL only: Comment on release issue with link (example)
   • FINAL only: Create blog.ipfs.tech entry (example)
   • FINAL non-PATCH: (optional) Post on social media (bsky, x.com, Reddit)

   Final Steps

   • FINAL non-PATCH: Create dependency update PR
     • Review direct dependencies from root go.mod (⚠️ do NOT run go get -u as it will upgrade indirect dependencies which may cause problems)
     • Run make mod_tidy
     • Create PR with go.mod and go.sum updates
     • Add PR to next release milestone
   • FINAL non-PATCH: Create next release issue (example)
   • FINAL only: Close release issue
10. lidel commented on Apr 24, 2026

    

    lidel

    on Apr 24, 2026

    ContributorAuthor

    More actions

    🎉 Kubo v0.41.0 is out!
11. lidel commented on May 5, 2026

    

    lidel

    on May 5, 2026

    ContributorAuthor

    More actions

    Kubo 0.41 shipped in IPFS Desktop v0.49
12. lidel

    closed this as completedon May 5, 2026
13. lidel

    unpinned this issue on May 5, 2026