Version Packages

[github-actions]

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.

Releases

@peerbit/shared-fs-cli@0.13.17

Patch Changes

• 475d60f: Compact emitted JavaScript whitespace while preserving declarations, source maps, module surfaces, and the CLI shebang.
• Updated dependencies [475d60f]
• Updated dependencies [dd79d42]
• Updated dependencies [a7eb210]
• Updated dependencies [630ac12]
• Updated dependencies [e30a8d4]
• Updated dependencies [fde5d3f]
  • @peerbit/shared-fs@0.13.16

@peerbit/shared-fs@0.13.16

Patch Changes

• 475d60f: Compact emitted JavaScript whitespace while preserving declarations, source maps, module surfaces, and the CLI shebang.
• dd79d42: Trim implementation comments from the published JavaScript and source maps while preserving API documentation in the declaration files.
• a7eb210: Release watcher and changeset lifecycle state promptly on close, detach abort
  listeners, and cancel superseded retry timers.
• 630ac12: Add experimental, generation-isolated Merkle v1 block and content-root codecs,
  codec-local structural verification, bitmap helpers, and cross-runtime golden
  vectors as the first bounded random-write storage slice.
• e30a8d4: Define the generation-isolated Merkle v1 file-version wire model and its
  strict, derived reverse-index projection, bounded canonical decode APIs, and
  cross-runtime golden vectors.
• fde5d3f: Add an opt-in, generation-isolated Merkle v1 exact-range read session with
  fail-closed block verification, authenticated sparse holes, bounded verified
  LRU caches, cancellation-safe concurrent fetch coalescing, and structural work
  counters.

[peerbit-org]

Holding this release without rerunning the failed job. The first Windows portable run reached the pre-existing persistent-multi-writer private receipt-session readiness probe and failed at line 100 after the same quiet-reconnect race already traced to the old Peerbit cohort; the package-build and all three tarball-install checks passed. PR #300 replaces this probe with the public exact-entry readiness waiter, removes the test retry and CI timeout inflation, and will pin the upstream #1426 release cohort once published. Let the changesets PR update from that merge, then require a fresh first-attempt three-OS pass before release.

[peerbit-org]

Release remains held; no rerun or auto-merge.\n\nFresh exact-master evidence at bcb2dbb:\n- Shared FS CI attempt 1 failed on Windows: the durable naming-conflict/tombstone disposal case exhausted its built-in retry while waiting for a persisted remote replica, and the real-partition directory merge plus cleanup each timed out at 120s.\n- macOS persistent-multi-writer passed only with retry x1.\n- Ubuntu snapshot-readable-before-log passed only with retry x1.\n- Package-install and published-npm smoke passed on all three OSes, but the smoke tested the unchanged published versions, not this release candidate.\n\nRun: https://github.com/dao-xyz/peerbit-examples/actions/runs/33939518592\n\nThe release workflow only updated this PR to 9444913. npm remains @peerbit/shared-fs 0.13.15 and @peerbit/shared-fs-cli 0.13.16. Do not merge or publish until the upstream receipt/session liveness fix is released, downstream is rebased, and a fresh exact head passes Ubuntu, macOS, and Windows with zero built-in retries.

[peerbit-org]

Release hold remains in force after the #336 merge.

Exact master e30a8d406da2f328fbff20a04d81bdc66c6e468c, first workflow attempt 33941567486, failed in macOS portable CI. persistent-multi-writer exhausted its configured retry x1 after 312.6 seconds:

• one execution observed only two of the three expected conflict heads;
• the other failed with Timeout waiting for replicator 2Ir0IbV3m4dHYnNU0kjXBoA45mTIbgHbRIBPh1jdlUs= from @peerbit/shared-log.

Ubuntu and Windows passed. No workflow rerun was requested. The exact #336 PR head had passed the same portable matrix first-attempt and retry-free immediately before merge, while #336 itself changes only the isolated Merkle wire model. This is further evidence of the intermittent upstream receipt/session/replicator liveness blocker, not feature coupling.

Please do not merge this release PR until the upstream fix is released, downstream #300 is refreshed, and fresh Ubuntu/macOS/Windows persisted-disposal, process-crash, and persistent-multiwriter coverage passes with zero retry markers.

[peerbit-org]

Release remains held at regenerated head 3666f82ca4bc7db49b346f10b2c260c077756b6c; auto-merge is disabled. The release workflow did not publish.

The build-only #338 head and post-merge master 403942374a2be0b6c16cfd5467c748cf4900e6ad both passed Ubuntu/macOS/Windows without a retry. That does not clear the durability gate: minutes earlier, isolated non-runtime #329 on the same unchanged runtime cohort hard-failed Ubuntu durable disposal and macOS persistent multiwriter after retry x1 each. The observed sequence was clean #336 PR -> failed #336 master -> failed #337 PR -> failed #329 PR -> clean #338 PR/master, without an upstream fix. That is direct evidence of intermittent receipt/session/replicator liveness, not resolution.

Do not merge or publish this release until upstream provides a coherent fix cohort, downstream refreshes #300, and a fresh naturally triggered Ubuntu/macOS/Windows disposal/process-crash/persistent-multiwriter run passes first-attempt. Do not use a blind rerun or timeout inflation as acceptance evidence.