v0.3.1

What's Changed

• docs(pinning): eliminate copy-n-paste typo by @smoyer64 in #28

New Contributors

• @smoyer64 made their first contribution in #28

Full Changelog: v0.3.0...v0.3.1

v0.3.0

What's Changed

• sync: update CI config files by @web3-bot in #16
• sync: update CI config files by @web3-bot in #20
• sync: update CI config files by @web3-bot in #21
• sync: update CI config files by @web3-bot in #22
• feat!: add and connect missing context, remove RemovePinWithMode by @MichaelMure in #23
• sync: update CI config files by @web3-bot in #26

Full Changelog: v0.2.1...v0.3.0

v0.2.0

This release upgrades dependencies to plumb through datastore interface changes.

v0.1.2

Fixes and optimizations in reindexing. Log every operation.

v0.1.1

Converting from an IPLD backed pinner to a datastore backed one now requires much less memory and does not touch any of the indirect pins stored in the underlying DAGStore.

v0.1.0

Store pins in datastore instead of a DAG

Adds a new /pins namespace to the given datastore and uses that to store pins as cbor binary, keyed by unique pin ID.

The new datastore pinner stores pins in the datastore as individual key-value items. This is faster than the dag pinner, which stored all pins in a single dag that had to be rewritten every time a pin was added or removed.

The new pinner provides a secondary indexing mechanism that can be used to index any data that a pin has. Secondary indexing logic is provided by the dsindex package. The new pinner currently includes indexing by CID.

Both the new datastore pinner (dspinner package) and the old dag pinner (ipldpinner package) implementations are included to support migration between the two. Migration logic is provided by the pinconv package.

Other features in new pinner:

• Benchmarks are provided to compare performance of between the old and new pinners
• New pinner does not keep in-memory set of pinned CIDs, instead it relies on the datastore
• Separate recursive and direct CID indexes allow searching for pins without having to load pin data to check the mode
• New pinner can rebuild indexes on load, if saved pins appear out of sync with the indexes

Breaking Change

Since we now have two pinner implementations (ipldpinner and dspinner) the functions for creating the datastores now lives in the individual packages. The dspinner is much more performant and should be used unless backwards compatibility is needed.

Release v0.0.4

Avoid holding pin lock while fetching updates to a pin.

v0.0.3

Merge pull request #1 from ipfs/feat/async-ds

Support Async Datastores