chore: 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

@vertz/native-compiler@0.2.69

@vertz/native-compiler

0.2.67

Patch Changes

• #2725 56e7e2f Thanks @viniciusdacal! - fix(native-compiler): add repository/license/description fields to package.json

  npm publish with --provenance rejected the 0.2.66 publish with:

  npm error code E422
  Error verifying sigstore provenance bundle: Failed to validate
  repository information: package.json: "repository.url" is "",
  expected to match "https://github.com/vertz-dev/vertz" from provenance
  

  The @vertz/native-compiler package had never been published before, and its package.json was missing repository, license, and description. npm's provenance attestation requires the manifest's repository.url to match the source repo recorded in the provenance bundle. Added all three fields matching the pattern used by the other @vertz/* packages.

0.2.66

Patch Changes

• #2685 4cc0aa9 Thanks @viniciusdacal! - Fix false-positive batch import injection when async batch() appears as an object method definition

0.1.1

Patch Changes

• #2265 36b0f20 Thanks @viniciusdacal! - feat(ui): add form-level onChange with per-input debounce

  <form onChange={handler}> fires when any child input changes, receiving all current form values as a FormValues object. Per-input debounce={ms} delays the callback for text inputs while immediate controls (selects, checkboxes) flush instantly.

  Breaking: onChange on <form> now receives FormValues instead of a DOM Event. Use ref + addEventListener for the raw DOM event.

@vertz/cli@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/codegen@0.2.69
  • @vertz/compiler@0.2.69
  • @vertz/create-vertz-app@0.2.69
  • @vertz/db@0.2.69
  • @vertz/errors@0.2.69
  • @vertz/tui@0.2.69
  • @vertz/ui-server@0.2.69
  • @vertz/docs@0.1.3

@vertz/cloudflare@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/core@0.2.69
  • @vertz/ui-server@0.2.69

@vertz/codegen@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/compiler@0.2.69

@vertz/core@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/schema@0.2.69

create-vertz@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/create-vertz-app@0.2.69

@vertz/db@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/errors@0.2.69
  • @vertz/schema@0.2.69

@vertz/desktop@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/errors@0.2.69

@vertz/fetch@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/errors@0.2.69

@vertz/runtime@0.2.69

Patch Changes

• #2748 d220831 Thanks @viniciusdacal! - feat(vtz): add vitest-compatible mock APIs to @vertz/test

  Real-world test suites written against vitest often call getMockImplementation(),
  getMockName(), mockName(), and withImplementation() on mock functions. Our
  runtime exposed mock() / vi.fn() without those methods, so tests migrated
  from vitest hit TypeError: x.getMockImplementation is not a function (surfaced
  in @vertz/cli production-build: BuildOrchestrator analyze() call fails with undefined compiler #2731).

  This PR fills the gap. Added to every mock created by mock(), vi.fn(), and
  spyOn():

  • getMockImplementation() — returns the current default implementation, or
    undefined if none is set. Does not consider the once-queue (matches vitest).
  • getMockName() — returns the display name set via mockName(). Defaults
    to '' (empty string).
  • mockName(name) — sets the display name for diagnostics. Returns the mock
    for chaining. Cleared by mockReset(); preserved by mockClear().
  • withImplementation(fn, cb) — temporarily swaps the default implementation
    with fn, runs cb, then restores the original — awaiting cb if it returns
    a Promise. Returns cb's result. Restores cleanly on both sync and async
    exceptions. Does not disturb getMockImplementation() after return.

  Also added type declarations for all four methods to MockFunction in
  @vertz/test, and added Rust + TS test coverage (10 Rust tests, 15 TS tests).

  Not implemented (intentionally): mockThrow / mockThrowOnce (v4.1.0+ vitest,
  would add surface without strong use-case), mock.settledResults /
  mock.instances / mock.contexts / mock.invocationCallOrder (separate state
  that the runtime doesn't currently track — follow-up if demand materializes).

• #2740 48875ca Thanks @viniciusdacal! - fix(vtz): rewrite bare imports inside pre-bundled /@deps/ files

  The dev server's pre-bundle short-circuit previously served files from
  .vertz/deps/ verbatim. When a bundle still contained bare specifiers
  (e.g. an @vertz/theme-shadcn bundle with import { css } from "@vertz/ui"),
  the browser rejected it with Failed to resolve module specifier "@vertz/ui".
  The pre-bundle branch now runs the same import rewriter used by the direct
  node_modules/ serve path. Closes Dev server does not rewrite bare @vertz/ui imports inside @vertz/theme-shadcn #2730.

• #2742 7f7ff47 Thanks @viniciusdacal! - fix(vtz): vtz ci now loads ci.config.ts through vtz itself (no more bun/tsx dependency)

  vtz ci's config loader used to spawn an external JS runtime to evaluate
  ci.config.ts — preferring bun, falling back to node --import tsx. That
  made bun (or a tsx devDependency) a hard requirement for vtz ci, even
  though vtz is itself a TypeScript runtime. The fallback chain was
  discovered in vtz ci: load ci.config.ts via vtz runtime itself (not bun/tsx) #2739 while trying to drop bun from CI; the @vertz/ci
  package.json's exports field also doesn't satisfy strict-Node ESM, which
  tsx uses, so the fallback was fragile.

  This PR makes vtz self-host:

  • New hidden subcommand vtz __exec <file> [args...] — runs a
    single JS/TS file through the vtz runtime with process.argv populated.
    Not intended for end-user use; exists to support internal tooling like
    vtz ci.
  • find_runtime() in ci/config.rs now prefers the current vtz binary
    via std::env::current_exe() with __exec. bun/node+tsx stay as
    fallbacks for the edge case where current_exe() is unavailable.
  • process.exit(code) is now implemented (via a new op_process_exit
    op). It previously threw. The existing .pipe/_loader.mjs calls
    process.exit(0) at the end of its run, so this is necessary for the
    loader to terminate cleanly under vtz.

  After this lands, vtz ci has zero external-runtime dependencies — vtz
  alone is sufficient. Unblocks migrating CI from bun install to
  vtz install --frozen (tracked separately).

• #2747 7fea5d7 Thanks @viniciusdacal! - fix(vtz): semver resolver must not return versions that don't satisfy the range

  vtz install incorrectly resolved esbuild: ^0.27.3 to 0.25.12 when a stale
  lockfile entry existed, because the lockfile-reuse fast path trusted the pinned
  version without revalidating that it still satisfied the requested range. The
  companion graph_to_lockfile path also wrote root-dep entries by name-only,
  blindly accepting whichever hoisted version was present.

  Both paths now verify that the chosen version satisfies the declared range. A
  stale or out-of-range pin falls through to a fresh registry resolve instead of
  silently being reused. Closes vtz install resolver: ^0.27.3 incorrectly resolves to 0.25.12 #2738.

@vertz/schema@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/errors@0.2.69

@vertz/server@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/core@0.2.69
  • @vertz/db@0.2.69
  • @vertz/errors@0.2.69
  • @vertz/schema@0.2.69

@vertz/testing@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/core@0.2.69
  • @vertz/db@0.2.69
  • @vertz/server@0.2.69

@vertz/theme-shadcn@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/ui@0.2.69
  • @vertz/ui-primitives@0.2.69

@vertz/tui@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/ui@0.2.69

@vertz/ui@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/fetch@0.2.69

@vertz/ui-canvas@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/ui@0.2.69

@vertz/ui-primitives@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/ui@0.2.69

@vertz/ui-server@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/core@0.2.69
  • @vertz/ui@0.2.69

vertz@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/cli@0.2.69
  • @vertz/cloudflare@0.2.69
  • @vertz/db@0.2.69
  • @vertz/errors@0.2.69
  • @vertz/fetch@0.2.69
  • @vertz/schema@0.2.69
  • @vertz/server@0.2.69
  • @vertz/testing@0.2.69
  • @vertz/tui@0.2.69
  • @vertz/ui@0.2.69
  • @vertz/ui-primitives@0.2.69
  • @vertz/ui-server@0.2.69
  • @vertz/ui-auth@0.2.19

@vertz/compiler@0.2.69

@vertz/create-vertz-app@0.2.69

@vertz/errors@0.2.69

@vertz/icons@0.2.69

@vertz/test@0.2.69

@vertz-benchmarks/vertz-app@0.0.67

Patch Changes

• Updated dependencies []:
  • @vertz/theme-shadcn@0.2.69
  • @vertz/ui@0.2.69
  • @vertz/ui-server@0.2.69

@vertz-examples/task-manager@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/errors@0.2.69
  • @vertz/fetch@0.2.69
  • @vertz/icons@0.2.69
  • @vertz/schema@0.2.69
  • @vertz/theme-shadcn@0.2.69
  • @vertz/ui@0.2.69
  • @vertz/ui-primitives@0.2.69
  • @vertz/ui-server@0.2.69

@vertz/cli-runtime@0.2.69

Patch Changes

• Updated dependencies []:
  • @vertz/fetch@0.2.69

@vertz/native-compiler-darwin-arm64@0.2.69

@vertz/native-compiler-darwin-arm64

0.2.65

@vertz/native-compiler-darwin-x64@0.2.69

@vertz/native-compiler-darwin-x64

0.2.65

@vertz/native-compiler-linux-arm64@0.2.69

@vertz/native-compiler-linux-arm64

0.2.65

@vertz/native-compiler-linux-x64@0.2.69

@vertz/native-compiler-linux-x64

0.2.65

@vertz/runtime-darwin-arm64@0.2.69

@vertz/runtime-darwin-x64@0.2.69

@vertz/runtime-linux-arm64@0.2.69

@vertz/runtime-linux-x64@0.2.69