⚡️ v0.33.0 RELEASE 🚀

[alanshaw]

All new Web UI - Check on your node stats, explore the IPLD powered merkle forest, see peers around the world and manage your files, without needing to touch the CLI

🗺 What's left for release

• [x] WebUI 2.0 (and https://github.com/ipfs/js-ipfs/pull/1595)
• [x] CID tool
• [x] IPLD breaking change
• [x] fix to libp2p record
• [x] fix for 'datastore key does not have a valid format'

🔦 Highlights

🕹 Web UI 2.0

The IPFS Web UI has been given a HUGE revamp and is now 10x, no, 100x better than before! 😄

• Check the status of your node, it's Peer ID and connection info, the network traffic and the number of connected peers
• Easily manage files in your IPFS repo. You can drag and drop to add files, move and rename them, delete, share or download them
• You can explore IPLD data that underpins how IPFS works
• See all of your connected peers, geolocated by their IP address
• Review the settings for your IPFS node, and update them to better suit your needs

Files	Explore	Peers	Settings

🛠 CID tool

A command line tool for converting, formatting and discovering properties of CIDs.

In the near future IPFS will be switching it's default CID version for added content to version 1 and will use base 32 encoding for serialized CIDs. This tool gives you the power to inspect and learn about CIDs as well as convert any CIDs you've been using from whatever base they're encoded in to a different base!

• Documentation
• Demo video

🏗 API Changes

• Added CLI command ipfs cid [sub-command]
  • View the help with ipfs cid --help or view the documentation online
• ipfs.types.dagCBOR and ipfs.types.dagPB have been removed
  • See #1626 and #374 for more information
• dag-cbor nodes retrieved from ipfs.dag.get now represent links as CID instances not {"/": "base-encoded-cid"} objects
  • See #1668 for more information

✅ Release Checklist

• Robustness and quality
  • [x] Ensure that all tests are passing, this includes:
  • [x] unit
  • [x] interop
  • [x] sharness
  • [x] Publish a release candidate to npm

    # Current version is 0.31.7, to publish a release candidate for 0.32.0:
    npm run build
    npm version 0.32.0-rc.1
    # Publish with "next" tag to ensure people still get 0.31.7 when they `npm i ipfs`
    npm publish --tag next
    git push origin master v0.32.0-rc.1

  • [x] Run tests of the following projects with the new release:
  • [x] ipfs-pubsub-room
  • [x] peer-star-app
  • [x] ipfs-log
  • [x] orbit-db
• Documentation
  • [x] Ensure that README.md is up to date
  • [x] Ensure that all the examples run
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/browser-add-readable-stream
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/browser-browserify
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/browser-mfs
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/browser-readablestream
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/browser-script-tag
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/browser-video-streaming
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/browser-webpack
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/circuit-relaying
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/custom-ipfs-repo
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/custom-libp2p
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/exchange-files-in-browser
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/explore-ethereum-blockchain
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/ipfs-101
  • [ ] https://github.com/ipfs/js-ipfs/tree/master/examples/run-in-electron
    • Known issue: https://github.com/ipfs/js-ipfs/issues/1584
  • [x] https://github.com/ipfs/js-ipfs/tree/master/examples/traverse-ipld-graphs
• Communication
  • [x] Create the release issue
  • [x] Announcements (both pre-release and post-release)
  • [x] Twitter
  • [x] IRC
  • [x] Reddit
  • [x] Blog post

🙌🏽 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 at the Ready column in our waffle board - https://waffle.io/ipfs/js-ipfs?label=help%20wanted
• Join an IPFS All Hands, introduce yourself and let us know where you would like to contribute - https://github.com/ipfs/pm/#all-hands-call
• 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 http://discuss.ipfs.io/ and help users finding their answers.
• Join the ⚡️ⒿⓈ Core Dev Team Weekly Sync 🙌🏽 and be part of the Sprint 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.

[daviddias]

Wooollt!! Looking forward to get this release!!!

[daviddias]

Shall the latest and greatest libp2p advancements go into this release as well? @jacobheun @vasco-santos ?

[daviddias]

The IPLD breaking change has been merged to master. Now the last mile is getting those Ping tests to pass. @jacobheun @vasco-santos can we have your help on figuring out those? https://github.com/ipfs/js-ipfs/issues/1635#issuecomment-434600441 might get us better debugging capabilities

[daviddias]

Master has now all tests passing with flying colors 🌈 @alanshaw wanna drive this release home?! 🌟

[marcusnewton]

@diasdavid I would love if this is released like right now. Intending to demo IPFS to some people today and the current globe is too laggy for my computer!

[daviddias]

@marcusnewton1 it might not be in the next 60 minutes, but if you use js-ipfs master, you should be golden!

[daviddias]

It seems that the WebUI is always thinking that the HTTP API port is 5001 and therefore fails to automatically load with js-ipfs daemon

[daviddias]

That said, this looks amazing btw!!

[marcusnewton]

@diasdavid Well done guys.

[olizilla]

@diasdavid you should be able to load webui from :5002 and it should work out of the box. I'm looking into it.

[alanshaw]

@marcusnewton1 you can npm install ipfs@0.33.0-rc.4 for now.

[daviddias]

@olizilla it did work indeed, that's my second screenshot https://github.com/ipfs/js-ipfs/issues/1635#issuecomment-435024307

[olizilla]

I've tested on both master (73da4ecc8592a11ea7c4bc2be744cfdd4eb832ec) and ipfs@0.33.0-rc.4 and I can open http://127.0.0.1:5002/webui and have the webui connect to the api on :5002. It does not prompt to enter a custom api port.

If you have custom CORS config, then you may see the help page, and it will reference :5001 as being the api port. As mentioned in https://github.com/ipfs/js-ipfs/issues/1563 I'd like to make the help text in webui be correct for js-ipfs by... changing js-ipfs to use 5001, but changing the default api port is something for a subsequent release.

[marcusnewton]

@alanshaw Yep, worked for me, once I got through npm setup

[daviddias]

(first giphy for Legendary!)

Great work JS Core Team!!! 👏🏽👏🏽👏🏽👏🏽👏🏽