Version Packages

[patchcrow]

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 main, this PR will be updated.

Releases

@inkandswitch/patchwork-bootloader@0.8.1

Patch Changes

• d3b5e82: Move to @automerge/automerge-repo-keyhive 0.6.0-alpha.1 and @keyhive/keyhive 0.3.0-alpha.1. These are exact pins resolved from the workspace catalog at publish time, so both packages move together to keep a single copy of automerge-repo in the consumer's tree.

  The new keyhive can't read state written by 0.5, so the bootloader now stores keyhive state in a versioned database (<prefix>-keyhive-0.6) and leaves the old <prefix>-keyhive database untouched. Existing installs start with fresh keyhive state on upgrade.

  The bootloader also resolves the keyhive wasm asset via the package's @keyhive/keyhive/wasm export instead of the old keyhive_wasm.wasm file path.

@inkandswitch/patchwork@0.8.4

Patch Changes

• d3b5e82: Move to @automerge/automerge-repo-keyhive 0.6.0-alpha.1 and @keyhive/keyhive 0.3.0-alpha.1. These are exact pins resolved from the workspace catalog at publish time, so both packages move together to keep a single copy of automerge-repo in the consumer's tree.

  The new keyhive can't read state written by 0.5, so the bootloader now stores keyhive state in a versioned database (<prefix>-keyhive-0.6) and leaves the old <prefix>-keyhive database untouched. Existing installs start with fresh keyhive state on upgrade.

  The bootloader also resolves the keyhive wasm asset via the package's @keyhive/keyhive/wasm export instead of the old keyhive_wasm.wasm file path.

• Updated dependencies [d3b5e82]

  • @inkandswitch/patchwork-bootloader@0.8.1

[github-actions]

🪡 Patchwork

Torn down.