v0.10.0

Changed

• Breaking: the @interop/was-client peer dependency is renamed to
  @interop/pws-client (>=0.105.0 <1.0.0), following the package's own
  rename. Hosts install @interop/pws-client in its place. pws-client 0.104.0
  and 0.105.0 change what sealed Resources carry (the pws JWE header
  parameter, the PwsEpochConfiguration descriptor state type), so a bundle
  written under an earlier client no longer opens through this version.
• Requires @interop/storage-core 0.44.0, @interop/vh-resource-log 0.11.0 and
  @interop/wallet-core 0.112.0.

v0.9.0

Changed

• Breaking: requires @interop/space-archive 0.11.0. The bundle manifest's own
  manifest.yml entry now cites https://w3id.org/pws#archive-manifest, the
  PWS spec's Archive manifest section, in place of the FEP-6fcd manifest-file
  URL. This is wire text in written bundles; bundles written before this version
  carry the FEP URL. No reader path compares the value (WBU-12).
• Requires @interop/storage-core 0.42.0, @interop/wallet-core 0.109.0 and
  @interop/was-client 0.101.0; test:dist passes again (WBU-13).

Fixed

• The migration test fixtures write the .space.meta.<spaceId>.json and
  .collection.meta.<collectionId>.json names through space-archive's file-name
  builders, and seal chunked fixtures with was-client's spaceUrl codec
  parameter, so the migration tests exercise the Collection Metadata path again.

v0.8.0

Changed

• Breaking: requires @interop/space-archive 0.10.0, which renames the Space
  and Collection Metadata files to .space.meta.<spaceId>.json and
  .collection.meta.<collectionId>.json. Archives written under the old names
  no longer classify. The browser bundle test packs the new name.

v0.7.0

Changed

• Breaking: MIGRATION_WALK_ORDER is renamed MIGRATION_ORDER and
  WALK_STOPPING_ERROR_NAME is renamed MIGRATION_STOPPING_ERROR_NAME. Their
  values are unchanged. A run of migrateBundle is a migration; the readers'
  lazy entry iteration is the entry cursor, space-archive's term (WBU-11).
• A descriptor recipient entry that names a recovered generation but fails its
  AES-KW check (was-client's IntegrityError) is a tamper signal, not a
  generation the migration skips as a non-recipient. In the current epoch the
  generation is dropped and the collection opens with the rest; the report's new
  generationCauses counts the dropped generations by error name. When no
  generation survives, the collection stops under IntegrityError with every
  Resource counted as unopenable. In an older epoch the error is the Resource's
  cause, and no older generation is tried. A sealed index schema whose epoch
  entry fails the check is not handed on, and the report's new
  indexSchemaCause names the error. Both report members are optional and
  additive. Pinned by tests; before, the same entry was reported as
  KeyUnwrapError (WBU-9).
• Requires @interop/was-client 0.99.1 (peer range bumped). Update to latest
  storage-core, space-archive, vh-resource-log and wallet-core deps.
• A corrupt older-epoch entry costs one unwrap per collection, not one per
  Resource under that epoch: was-client 0.99.1 remembers the failed check on the
  cipher. Nothing changed here; a migration test over several Resources under
  such an epoch counts the key-agreement derivations (WBU-10).

v0.6.1

Changed

• Update to latest wallet-core and storage-core deps.

v0.6.0

Changed

• The app-key collection is now app-keys (renamed from app-connections in
  wallet-core). The migration walk counts it under that id.

v0.5.1

Changed

• Update to latest wallet-core and storage-core deps.
• Fix cold-cache reload and fs/path warnings in browser tests.

v0.5.0

Added

• The migration walk migrates chunked Resources in encrypted app collections.
  was-client reassembles each one from the archive's chunk files through a
  chunkSource, and the sink receives it whole as bytes. A missing chunk, a
  chunked envelope with no chunk directory, and a stray chunk directory count as
  unopenable under NotFoundError; a pending stub or a chunk bound to another
  Resource or epoch under EncryptionError.

Changed

• BREAKING: an encrypted collection's Resource reaches
  appCollections.importResource by what it decrypts to. JSON arrives as
  { json } under application/json. A binary or text Resource, small or
  chunked, arrives as { bytes } under its sealed content type
  (application/octet-stream when none), including a chunked Resource sealed as
  application/json. Small binary Resources previously arrived as a Blob in
  json under application/json.

• BREAKING: the @interop/was-client peer range is now >=0.80.0, the release
  that carries chunkSource and exports blobBytes from ./edv/core.

• ChunkedResourceUnsupportedError now covers only a chunked Resource in a
  plaintext app collection or a standard collection.

• BREAKING: the sink port names the migrated unit a Resource. AppCollectionRow
  is now AppCollectionResource, and appCollections.importRow is now
  appCollections.importResource. The parsed JSON payload field is json (was
  row) on every sink method, so app collections take { json } or
  { bytes }.

v0.4.3

Fixed

• Regen the lockfile.

v0.4.2

Fixed

• Remove stray storage-core override.