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/cli@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/data@0.0.2
  • @xnetjs/sync@0.0.2

@xnetjs/core@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.

@xnetjs/crypto@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/core@0.0.2

@xnetjs/data@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/identity@0.0.2
  • @xnetjs/storage@0.0.2
  • @xnetjs/crypto@0.0.2
  • @xnetjs/sqlite@0.0.2
  • @xnetjs/core@0.0.2
  • @xnetjs/sync@0.0.2

@xnetjs/data-bridge@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/core@0.0.2
  • @xnetjs/data@0.0.2

@xnetjs/history@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/core@0.0.2
  • @xnetjs/data@0.0.2
  • @xnetjs/sync@0.0.2

@xnetjs/identity@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/crypto@0.0.2
  • @xnetjs/core@0.0.2

@xnetjs/plugins@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/core@0.0.2
  • @xnetjs/data@0.0.2

@xnetjs/react@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/data-bridge@0.0.2
  • @xnetjs/identity@0.0.2
  • @xnetjs/history@0.0.2
  • @xnetjs/plugins@0.0.2
  • @xnetjs/crypto@0.0.2
  • @xnetjs/core@0.0.2
  • @xnetjs/data@0.0.2

@xnetjs/sqlite@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.

@xnetjs/storage@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/crypto@0.0.2
  • @xnetjs/sqlite@0.0.2
  • @xnetjs/core@0.0.2

@xnetjs/sync@0.0.2

Patch Changes

• cd2a564: Set up automated npm publishing via Changesets and GitHub Actions trusted publishing, and standardize package publish metadata (public access, provenance, files, and dist entrypoints) for the initial @xnetjs release set including the React package chain.
• Updated dependencies [cd2a564]
  • @xnetjs/identity@0.0.2
  • @xnetjs/crypto@0.0.2
  • @xnetjs/core@0.0.2

[greptile-apps]

Greptile Summary

This is a standard automated release PR generated by the Changesets release GitHub Action, bumping all 12 @xnetjs/* packages from 0.0.1 to 0.0.2 as a coordinated patch release. No source code changes are included — only version metadata and auto-generated changelogs.

• All 12 packages receive a consistent 0.0.1 → 0.0.2 patch version bump matching the consumed changeset (cd2a564).
• CHANGELOG.md files are newly created for every package, correctly documenting the patch change and the relevant updated dependency chains.
• The originating changeset file .changeset/late-beers-read.md is correctly deleted after being consumed.
• All internal cross-package dependencies continue to use workspace:* — this is correct for a pnpm Changesets monorepo; the package manager replaces the protocol with resolved versions at publish time.
• The dependency graph reflected in each CHANGELOG.md matches the package.json dependency declarations (e.g., @xnetjs/data depending on @xnetjs/identity, @xnetjs/storage, @xnetjs/crypto, @xnetjs/sqlite, @xnetjs/core, and @xnetjs/sync).

Confidence Score: 5/5

• This PR is safe to merge — it is a fully automated, metadata-only release bump with no logic changes.
• All changes are auto-generated by the Changesets release action (version bumps + CHANGELOG creation). No source code is modified, the version increments are consistent across all packages, internal workspace dependencies are correctly preserved, and the consumed changeset file is properly cleaned up. There are no logic, security, or correctness concerns.
• No files require special attention.

Important Files Changed

Filename	Overview
packages/cli/package.json	Version bumped from 0.0.1 to 0.0.2; internal deps remain workspace:* (correct for pnpm Changesets monorepo).
packages/core/package.json	Version bumped from 0.0.1 to 0.0.2; leaf package with no internal deps — straightforward bump.
packages/crypto/package.json	Version bumped from 0.0.1 to 0.0.2; @xnetjs/core dep correctly stays workspace:*.
packages/data/package.json	Version bumped from 0.0.1 to 0.0.2; all six internal @xnetjs dependencies remain workspace:* as expected.
packages/react/package.json	Version bumped from 0.0.1 to 0.0.2; all seven internal @xnetjs dependencies remain workspace:* as expected.
packages/data-bridge/package.json	Version bumped from 0.0.1 to 0.0.2; internal deps remain workspace:*.
packages/history/package.json	Version bumped from 0.0.1 to 0.0.2; internal deps remain workspace:*.
packages/identity/package.json	Version bumped from 0.0.1 to 0.0.2; internal deps remain workspace:*.
packages/plugins/package.json	Version bumped from 0.0.1 to 0.0.2; internal deps remain workspace:*.
packages/sqlite/package.json	Version bumped from 0.0.1 to 0.0.2; standalone leaf package with no internal deps.
packages/storage/package.json	Version bumped from 0.0.1 to 0.0.2; internal deps remain workspace:*.
packages/sync/package.json	Version bumped from 0.0.1 to 0.0.2; internal deps remain workspace:*.
.changeset/late-beers-read.md	Changeset entry correctly deleted after being consumed by the Changesets release action.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    core["@xnetjs/core\nv0.0.2"]
    sqlite["@xnetjs/sqlite\nv0.0.2"]
    crypto["@xnetjs/crypto\nv0.0.2"]
    identity["@xnetjs/identity\nv0.0.2"]
    storage["@xnetjs/storage\nv0.0.2"]
    sync["@xnetjs/sync\nv0.0.2"]
    data["@xnetjs/data\nv0.0.2"]
    databridge["@xnetjs/data-bridge\nv0.0.2"]
    history["@xnetjs/history\nv0.0.2"]
    plugins["@xnetjs/plugins\nv0.0.2"]
    react["@xnetjs/react\nv0.0.2"]
    cli["@xnetjs/cli\nv0.0.2"]

    core --> crypto
    core --> identity
    core --> storage
    core --> sync
    core --> data
    core --> databridge

    sqlite --> storage

    crypto --> identity
    crypto --> storage
    crypto --> sync

    identity --> sync
    identity --> data

    storage --> data

    sync --> data
    sync --> cli

    sqlite --> data

    data --> databridge
    data --> history
    data --> plugins
    data --> react
    data --> cli

    databridge --> react

    identity --> react
    history --> react
    plugins --> react
    crypto --> react
    core --> react

Loading

_{Last reviewed commit: b9df6e0}