Skip to content

Release 0.32 #10547

Closed
Closed

Description

@gammazero

Meta

Items In Scope

Required

Fixes for things found in RC:

Nice To Have (Optional)

Closes #9323

Activity

  1. pinned this issue on Oct 18, 2024
  2. lidel commented on Oct 30, 2024

    @lidel
    Contributor

    ✅ Release Checklist (v0.32.0-rc1)

    • merge docs: add note about separate port use #10562
      • resolve CI issues (pinged IPDX)
    • 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
      • update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-RCN)
      • create a draft PR from release-vX.Y to release
      • 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. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
          • 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
    • 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 -m 'Release X.Y.Z'
      • ⚠️ 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
    • Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).
    • Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:
      • Publish the release to DockerHub
        using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
      • Publish the release to dist.ipfs.tech
        using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
        • check out ipfs/distributions
        • create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
        • run ./dist.sh add-version kubo vX.Y.Z(-RCN) to add the new version to the versions file
        • create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
        • wait for the CI workflow run initiated by the merge to master to finish
        • verify the release is available on dist.ipfs.tech
      • 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 ...
      • 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
    • Update Kubo staging environment, see the Running Kubo tests on staging for details.
      • Test last release against the current RC
      • Test last release against the current one
    • Promote the release
      using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...
    • Test the new version with ipfs-companion (currently skipped)
      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 as reviewer
    • Update Kubo docs
      using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...
    • 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
      • 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
      • go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
      • run make mod_tidy
      • create a PR which updates go.mod and go.sum
      • add the PR to the next release milestone
    • Close the release issue
  3. self-assigned this
    on Oct 30, 2024
  4. lidel commented on Oct 30, 2024

    @lidel
    Contributor

    Early testers ping for v0.32.0-rc1 testing ✨ If you have spare time, and don't have /ws listener enabled yet, give AutoTLS a try.

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

  5. lidel commented on Nov 7, 2024

    @lidel
    Contributor

    ✅ Release Checklist (v0.32.0-rc2)

    • 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
      • update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-rcN)
      • create a draft PR from release-vX.Y to release
      • 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. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
          • 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
    • 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 -m 'Release X.Y.Z'
      • ⚠️ 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
    • Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).
    • Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:
      • Publish the release to DockerHub
        using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
      • Publish the release to dist.ipfs.tech
        using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
        • check out ipfs/distributions
        • create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
        • run ./dist.sh add-version kubo vX.Y.Z(-rcN) to add the new version to the versions file
        • create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
        • wait for the CI workflow run initiated by the merge to master to finish
        • verify the release is available on dist.ipfs.tech
      • 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 ...
      • 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
    • Update Kubo staging environment, see the Running Kubo tests on staging for details.
      • Test last release against the current RC
      • Test last release against the current one
    • Promote the release
      using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...
    • Test the new version with ipfs-companion (currently skipped)
      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 as reviewer
    • Update Kubo docs
      using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...
    • 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
      • 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
      • go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
      • run make mod_tidy
      • create a PR which updates go.mod and go.sum
      • add the PR to the next release milestone
    • Close the release issue
  6. added a commit that references this issue on Nov 8, 2024
  7. lidel commented on Nov 8, 2024

    @lidel
    Contributor

    0.32.0-rc2 is ready

  8. lidel commented on Nov 13, 2024

    @lidel
    Contributor

    ✅ Release Checklist (v0.32.0)

    • 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
      • update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-rcN)
      • create a draft PR from release-vX.Y to release
      • 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. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
          • 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
    • 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 -m 'Release X.Y.Z'
      • ⚠️ 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
    • Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).
    • Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:
      • Publish the release to DockerHub
        using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
      • Publish the release to dist.ipfs.tech
        using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
        • check out ipfs/distributions
        • create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
        • run ./dist.sh add-version kubo vX.Y.Z(-rcN) to add the new version to the versions file
        • create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
        • wait for the CI workflow run initiated by the merge to master to finish
        • verify the release is available on dist.ipfs.tech
      • 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 ...
      • 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
    • Update Kubo staging environment, see the Running Kubo tests on staging for details.
      • Test last release against the current RC
      • Test last release against the current one
    • Promote the release
      using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...
    • Test the new version with ipfs-companion (currently skipped)
      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 as reviewer
    • Update Kubo docs
      using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...
    • 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
      • 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
      • go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
      • run make mod_tidy
      • create a PR which updates go.mod and go.sum
      • add the PR to the next release milestone
    • Close the release issue
  9. lidel commented on Nov 14, 2024

    @lidel
    Contributor

    Kubo v0.32.0 is out!

  10. unpinned this issue on Nov 14, 2024
  11. lidel commented on Nov 15, 2024

    @lidel
    Contributor

    Making patch with fix from #10581 (to restore accelerated dht client)

    ✅ Release Checklist v0.32.1

    • 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
      • update the CurrentVersionNumber in version.go in the release-vX.Y branch to vX.Y.Z(-rcN)
      • create a draft PR from release-vX.Y to release
      • 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. Note that the command expects your $GOPATH/src/github.com/ipfs/kubo to include latest commits from release-vX.Y
          • 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
    • 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 -m 'Release X.Y.Z'
      • ⚠️ 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
    • Verify ipfs/distributions's .tool-versions's golang entry is set to the latest go release on the major go branch Kubo is being tested on (see go-version:).
    • Publish to Dockerhub, NPM, and dist.ipfs.tech and GitHub using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-all or follow each step below:
      • Publish the release to DockerHub
        using ./kuboreleaser --skip-check-before --skip-run release --version vX.Y.Z(-rcN) publish-to-dockerhub or ...
      • Publish the release to dist.ipfs.tech
        using ./kuboreleaser release --version vX.Y.Z(-rcN) publish-to-distributions or ...
        • check out ipfs/distributions
        • create new branch: run git checkout -b release-kubo-X.Y.Z(-rcN)
        • run ./dist.sh add-version kubo vX.Y.Z(-rcN) to add the new version to the versions file
        • create and merge the PR which updates dists/kubo/versions and dists/go-ipfs/versions ( and dists/kubo/current and dists/go-ipfs/current)
        • wait for the CI workflow run initiated by the merge to master to finish
        • verify the release is available on dist.ipfs.tech
      • 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 ...
      • 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
    • Update Kubo staging environment, see the Running Kubo tests on staging for details.
      • Test last release against the current RC
      • Test last release against the current one
    • Promote the release
      using ./kuboreleaser release --version vX.Y.Z(-rcN) promote or ...
    • Test the new version with ipfs-companion (currently skipped)
      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 as reviewer
    • Update Kubo docs
      using ./kuboreleaser release --version vX.Y.Z(-rcN) update-ipfs-docs or ...
    • 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
      • 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
      • go over direct dependencies from go.mod in the root directory (NOTE: do not run go get -u as it will upgrade indirect dependencies which may cause problems)
      • run make mod_tidy
      • create a PR which updates go.mod and go.sum
      • add the PR to the next release milestone
    • Close the release issue
  12. reopened this on Nov 15, 2024
  13. lidel commented on Nov 26, 2024

    @lidel
    Contributor

    Delayed by Fleek issues. Finally closed, docs.ipfs.tech and blog include info about 0.32.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions