v0.6.0

@file-transfer/web 0.6.0

Patch Changes

• Updated dependencies [9c5bb91]
  • @file-transfer/transport@1.2.1

@file-transfer/client 0.1.4

Patch Changes

• Updated dependencies [9c5bb91]
  • @file-transfer/sink@0.1.1
  • @file-transfer/transport@1.2.1

@file-transfer/conformance 0.3.0

Minor Changes

• 9c5bb91: Runs on Effect 4.1.0. secureCrypto is renamed secureRandom and provides Effect's SecureRandom (SecureRandom.layerWebCrypto) instead of Crypto, which Effect 4.1.0 removed; it no longer offers a digest, which no reference layer used.

@file-transfer/sink 0.1.1

Patch Changes

• 9c5bb91: Runs on Effect 4.1.0, with no change in behaviour. Deploys keep working: Alchemy 2.0.0-beta.84 is patched to Effect 4.1's crypto modules (patches/README.md), and every @effect package is pinned to the effect version.

@file-transfer/transport 1.2.1

Patch Changes

• 9c5bb91: Runs on Effect 4.1.0, with no change in behaviour. Deploys keep working: Alchemy 2.0.0-beta.84 is patched to Effect 4.1's crypto modules (patches/README.md), and every @effect package is pinned to the effect version.

@file-transfer/platform-cloudflare 0.6.0

Patch Changes

• 9c5bb91: Runs on Effect 4.1.0, with no change in behaviour. Deploys keep working: Alchemy 2.0.0-beta.84 is patched to Effect 4.1's crypto modules (patches/README.md), and every @effect package is pinned to the effect version.
• Updated dependencies [9c5bb91]
  • @file-transfer/service-quota@0.6.0
  • @file-transfer/service-telemetry@0.6.0
  • @file-transfer/transport@1.2.1

@file-transfer/service-abuse 0.6.0

Minor Changes

• 9c5bb91: Runs on Effect 4.1.0. The reference layers now require Effect's SecureRandom (from effect/crypto) instead of Crypto, which Effect 4.1.0 removed: provide SecureRandom.layerWebCrypto, or your runtime's SecureRandom, where you provided Crypto. Identifiers are still 16 secure random bytes in hex, and every guarantee and negative control is unchanged.

Patch Changes

• Updated dependencies [9c5bb91]
  • @file-transfer/conformance@0.3.0

@file-transfer/service-quota 0.6.0

Patch Changes

• 9c5bb91: Runs on Effect 4.1.0, with no change in behaviour. Deploys keep working: Alchemy 2.0.0-beta.84 is patched to Effect 4.1's crypto modules (patches/README.md), and every @effect package is pinned to the effect version.
• Updated dependencies [9c5bb91]
  • @file-transfer/conformance@0.3.0

@file-transfer/service-relay 0.6.0

Minor Changes

• 9c5bb91: Runs on Effect 4.1.0. The reference layers now require Effect's SecureRandom (from effect/crypto) instead of Crypto, which Effect 4.1.0 removed: provide SecureRandom.layerWebCrypto, or your runtime's SecureRandom, where you provided Crypto. Identifiers are still 16 secure random bytes in hex, and every guarantee and negative control is unchanged.

Patch Changes

• Updated dependencies [9c5bb91]
  • @file-transfer/conformance@0.3.0

@file-transfer/service-room 0.6.0

Minor Changes

• 9c5bb91: Runs on Effect 4.1.0. The reference layers now require Effect's SecureRandom (from effect/crypto) instead of Crypto, which Effect 4.1.0 removed: provide SecureRandom.layerWebCrypto, or your runtime's SecureRandom, where you provided Crypto. Identifiers are still 16 secure random bytes in hex, and every guarantee and negative control is unchanged.

Patch Changes

• Updated dependencies [9c5bb91]
  • @file-transfer/conformance@0.3.0

@file-transfer/service-telemetry 0.6.0

Patch Changes

• 9c5bb91: Runs on Effect 4.1.0, with no change in behaviour. Deploys keep working: Alchemy 2.0.0-beta.84 is patched to Effect 4.1's crypto modules (patches/README.md), and every @effect package is pinned to the effect version.
• Updated dependencies [9c5bb91]
  • @file-transfer/conformance@0.3.0

v0.5.6

@file-transfer/platform-cloudflare 0.5.6

Patch Changes

• 9550c6a: Deploys with Alchemy 2.0.0-beta.84 and its separate @alchemy.run/cloudflare provider package, with the Worker Preview asset settings fix carried over. CI deploys and destroys now stop, naming both versions, unless the account's shared Alchemy state store answers at the version the installed Alchemy expects, instead of letting --yes replace or downgrade the store (ADR 0025).
• @file-transfer/service-quota@0.5.6
  • @file-transfer/service-telemetry@0.5.6

v0.5.5

@file-transfer/conformance 0.2.1

Patch Changes

• cd619d4: The fileTransfer.testSupportFiles key leaves package.json; the module graph configuration (ox-dep-lint.config.ts) now names the suite's entry as test support. The package's code is unchanged.

@file-transfer/platform-cloudflare 0.5.5

Patch Changes

• @file-transfer/service-quota@0.5.5
  • @file-transfer/service-telemetry@0.5.5

@file-transfer/service-abuse 0.5.5

Patch Changes

• Updated dependencies [cd619d4]
  • @file-transfer/conformance@0.2.1

@file-transfer/service-quota 0.5.5

Patch Changes

• Updated dependencies [cd619d4]
  • @file-transfer/conformance@0.2.1

@file-transfer/service-relay 0.5.5

Patch Changes

• Updated dependencies [cd619d4]
  • @file-transfer/conformance@0.2.1

@file-transfer/service-room 0.5.5

Patch Changes

• Updated dependencies [cd619d4]
  • @file-transfer/conformance@0.2.1

@file-transfer/service-telemetry 0.5.5

Patch Changes

• Updated dependencies [cd619d4]
  • @file-transfer/conformance@0.2.1

v0.5.4

@file-transfer/web 0.5.4

Patch Changes

• 6b8ee0b: The browser leak checks now read Blob, File and FormData request bodies in every browser; in the app, only a comment in the address module changes. Nothing changes for people using the app.

@file-transfer/platform-cloudflare 0.5.4

Patch Changes

• @file-transfer/service-quota@0.5.4
  • @file-transfer/service-telemetry@0.5.4

v0.5.3

@file-transfer/platform-cloudflare 0.5.3

Patch Changes

• 4bd2eb0: Drops the unused workerd devDependency; wrangler brings its own. The Worker it builds is unchanged.

  Repository: knip checks dependency hygiene in bun run check, replacing the module graph check's unused-dependency rule.

• @file-transfer/service-quota@0.5.3

  • @file-transfer/service-telemetry@0.5.3

v0.5.2

@file-transfer/web 0.5.2

Patch Changes

• 28d84be: When a transfer stops right after its files were opened for writing, the recipient now retries removing the half-written folder for a moment instead of leaving it until the next visit (Chromium briefly refuses the removal). The browser suite also patches storage on prototypes, which WebKit keeps, so its storage checks no longer fail at random there.

@file-transfer/platform-cloudflare 0.5.2

Patch Changes

• @file-transfer/service-quota@0.5.2
  • @file-transfer/service-telemetry@0.5.2

v0.5.1

@file-transfer/web 0.5.1

Patch Changes

• e3d0bbf: The web app reads its own address in one module, and a lint rule stops any other code from reading the URL fragment that holds the link secret. Nothing changes for people using the app.

@file-transfer/platform-cloudflare 0.5.1

Patch Changes

• @file-transfer/service-quota@0.5.1
  • @file-transfer/service-telemetry@0.5.1

v0.5.0

@file-transfer/platform-cloudflare 0.5.0

Minor Changes

• 849482b: A room now remembers that a recipient completed and tells a sender that joins afterwards. A sender whose connection dropped just as the transfer finished, and that came back after the recipient had left, used to wait for the recipient forever; it now shows the transfer as delivered.

Patch Changes

• @file-transfer/service-quota@0.5.0
  • @file-transfer/service-telemetry@0.5.0

v0.4.5

@file-transfer/web 0.4.5

Patch Changes

• 5bf09fb: The web app exports its recipient life cycle table so docs/state-machines.md can be generated from it. Nothing changes for people using the app.

@file-transfer/platform-cloudflare 0.4.5

Patch Changes

• @file-transfer/service-quota@0.4.5
  • @file-transfer/service-telemetry@0.4.5

v0.4.4

@file-transfer/web 0.4.4

Patch Changes

• 733094a: When the browser cannot open storage for a transfer (a full disk, say), the recipient now gives back the storage lock and removes the files it had started, so they no longer linger until the tab closes.

@file-transfer/platform-cloudflare 0.4.4

Patch Changes

• @file-transfer/service-quota@0.4.4
  • @file-transfer/service-telemetry@0.4.4