⚡️ v0.41.0 RELEASE 🚀

[alanshaw]

One giant leap forward

🗺 What's left for release

• refactor: async await and async iterables
  • refactor: convert examples
• feat: UnixFS v1.5
• perf: UnixFS importer speed-em-ups
• feat: CLI implemented repo stat --human
• feat: CLI implemented bitswap stat --human
• feat: libp2pOptions passed to libp2p bundle function
• feat: [email protected]
• feat: CLI implemented ipfs add --hidden flag
• fix: fix: limit SW registration to content root

🚢 Estimated shipping date

Feb 14

🔦 Highlights

🦁 Async Await and Async Iterables

🎶 In the jungle, the mighty jungle the lion sleeps tonight!
🎶 async await, async await, async await, async await...

We've completed a HUGE refactor to js-ipfs internals 🥳, switching to using Promises and async/await over Callbacks and using async iterables instead of Node.js and Pull Streams. Ok, tell a lie, it's actually not just js-ipfs internals, it's the whole stack, including libp2p, IPLD and multiformats, you might call it a ground up re-write, but, you know, we don't like to brag.

🚨 Oh, wait, serious note - this release brings big breaking changes to the core API so please consult the "API Changes" section below for all the information.

It's been a long and emotional voyage but this refactor brings a plethora of incredible immediate and future benefits to consumers, contributors and core developers that make all the work and effort worthwhile. To summarise, we've:

• Switched to streaming APIs by default to reduce memory pressure
• Reduced API surface area by removing buffering, Node.js and Pull Stream APIs
• Reduced the amount of code in the code base and number of dependencies we depend on (for smaller browser bundles and faster install times)
• Switched to using async iterables to stream data to help make streaming more approachable
• Switched to using async/await so we’ll get better error stack traces and improved readability and maintainability

Using async/await in JavaScript is gaining a lot of traction in the ecosystem and is rapidly becoming the de facto way of writing idiomatic JS. We want js-ipfs to move with the times and continue to be attractive to contributors by using modern JS features, techniques and practices. The big idea with these changes is for the code to be easier to contribute to, easier to understand, easier to maintain, and be faster and smaller than ever.

This change is so big, and so significant, we wrote a whole blog post about it to explain the motivations behind the changes...in excruciating delightful depth 🤣!

We've also compiled some stats on this refactor for your viewing pleasure:

• 27 direct dependencies were removed from our package.json
• 214 fewer modules end up in our browser bundle
• 155 kB lighter browser bundle (unpkg.com/[email protected] vs unpkg.com/[email protected]) - that's 18% smaller!
• 124 kB lighter ipfs-http-client browser bundle (unpkg.com/[email protected] vs unpkg.com/[email protected]) - that's 60% smaller!
• ~2,600 lines of code removed (net)
• ~360 lines of code removed from ipfs-http-client (net)
• ~10 minutes shorter CI run times

...and a lot of those stats are just for js-ipfs and js-ipfs-http-client - the tip of the iceberg! We saw changes similar to this for between 60-70 dependencies across IPFS, libp2p, IPLD and multiformats.

🌗 UnixFS v1.5

Turns out, it's really important for package managers to retain file metadata, particularly last modified time (mtime). File mtime allows them to selectively sync only data that has changed. Up until now if you wanted to host a large data set on IPFS, like a package manager's repository, it would be difficult to update.

"What about the permenant web?" I hear you cry. Well, this absolutely doesn't prevent a particular snapshot of a package manager's repository from being permenantly available. Metadata just enables diffs to be imported, instead of the whole thing. So, when I say "difficult to update", like I did up there, I mean slow and/or impossible. When you have Terabytes (or more) of package data and someone publishes a new package, it's kinda inconvenient to import everything again, when only a little part changed. File mtime is a really good indicator of which things have changed, so you can use it in IPFS now! 🥳

For example, there's two new options to jsipfs add that allow mode and mtime to be preserved as the file is added to IPFS:

$ jsipfs add -r --preserve-mtime --preserve-mode ~/Desktop/gif
added QmT6WX9McZyx5ZoisRgpsjYKDBWnYpMnBLpfAgjW5kavBA gif/yesthisisdog.jpg
added QmXMrFfZ9zHLZKN7xP2dX76YFFhvBJsQkd4fLnTDkyR31Q gif

Ok, no big changes there aside from the new options, buuut, now when you list directory contents you get Mode and Mtime info:

$ jsipfs ls QmXMrFfZ9zHLZKN7xP2dX76YFFhvBJsQkd4fLnTDkyR31Q -v
Mode       Mtime                           Hash                                           Size  Name
-rw-r--r-- Apr 16, 2018, 12:20:33 PM GMT+1 QmT6WX9McZyx5ZoisRgpsjYKDBWnYpMnBLpfAgjW5kavBA 87779 yesthisisdog.jpg

The coolest thing is that it's completely backwards compatible. The CID for a given file/directory only changes if you opt in to metadata, otherwise the CIDs remain the same. Hooray!

There's a bunch of changes that add metadata capability to the CLI, HTTP and core API both for inputs and outputs. There's also a couple of new MFS commands touch and chmod which allow you to change the metadata whenever you like! Magic 🧙‍♂️.

See the API Changes sections below for details of all the new UnixFS v1.5 stuffs.

🏗 API Changes

Core API

There are significant and breaking core API changes in this release. Please see the migration guide.

• IPFS is not a class that can be instantiated - use IPFS.create. An IPFS node instance is not an event emitter.

• The init option passed to IPFS.create will now not take any initialization steps if it is set to false. Previously, the repo would be initialized if it already existed. This is no longer the case. If you wish to initialize a node but only if the repo exists, pass init: { allowNew: false } to the constructor.

• Instance .ready property has been removed. Please use IPFS.create instead.

• IPFS.createNode has been removed, please use IPFS.create instead.

• Callbacks are no longer supported on any API methods. Please use a utility such as callbackify on API methods that return Promises to emulate previous behaviour. See the migration guide for more info.

• Delegated peer and content routing modules are no longer included as part of core (but are still available if starting a js-ipfs daemon from the command line). If you wish to use delegated routing and are creating your node programmatically in Node.js or the browser you must npm install libp2p-delegated-content-routing and/or npm install libp2p-delegated-peer-routing and provide configured instances of them in options.libp2p. See the module repos for further instructions:

  • https://github.com/libp2p/js-libp2p-delegated-content-routing
  • https://github.com/libp2p/js-libp2p-delegated-peer-routing

• add now returns an async iterable.

• add now accepts mode and mtime options on inputs to allow setting mode and mtime metadata for added files. See the core interface docs for more info.

• add results now contain a cid property (a CID instance) instead of a string hash property.

• 🆕 add results now include mode and mtime properties if they were set.

• addReadableStream, addPullStream have been removed. Please see the migration guide for more info.

• addFromStream has been removed. Use add instead.

• addFromFs has been removed. Please use the exported globSource utility and pass the result to add. See the glob source documentation for more details and an example.

• addFromURL has been removed. Please use the exported urlSource utility and pass the result to add. See the URL source documentation for more details and an example.

• bitswap.stat result has changed - wantlist and values are now an array of CID instances and peers is now a string[] of peer IDs.

• bitswap.wantlist now returns an array of CID instances.

• block.rm now returns an async iterable.

• block.rm now yields objects of { cid: CID, error: Error }.

• block.stat result now contains a cid property (whose value is a CID instance) instead of a key property.

• dht.findProvs, dht.provide, dht.put and dht.query now all return an async iterable.

• dht.findPeer, dht.findProvs, dht.provide, dht.put and dht.query now yield/return an object { id: string, addrs: Multiaddr[] } instead of a PeerInfo instance(s).

• 🆕 files.chmod has been added. See the core interface docs for info.

• 🆕 files.flush now returns the root CID for the path that was flushed (/ by default)

• files.lsPullStream and files.lsReadableStream have been removed. Please see the migration guide for more info.

• files.ls now returns an async iterable.

• files.ls results now contain a cid property (whose value is a CID instance) instead of a hash property.

• 🆕 files.ls results now include mode and mtime properties if they were set. See the core interface docs for more info.

• files.ls no longer takes a long option (in core) - you will receive all data by default.

• 🆕 files.mkdir now accepts mode and mtime options to allow setting mode and mtime metadata. See the core interface docs for more info.

• files.readPullStream and files.readReadableStream have been removed. Please see the migration guide for more info.

• files.read now returns an async iterable.

• files.stat result now contains a cid property (whose value is a CID instance) instead of a hash property.

• 🆕 files.stat result now includes mode and mtime properties if they were set. See the core interface docs for more info.

• 🆕 files.touch has been added. See the core interface docs for info.

• 🆕 files.write now accepts mode and mtime options to allow setting mode and mtime metadata. See the core interface docs for more info.

• get now returns an async iterable. The content property value for objects yielded from the iterator is now an async iterable that yields BufferList objects.

• id result has changed, the addresses property is now a Multiaddr[]

• name.resolve now returns an async iterable. It yields increasingly more accurate resolved values as they are discovered until the best value is selected from the quorum of 16. The "best" resolved value is the last item yielded from the iterator. If you are interested only in this best value you could use it-last to extract it like so:

  const last = require('it-last')
  await last(ipfs.name.resolve('/ipns/QmHash'))

• 🆕 object.get now accepts a timeout option. It will cause the method to throw with a TimeoutError if no data is received within the timeout window. It can be passed as a number or a string. If a number is passed it is interpreted as milliseconds, if a string is passed it is interpreted as a human readable duration.

• ls now returns an async iterable.

• ls results now contain a cid property (whose value is a CID instance) instead of a hash property.

• 🆕 ls results now include mode and mtime properties if they were set. See the core interface docs for more info.

• pin.add results now contain a cid property (a CID instance) instead of a string hash property.

• 🆕 pin.add now accepts a timeout option. It will cause the method to throw with a TimeoutError if no data is received within the timeout window. It can be passed as a number or a string. If a number is passed it is interpreted as milliseconds, if a string is passed it is interpreted as a human readable duration.

• pin.ls now returns an async iterable.

• pin.ls results now contain a cid property (a CID instance) instead of a string hash property.

• pin.rm results now contain a cid property (a CID instance) instead of a string hash property.

• ping now returns an async iterable.

• refs and refs.local now return an async iterable.

• 🆕 refs now accepts a timeout option. It will cause the method to throw with a TimeoutError if no data is received within the timeout window. It can be passed as a number or a string. If a number is passed it is interpreted as milliseconds, if a string is passed it is interpreted as a human readable duration.

• repo.gc now returns an async iterable.

• stats.bw now returns an async iterable.

• swarm.peers now returns an array of objects with a peer property that is a string, instead of a PeerId instance.

• swarm.addrs now returns an array of objects { id: string, addrs: Multiaddr[] } instead of PeerInfo instances.

HTTP API

• 🆕 /api/v0/add now supports the following additional multipart headers to allow mode and mtime metadata to be set on individual files:
  • mode file mode to apply to created UnixFS entries [string]
  • mtime modification time in seconds before or since the Unix Epoch to apply to created UnixFS entries [number]
  • mtime-nsecs modification time fraction in nanoseconds [number]
• 🆕 /api/v0/add now returns file Mode, Mtime and MtimeNsecs if set.
• /api/v0/file/ls has been removed, please use /api/v0/ls instead.
• 🆕 /api/v0/files/chmod has been added and supports the following query string args:
  • arg path of file to apply mode to [string]
  • mode file mode to apply [string]
• 🆕 /api/v0/files/ls now returns file Mode, Mtime and MtimeNsecs if set.
• 🆕 /api/v0/files/mkdir now supports supports the following additional query string args:
  • mode file mode to apply [string]
  • mtime modification time in seconds before or since the Unix Epoch to apply [number]
• 🆕 /api/v0/files/stat now returns file Mode, Mtime and MtimeNsecs if set.
• 🆕 /api/v0/files/touch has been added and supports the following query string args:
  • arg path of file to apply mode to [string]
  • mtime modification time in seconds before or since the Unix Epoch to apply [number]
• 🆕 /api/v0/files/write now supports the following additional multipart headers:
  • mode file mode to apply to created UnixFS entries [string]
  • mtime modification time in seconds before or since the Unix Epoch to apply to created UnixFS entries [number]
• 🆕 /api/v0/ls now returns file Mode, Mtime and MtimeNsecs if set.

CLI

• 🆕 jsipfs add [file...] now supports the following flags to respect and apply mode and mtime metadata of files added from the file system or explicitly set them:
  • --preserve-mode automatically apply permissions to created UnixFS entries from the file system [boolean] [default: false]
  • --preserve-mtime automatically apply modification time to created UnixFS entries from the file system [boolean] [default: false]
  • --mode file mode to apply to created UnixFS entries [string]
  • --mtime modification time in seconds before or since the Unix Epoch to apply to created UnixFS entries [number]
  • --mtime-nsecs modification time fraction in nanoseconds [number]
• jsipfs file ls has been removed, please use jsipfs ls instead.
• 🆕 jsipfs files chmod [mode] [path] has been added.
• 🆕 jsipfs files ls now prints file mode and mtime.
• 🆕 jsipfs files mkdir now supports the following flags:
  • --mode file mode to apply to created UnixFS entries [string]
  • --mtime modification time in seconds before or since the Unix Epoch to apply to created UnixFS entries [number]
• 🆕 jsipfs files stat now prints file mode and mtime.
• 🆕 jsipfs files touch [path] has been added and supports the following flags:
  • --mtime modification time in seconds before or since the Unix Epoch to apply to created UnixFS entries [number]
• 🆕 jsipfs files write now supports the following flags:
  • --mode file mode to apply to created UnixFS entries [string]
  • --mtime modification time in seconds before or since the Unix Epoch to apply to created UnixFS entries [number]
• 🆕 jsipfs ls now prints file mode and mtime.

Other changes

• libp2p has been upgraded to 0.27, which also includes breaking changes to it's core API. Please see the release announcement post for more info:
  • https://blog.ipfs.io/2020-02-07-js-libp2p-0-27/
• The protocol name for peer IDs in multiaddrs has changed from 'ipfs' to 'p2p'. There's no changes to data on the wire but this change is seen when multiaddrs are converted to strings.

✅ 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-ipfs or js-ipfs-http-client)
      • ipfs-desktop (Does not depend on js-ipfs or js-ipfs-http-client)
      • ipfs-companion Migration to JS API with Async Await and Async Iterables ipfs-companion#843
      • npm-on-ipfs preparations for js-ipfs 0.41 ipfs-shipyard/npm-on-ipfs#123
      • ipfs-pubsub-room does not depend on IPFS anymore chore: remove ipfs-pubsub-room from CI #2765
      • peer-base preparations for js-ipfs 0.41 peer-base/peer-base#321
      • service-worker-gateway deps(dev): bump webpack from 5.77.0 to 5.90.3 service-worker-gateway#44
    • Third party application testing
      • ipfs-log preparations for js-ipfs 0.41 orbitdb-archive/ipfs-log#296
      • orbit-db preparations for js-ipfs 0.41 orbitdb/orbitdb#762
      • sidetree preparations for js-ipfs 0.41 decentralized-identity/sidetree#394
• Stage 1 - Internal Testing
  • Documentation
    • Ensure that README.md is up to date docs: update README #2750
      • Install section
      • API calls
      • Packages Listing
  • Publish a release candidate to npm

    # All successful builds of master update the `build/last-successful` branch
    # which contains an `npm-shrinkwrap.json`.
    # This command checks that branch out, installs it's dependencies using `npm ci`,
    # creates a release branch (e.g. release/v0.34.x), updates the minor prerelease
    # version (e.g. 0.33.1 -> 0.34.0-rc.0) and publishes it to npm.
    npx aegir publish-rc
    
    # Later we may wish to update the rc. First cherry-pick/otherwise merge the
    # new commits into the release branch on github (e.g. not locally) and wait
    # for CI to pass. Then update the lockfiles used by CI (n.b. one day this
    # will be done by our ci tools) with this command:
    npx aegir update-release-branch-lockfiles release/v0.34.x
    
    # Then update the rc published on npm. This command pulls the specified
    # release branch, installs it's dependencies `npm ci`, increments the  
    # prerelease version (e.g. 0.34.0-rc.0 -> 0.34.0-rc.1) and publishes it
    # to npm.
    npx aegir update-rc release/v0.34.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 refactor: examples for js-ipfs 0.41 ipfs-inactive/old-js-ipfs-website#270
  • 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 https://discuss.ipfs.io/t/js-ipfs-v0-41-0-release-candidate/7241
    • Twitter https://twitter.com/_alanshaw/status/1227187540911894528
    • 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.34.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.34.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 https://twitter.com/_alanshaw/status/1227979118895157248
    • IRC
    • Reddit https://www.reddit.com/r/ipfs/comments/f3cnsj/js_ipfs_v0410_release/
    • discuss.ipfs.io https://discuss.ipfs.io/t/js-ipfs-v0-41-0-release/7263
    • Announce it on the IPFS Users Mailing List https://groups.google.com/forum/#!topic/ipfs-users/kS-Gw63gCtI
  • Copy release notes to the GitHub Release description

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

• @achingbrain (159 commits, 69 PRs, 10 issues, 121 comments)
• @adamsoffer (2 comments)
• @AdityaNambiar (1 issue, 1 comment)
• @AgentJ-WR (1 PR, 1 issue)
• @agowa338 (1 issue)
• @alanhoff (1 comment)
• @alanshaw (85 commits, 88 PRs, 12 issues, 177 comments)
• @AliMirlou (1 comment)
• @andylim0221 (1 comment)
• @AuHau (1 issue, 3 comments)
• @autonome (4 comments)
• @blakebyrnes (1 issue, 1 comment)
• @bonedaddy (1 comment)
• @bugeats (1 comment)
• @calikevuche (1 issue, 1 comment)
• @carsonfarmer (14 commits, 9 PRs, 4 issues, 27 comments)
• @chriamue (1 PR)
• @claassistantio (3 comments)
• @codecov-io (9 comments)
• @coryschwartz (1 PR, 1 comment)
• @DallasC (1 issue)
• @DaniellMesquita (3 comments)
• @dannyid (1 comment)
• @daviddias (6 commits, 3 PRs, 2 issues, 21 comments)
• @DieMyst (1 issue)
• @dignifiedquire (2 comments)
• @dirkmc (11 commits, 5 PRs, 9 comments)
• @dostu (1 comment)
• @ekkis (1 issue, 6 comments)
• @elmariachi111 (1 comment)
• @emclab (4 issues, 7 comments)
• @eordano (1 PR)
• @folex (1 comment)
• @ggarri (1 commit, 1 PR, 3 issues, 5 comments)
• @hacdias (9 commits, 4 PRs, 1 issue, 15 comments)
• @hiddentao (1 comment)
• @hugomrdias (48 commits, 10 PRs, 3 issues, 41 comments)
• @iameddieyayaya (1 comment)
• @ilirhushi (2 PRs, 2 comments)
• @inspiraluna (2 comments)
• @jacobheun (123 commits, 28 PRs, 3 issues, 55 comments)
• @jimpick (1 commit, 1 PR)
• @joequant (1 issue)
• @john-osullivan (1 issue, 4 comments)
• @Jorropo (1 PR)
• @kawmaiparis (1 issue)
• @khartig (1 issue)
• @kottackalsulvin (2 issues)
• @kuabhish (4 comments)
• @kumavis (1 PR, 1 issue, 6 comments)
• @leandroyalet (2 comments)
• @lidel (6 commits, 3 PRs, 12 comments)
• @Maj0rT (2 issues, 1 comment)
• @mariotaku (1 issue, 2 comments)
• @mburns (5 PRs, 1 comment)
• @mcclure (1 issue, 2 comments)
• @michaelsbradleyjr (1 comment)
• @mikeal (5 commits, 3 PRs, 3 issues, 18 comments)
• @mohe2015 (1 comment)
• @momack2 (1 comment)
• @mpetrunic (1 issue, 1 comment)
• @mqklin (1 issue, 1 comment)
• @My9Bot (1 comment)
• @nhynes (2 comments)
• @npfoss (1 comment)
• @oed (1 comment)
• @olizilla (2 commits, 1 PR, 11 comments)
• @parkan (1 comment)
• @pcowgill (1 commit, 2 PRs, 7 issues, 41 comments)
• @PedroMiguelSS (6 commits, 6 PRs, 3 comments)
• @peter-donovan (1 comment)
• @posix4e (1 issue)
• @Prabhakar-Poudel (2 comments)
• @pvsmounish (1 comment)
• @qu37zal (1 issue)
• @raulk (1 comment)
• @raullaprida (1 issue, 1 comment)
• @ribasushi (1 issue, 2 comments)
• @ridenaio (2 issues)
• @Rkrushanovskij (1 issue, 1 comment)
• @robertkiel (3 issues, 2 comments)
• @ruifortes (3 issues)
• @rvagg (3 commits, 4 PRs, 5 comments)
• @SahidMiller (1 comment)
• @Schwartz10 (1 issue)
• @shamb0t (1 issue, 1 comment)
• @shresthagrawal (1 commit, 1 PR, 1 issue, 7 comments)
• @stale (3 comments)
• @Stebalien (4 commits, 3 PRs, 1 issue, 10 comments)
• @SvenMeyer (1 issue, 4 comments)
• @tapaswenipathak (1 commit)
• @terichadbourne (3 comments)
• @travisperson (1 comment)
• @tuyennhv (1 comment)
• @uchetron (1 PR)
• @uluhonolulu (1 comment)
• @vasco-santos (92 commits, 42 PRs, 5 issues, 56 comments)
• @Velenir (1 issue)
• @vmx (22 commits, 1 PR, 1 issue, 25 comments)
• @vweevers (1 comment)
• @wehriam (1 comment)
• @wemeetagain (16 commits, 4 PRs, 5 comments)
• @xmaysonnave (1 issue, 1 comment)
• @zhoreeq (1 comment)
• @zicmama (1 comment)
• @zot (2 comments)

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

[wehriam]

What steps are required to define the issue and include a resolution for #2161 in this release? Transmitting large files between browsers seems like a primary use case.

[alanshaw]

With any luck this will be magically be fixed in this version with the new libp2p release which includes libp2p/js-libp2p-mplex#100

I agree this is an important bug to get squashed. If you’re willing it would be good to get your testing when the prerelease comes out.

[alanshaw]

[alanshaw]

🥚 0.41.0-rc.0 is out now!

[alanshaw]

🐣 0.41.0-rc.1 is out now!

[alanshaw]

🐥 0.41.0-rc.2 is out now with a bitswap fix.