chore(release): 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 main, this PR will be updated.

Releases

@xnetjs/abuse@0.1.2

Patch Changes

• Updated dependencies []:
  • @xnetjs/identity@0.1.2
  • @xnetjs/crypto@0.1.2

@xnetjs/cli@0.0.6

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/sqlite@0.1.2
  • @xnetjs/plugins@0.1.2
  • @xnetjs/runtime@0.1.2
  • @xnetjs/sync@0.1.2
  • @xnetjs/identity@0.1.2
  • @xnetjs/crypto@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/crypto@0.1.2

Patch Changes

• Updated dependencies []:
  • @xnetjs/core@0.1.2

@xnetjs/data@0.1.2

Patch Changes

• #392 1a045b3 Thanks @crs48! - SQL property upserts now enforce the full LWW ordering triple (Lamport →
  wallTime → author code-units), matching the in-memory shouldReplace
  comparator. The previous lamport-only guard let arrival order decide
  same-Lamport concurrent edits, so two replicas that received the same
  conflicting changes in different orders could permanently disagree on the
  materialized value. Applies to the per-change upsert, the batched
  applyNodeBatch path, and the native web/electron batch adapters.

• #392 1a045b3 Thanks @crs48! - Changes re-read from the local SQLite change log now pass hash verification.
  The changes table never persisted id, type, protocolVersion, or the
  batch fields, yet all of them are part of the signed content hash — so the
  reload-resync push (getChangesSince → hub) was structurally rejected as
  INVALID_HASH, tripped the outbound circuit breaker, and stranded edits made
  offline before an app restart. New rows persist those fields in an envelope
  inside the payload BLOB (no schema migration needed); legacy rows keep the
  old fallback behaviour.

• Updated dependencies [1a045b3]:

  • @xnetjs/sqlite@0.1.2
  • @xnetjs/storage@0.1.2
  • @xnetjs/sync@0.1.2
  • @xnetjs/identity@0.1.2
  • @xnetjs/crypto@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/data-bridge@0.1.2

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/sqlite@0.1.2
  • @xnetjs/sync@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/history@0.1.2

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/sync@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/identity@0.1.2

Patch Changes

• Updated dependencies []:
  • @xnetjs/crypto@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/plugins@0.1.2

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/abuse@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/react@0.1.2

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/data-bridge@0.1.2
  • @xnetjs/history@0.1.2
  • @xnetjs/plugins@0.1.2
  • @xnetjs/runtime@0.1.2
  • @xnetjs/sync@0.1.2
  • @xnetjs/identity@0.1.2
  • @xnetjs/crypto@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/runtime@0.1.2

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/data-bridge@0.1.2
  • @xnetjs/history@0.1.2
  • @xnetjs/plugins@0.1.2
  • @xnetjs/storage@0.1.2
  • @xnetjs/sync@0.1.2
  • @xnetjs/identity@0.1.2
  • @xnetjs/crypto@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/sqlite@0.1.2

Patch Changes

• #392 1a045b3 Thanks @crs48! - SQL property upserts now enforce the full LWW ordering triple (Lamport →
  wallTime → author code-units), matching the in-memory shouldReplace
  comparator. The previous lamport-only guard let arrival order decide
  same-Lamport concurrent edits, so two replicas that received the same
  conflicting changes in different orders could permanently disagree on the
  materialized value. Applies to the per-change upsert, the batched
  applyNodeBatch path, and the native web/electron batch adapters.

@xnetjs/storage@0.1.2

Patch Changes

• Updated dependencies [1a045b3]:
  • @xnetjs/sqlite@0.1.2
  • @xnetjs/crypto@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/sync@0.1.2

Patch Changes

• Updated dependencies []:
  • @xnetjs/identity@0.1.2
  • @xnetjs/crypto@0.1.2
  • @xnetjs/core@0.1.2

@xnetjs/core@0.1.2

xnet-cloud@0.0.4

Patch Changes

• Updated dependencies []:
  • @xnetjs/cloud@0.0.1
  • @xnetjs/crypto@0.1.2

@xnetjs/brain@0.0.5

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/vectors@0.0.1

@xnetjs/comms@0.0.5

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/crypto@0.1.2

@xnetjs/dashboard@0.0.5

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/plugins@0.1.2
  • @xnetjs/react@0.1.2
  • @xnetjs/social@0.0.5

@xnetjs/labs@0.0.5

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/plugins@0.1.2

@xnetjs/licenses@0.0.5

Patch Changes

• Updated dependencies []:
  • @xnetjs/crypto@0.1.2

@xnetjs/maps@0.0.5

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2

@xnetjs/server@0.0.4

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/data-bridge@0.1.2
  • @xnetjs/identity@0.1.2
  • @xnetjs/crypto@0.1.2

@xnetjs/social@0.0.5

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2
  • @xnetjs/crypto@0.1.2

@xnetjs/unreal@0.0.5

Patch Changes

• Updated dependencies [1a045b3, 1a045b3]:
  • @xnetjs/data@0.1.2

xnet-desktop@0.1.2

Desktop shell release riding the @xnetjs/core 0.1.2 train. Desktop-specific changes are not tracked here; see the core packages' changelogs for what shipped.

[github-actions]

Preview removed for PR #393.