mirror of
https://github.com/Instadapp/Swap-Aggregator-Subgraph.git
synced 2024-07-29 21:57:12 +00:00
10 KiB
10 KiB
0.15.3 (2020-06-10)
Features
- serialize Uint8Array as binary (like Buffer) (95f6bda)
0.15.2 (2020-03-27)
Bug Fixes
0.15.1 (2020-01-13)
Bug Fixes
- package: update multicodec to version 1.0.0 (d1d78a0)
- package: update multihashing-async to version 0.8.0 (b8d4a55)
0.15.0 (2019-05-10)
Bug Fixes
- package: update cids to version 0.7.0 (2dc3378)
BREAKING CHANGES
- package: Returned v1 CIDs now default to base32 encoding
Previous versions returned a base58 encoded string when toString()/
toBaseEncodedString() was called on a CIDv1. It now returns a base32
encoded string.
0.14.0 (2019-05-08)
Bug Fixes
- make cbor Decoder configurable (#90) (dfb9137)
- remove console.log statement (a413cb2)
- typo in travis badge (94122f0)
- package: update cids to version 0.6.0 (1d507f7)
- package: update multihashing-async to version 0.6.0 (b328072)
Features
BREAKING CHANGES
- The API is now async/await based
There are numerous changes, the most significant one is that the API is no longer callback based, but it using async/await.
For the full new API please see the IPLD Formats spec.
0.13.1 (2019-01-08)
Bug Fixes
Features
0.13.0 (2018-10-01)
Bug Fixes
- resolve falsy values (0a49705)
Features
- serialize and de-serialize CID instances (8585d65)
BREAKING CHANGES
- return values from de-serializer are now CID instances. Serializer still supports old link objects.
0.12.1 (2018-06-29)
Bug Fixes
Features
BREAKING CHANGES
- the first argument is now the serialized output NOT the dag node. See https://github.com/ipld/interface-ipld-format/issues/32
0.12.0 (2018-02-12)
Bug Fixes
- use binary blobs directly (5321d6a)
BREAKING CHANGES
- Everyone calling the functions of
resolveneed to pass in the binary data instead of an IPFS block.
So if your input is an IPFS block, the code changes from
resolver.resolve(block, path, (err, result) => {…}
to
resolver.resolve(block.data, path, (err, result) => {…}
0.12.0 (2018-02-12)
Bug Fixes
- use binary blobs directly (5321d6a)
BREAKING CHANGES
- Everyone calling the functions of
resolveneed to pass in the binary data instead of an IPFS block.
So if your input is an IPFS block, the code changes from
resolver.resolve(block, path, (err, result) => {…}
to
resolver.resolve(block.data, path, (err, result) => {…}
0.11.2 (2017-11-07)
Features
0.11.1 (2017-04-04)
0.11.0 (2017-03-21)
Features
- use new block api (4ec9228)
0.10.1 (2017-03-16)
0.10.0 (2017-03-13)
0.9.1 (2017-02-09)
0.9.0 (2017-02-02)
0.8.6 (2017-01-31)
Features
0.8.5 (2017-01-29)
0.8.4 (2017-01-29)
0.8.3 (2016-12-11)
Features
0.8.2 (2016-12-01)
0.8.1 (2016-11-21)
0.8.0 (2016-11-03)
0.7.1 (2016-10-30)
0.7.0 (2016-10-26)
Bug Fixes
- add array handling to .tree (656ad84)
- complete migration to async API (2e91d7c)
- out of scope traversal for 2 or more levels deep (b7a565b)
Features
- add util.serialize, util.deserialize and util.cid (fcc2ab5)
- resolve out of scope (bea41ea)
- resolver.resolve within scope (1158fa4)
- resolver.tree and resolver.multicodec (21ddefc)
- use async interfaces (48eb863)
0.6.0 (2016-05-22)
Bug Fixes
- cbor: Typo in lodash.clonedeep (2f617b0)
- Add missing babel-runtime dep (5c11ce8)
- correct references in package.json (12f18ab)
- Ensure inputs are not modified (b20f90b)
Features
- upgrade to latest spec (7375f99)