Releases: ipfs-inactive/js-ipfs-http-client
v12.0.1
New Awesome DAGNode (ipld-dag-pb) API
WARNING - This released introduced a breaking change in the DAGNode API, making DAGNode instances immutable objects. For more context, see: ipld/js-ipld-dag-pb#4
Bug Fixes
Features
v11.1.0
v11.0.1
New go-ipfs release support!
This js-ipfs-api adds support to go-ipfs 0.4.4 and you know what, there was no breaking API change, it just works™ (5 🌟 for having an http-api that doesn't get breaking changes when releases happen <3 @whyrusleeping )
So you might be asking, why a Major release then? Well, I considered it a couple of times and it made sense to me that setting an official support to a new go-ipfs version should be a major, but then after publish, I quickly realised that this realisation didn't make sense, but now I can't really roll it back :(. My apologies to all. The good news is that your update is going to go smoothly, enjoy :)
v11.0.0
v10.0.0
This major release comes from a breaking api change at the DAGNode level on the .toJSON and .multihash methods. If you were not using the Object API, your application should be good to upgrade. If you want to learn more about this change, you can read here: #398 (comment)
Features
v9.0.0
Update `add` interface to match interface-ipfs-core
The new interface for add can be found here https://github.com/ipfs/interface-ipfs-core#javascript---ipfsfilesadddata-callback
You can still add files from fs, single or recursively, under the call addFiles.
Adding urls is now under addUrl