⚡️ v0.39.0 RELEASE 🚀

[achingbrain]

🗺 What's left for release

• feat: Allow daemon to init and start in a single command
• fix: Limit concurrent HTTP requests in browser
• feat: Config profiles
• feat: Web UI 2.5.4
• feat: Support block rm over HTTP API

Future release:

• feat: Enable DHT in client mode
• feat: Reprovider
• feat: Repo migration tool
• fix: Locking for concurrent pin ops
• fix: Offline blockstore for pinning
• perf: Cache to improve pin performance

🚢 Estimated shipping date

23rd October

🔦 Highlights

🏗 API Changes

✅ Release Checklist

• Stage 0 - Automated Testing
  • Feature freeze. If any "non-trivial" changes (see the footnotes of docs/releases.md for a definition) get added to the release, uncheck all the checkboxes and return to this stage.
  • Automated Testing (already tested in CI) - Ensure that all tests are passing, this includes:
    • unit/functional/integration/e2e
    • interop
    • sharness (Does not run js-ipfs)
    • all the examples run without problems
    • IPFS application testing
      • webui (Does not depend on js-ifps or js-ipfs-http-client) #2542
      • ipfs-desktop (Does not depend on js-ifps or js-ipfs-http-client) #2542
      • ipfs-companion
      • npm-on-ipfs
      • ipfs-pubsub-room
      • peer-base
      • service-worker-gateway
    • Third party application testing
      • ipfs-log
      • orbit-db
      • sidetree
• Stage 1 - Internal Testing
  • Documentation
    • Ensure that README.md is up to date
      • Install section
      • API calls
      • Packages Listing
  • Publish a release candidate to npm

    # All succesful builds of master update the `build/last-successful branch which contains a npm-shrinkwrap.json.
    # This command checks that branch out, installs it's dependencies using `npm ci`, creates a release branch
    # (e.g. release/v0.39.x), updates the minor prerelease version (e.g. 0.38.0 -> 0.39.0-rc.0) and publishes it to npm
    npx aegir publish-rc
    
    # Later we may wish to update the rc.  First cherry-picked/otherwise merged the new commits into the release 
    # branch on github (e.g. not locally) and wait for CI to pass.  First update the lockfiles used by ci (n.b. one 
    # day this will be done by our ci tools):
    npx aegir update-release-branch-lockfiles release/v0.39.x
    
    # Then update the rc publisehd on npm.  This command pulls the specified release branch, installs it's dependencies
    # `npm ci`, increments the prerelease version (e.g. 0.39.0-rc.0 -> 0.39.0-rc.1) and publishes it to npm
    npx aegir update-rc release/v0.39.x

  • Network Testing:
    • test lab things - TBD
  • Infrastructure Testing:
    • TBD
  • Stage 2 - Community Dev Testing
  • Reach out to the IPFS early testers listed in docs/EARLY_TESTERS.md for testing this release (check when no more problems have been reported). If you'd like to be added to this list, please file a PR.
  • Reach out on IRC for additional early testers.
• Stage 3 - Community Prod Testing
  • Update js.ipfs.io examples to use the latest js-ipfs
  • Invite the IPFS early testers to deploy the release to part of their production infrastructure.
  • Invite the wider community (link to the release issue):
    • discuss.ipfs.io
    • Twitter
    • IRC
• Stage 4 - Release
  • Take a snapshot of everyone that has contributed to this release (including its direct dependencies in IPFS, libp2p, IPLD and multiformats) using the js-ipfs-contributors module.
  • Publish to npm:

     git checkout release/v0.39.x
    # Re-install dependencies using lockfile (will automatically remove your node_modules folder)
    # (Ensures the versions used for the browser build are the same that have been verified by CI)
    npm ci
    
    # lint, build, test, tag, publish
    npm run release-minor
    
    # reintegrate release branch into master
    git rm npm-shrinkwrap.json yarn.lock
    git commit -m 'chore: removed lock files'
    git checkout master
    git merge release/v0.39.x
    git push

  • Publish a blog post to github.com/ipfs/blog (at minimum, a c&p of this release issue with all the highlights, API changes and thank yous)
  • Broadcasting (link to blog post)
    • Twitter
    • IRC
    • Reddit
    • discuss.ipfs.io
    • Announce it on the IPFS Users Mailing List
  • Copy release notes to the GitHub Release description

❤️ Huge thank you to everyone that made this release possible

• @achingbrain (73 commits, 23 PRs, 4 issues, 64 comments)
• @alanshaw (2 PRs, 1 issue, 14 comments)
• @alx696 (1 issue, 1 comment)
• @aschmahmann (1 issue)
• @AuHau (6 commits, 6 PRs, 1 issue, 10 comments)
• @autonome (2 comments)
• @betamos (1 commit, 1 PR, 1 comment)
• @csuwildcat (1 commit, 1 PR)
• @cwaring (2 comments)
• @daviddias (2 commits, 1 PR, 3 issues, 50 comments)
• @dirkmc (1 commit)
• @guoliu (1 issue, 1 comment)
• @hacdias (2 commits, 1 PR, 1 comment)
• @hazae41 (1 comment)
• @hugomrdias (8 commits, 10 PRs, 1 issue, 16 comments)
• @iiska (1 commit, 1 PR)
• @its-VSP (1 comment)
• @jacobheun (2 commits, 4 PRs, 2 issues, 14 comments)
• @javaadpatel (1 issue)
• @kpp (2 issues, 3 comments)
• @lidel (1 commit)
• @mikeal (9 comments)
• @mkg20001 (2 comments)
• @momack2 (1 comment)
• @npfoss (2 issues, 5 comments)
• @oed (2 issues, 3 comments)
• @orpheus (2 comments)
• @pashoo2 (2 issues, 1 comment)
• @PedroMiguelSS (1 commit, 3 PRs)
• @prayaglehana (2 comments)
• @ptoner (3 comments)
• @reasv (1 issue, 5 comments)
• @rumkin (1 issue)
• @tapaswenipathak (3 comments)
• @vasco-santos (9 commits, 1 PR, 9 comments)
• @vaultec81 (1 issue, 2 comments)
• @vincepmartin (1 commit, 1 PR, 1 issue, 4 comments)
• @vmx (5 comments)
• @yehia67 (1 comment)
• @Ziwei-Wei (1 comment)

🙌🏽 Want to contribute?

Would you like to contribute to the IPFS project and don't know how? Well, there are a few places you can get started:

• Check the issues with the help wanted label in the js-ipfs repo
• Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/team-mgmt/#weekly-ipfs-all-hands
• Hack with IPFS and show us what you made! The All Hands call is also the perfect venue for demos, join in and show us what you built
• Join the discussion at https://discuss.ipfs.io/ and help users finding their answers.
• Join the 🚀 IPFS Core Implementations Weekly Sync 🛰 and be part of the action!

⁉️ Do you have questions?

The best place to ask your questions about IPFS, how it works and what you can do with it is at discuss.ipfs.io. We are also available at the #ipfs channel on Freenode.

[achingbrain]

🥚 0.39.0-rc.0 has been published

[achingbrain]

🐣 0.39.0-rc.1 has been published

[achingbrain]

🐤 v0.39.0-rc.2 has been published

[achingbrain]

v0.39.0 is now available: https://www.npmjs.com/package/ipfs/v/0.39.0