New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

鈿★笍 v0.28.0 RELEASE 馃殌 #1228

daviddias opened this Issue Feb 19, 2018 · 6 comments


None yet
4 participants
Copy link

daviddias commented Feb 19, 2018

馃殌 This release brings a panoply of bug fixes, perf improvements, testing improvements and new features. Migrating should be smooth.

馃椇 What's left to release

馃敠 Highlights

Spawn IPFS daemons, JS or Go, easier than ever with brand new IPFS Factory (ipfsd-ctl)

The ipfsd-ctl module got a big upgrade and now is capable of spawning JS and Go IPFS Daemons using only JavaScript! The documentation was also updated. We use it for all our tests on js-ipfs, js-ipfs-api and ipfs/interop.

Learn how to use it at

Thanks to @dryajov, @richardschneider for helping make this happen and everyone else that participated in the review of the new API.

馃摚 PubSub is now a 1st class API of libp2p as well

Now both IPFS and libp2p nodes expose the same PubSub API. This enables other applications that want to use the networking stack of IPFS only, including PubSub.

Check the updated example in the js-libp2p repo at

馃捇 Multiple jsipfs CLI updates

The jsipfs has been receiving a lot of love lately, updates include:

  • jsipfs ls -rList directories recursively
  • jsipfs version supports all flags now
  • Other bug fixes

To test it out, install it globally in your machine with npm: npm install ipfs --global.

Thanks @JonKrone and @vmx for shipping this!

馃摉 New example - Add multiple files as a directory in the Browser

You asked and @achingbrain shipped it! A new example to show how virtual directories can be added to IPFS from the Browser. Check it out at:

馃攲 jsipfs shutdown -- stop your daemon remotely

You now can call jsipfs shutdown to turn off your js-ipfs daemon. This comes in handy when you want to stop a remote node and do not have access to the terminal and/or you are running in Windows and interrupt signals don't work in the same way as in Linux.

馃挶 IPLD support for Bitcoin and Zcash

The DAG Api now can resolve through Bitcoin and Zcash blocks in the same way that it can resolve through Ethereum blocks thanks to and Thanks to @vmx for adding support.

Testing is now faster with Jenkins, lot faster

@VictorBjelkholm put a bunch of work and now we have super fast test set up for js-ipfs and its modules (remaining modules still being updated). Now when you submit a PR, you will see "Jenkins". The Jenkins service is running on a beefy machine and has no wait queues! No more waiting for Travis for 6 hours!

馃暥 libp2p-mplex is official and has a spec!

Our interoperable Stream Multiplexer has graduated, it has a spec -- -- and an updated module --

鈷库搱鈿★笍 js-ipfs Dev Team Weekly Sync 馃檶馃徑

The js-ipfs Dev Team has brought back the Weekly Sync ups! These are designed to be short meetings, focused in the work at hand identify what are the top priorities and everyone's focus for the week. Everyone is welcome to join, either as a contributor or just as a listener. Read more about it at #1179.

Release Checklist

馃檶馃徑 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:

鈦夛笍 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 We are also available at the #ipfs channel on Freenode.


This comment has been minimized.

Copy link

daviddias commented Mar 1, 2018

Aaaand it's released!



To 0.29! 馃殌

@daviddias daviddias closed this Mar 5, 2018

@wafflebot wafflebot bot removed the in progress label Mar 5, 2018


This comment has been minimized.

Copy link

mitra42 commented Mar 6, 2018

@diasdavid - For the 0.27 release someone put together a useful list of changes that app developers (building on top of it) should pay attention, is there anything we need to make sure of this time before updating ?


This comment has been minimized.

Copy link

daviddias commented Mar 6, 2018

@mitra42 unless you were accessing some internals directly and you only used the APIs declared by the spec, you should be golden :)


This comment has been minimized.

Copy link

mitra42 commented Mar 6, 2018

Thanks @diasdavid - I'll report if I hit any problems.


This comment has been minimized.

Copy link

maybeuright commented Mar 25, 2018



This comment has been minimized.

Copy link

gpliu commented Apr 6, 2018

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