cacache - npm Package Versions

7.0.3 (2017-04-05)

Bug Fixes

• read: fixing error message for integrity verification failures (9d4f0a5)

<a name="7.0.2"></a>

7.0.2 (2017-04-03)

Bug Fixes

• integrity: use EINTEGRITY error code and update ssri (8dc2e62)

<a name="7.0.1"></a>

7.0.1 (2017-04-03)

Bug Fixes

• docs: fix header name conflict in readme (afcd456)

<a name="7.0.0"></a>

7.0.0 (2017-04-03)

Bug Fixes

• test: fix content.write tests when running in docker (d2e9b6a)

Features

• integrity: subresource integrity support (#78) (b1e731f)

BREAKING CHANGES

• integrity: The entire API has been overhauled to use SRI hashes instead of digest/hashAlgorithm pairs. SRI hashes follow the Subresource Integrity standard and support strings and objects compatible with ssri.

• This change bumps the index version, which will invalidate all previous index entries. Content entries will remain intact, and existing caches will automatically reuse any content from before this breaking change.

• cacache.get.info(), cacache.ls(), and cacache.ls.stream() will now return objects that looks like this:

{
  key: String,
  integrity: '<algorithm>-<base64hash>',
  path: ContentPath,
  time: Date<ms>,
  metadata: Any
}

• opts.digest and opts.hashAlgorithm are obsolete for any API calls that used them.

• Anywhere opts.digest was accepted, opts.integrity is now an option. Any valid SRI hash is accepted here -- multiple hash entries will be resolved according to the standard: first, the "strongest" hash algorithm will be picked, and then each of the entries for that algorithm will be matched against the content. Content will be validated if any of the entries match (so, a single integrity string can be used for multiple "versions" of the same document/data).

• put.byDigest(), put.stream.byDigest, get.byDigest() and get.stream.byDigest() now expect an SRI instead of a digest + opts.hashAlgorithm pairing.

• get.hasContent() now expects an integrity hash instead of a digest. If content exists, it will return the specific single integrity hash that was found in the cache.

• verify() has learned to handle integrity-based caches, and forgotten how to handle old-style cache indices due to the format change.

• cacache.rm.content() now expects an integrity hash instead of a hex digest.

<a name="6.3.0"></a>

6.3.0 (2017-04-01)

Bug Fixes

• fixOwner: ignore EEXIST race condition from mkdirp (4670e9b)
• index: ignore index removal races when inserting (b9d2fa2)
• memo: use lru-cache for better mem management (#75) (d8ac5aa)

Features

• dependencies: Switch to move-concurrently (#77) (dc6482d)

<a name="6.2.0"></a>

6.2.0 (2017-03-15)

Bug Fixes

• index: additional bucket entry verification with checksum (#72) (f8e0f25)
• verify: return fixOwner.chownr promise (6818521)

Features

• tmp: safe tmp dir creation/management util (#73) (c42da71)

<a name="6.1.2"></a>

6.1.2 (2017-03-13)

Bug Fixes

• index: set default hashAlgorithm (d6eb2f0)

<a name="6.1.1"></a>

6.1.1 (2017-03-13)

Bug Fixes

• coverage: bumping coverage for verify (#71) (0b7faf6)
• deps: glob should have been a regular dep :< (0640bc4)

<a name="6.1.0"></a>

6.1.0 (2017-03-12)

Bug Fixes

• coverage: more coverage for content reads (#70) (ef4f70a)
• tests: use safe-buffer because omfg (#69) (6ab8132)

Features

• rm: limited rm.all and fixed bugs (#66) (d5d25ba), closes #66
• verify: tested, working cache verifier/gc (#68) (45ad77a)

<a name="6.0.2"></a>

6.0.2 (2017-03-11)

Bug Fixes

• index: segment cache items with another subbucket (#64) (c3644e5)

<a name="6.0.1"></a>