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.70

@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.70

Patch Changes

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

@vertz/cloudflare@0.2.70

Patch Changes

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

@vertz/codegen@0.2.70

Patch Changes

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

@vertz/core@0.2.70

Patch Changes

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

create-vertz@0.2.70

Patch Changes

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

@vertz/db@0.2.70

Patch Changes

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

@vertz/desktop@0.2.70

Patch Changes

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

@vertz/fetch@0.2.70

Patch Changes

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

@vertz/runtime@0.2.70

Patch Changes

• #2750 f7f05f4 Thanks @viniciusdacal! - fix(vtz): vi.mock propagates through transitive imports (resolves @vertz/cli production-build: BuildOrchestrator analyze() call fails with undefined compiler #2731)

  When a test file did vi.mock('m', () => ({ fn: ... })) and then drove
  production code that itself called await import('m'), the production code
  got the REAL frozen module namespace — spyOn mutations from the test
  didn't propagate. Static imports of mocked modules were fine; only the
  dynamic-import path leaked the real module.

  Three concrete fixes, all needed together:

  1. Wrap dynamic import() in non-test files when the test runner is
     active. The mock-hoisting compiler pass already wrapped dynamic imports
     in test files via __vertz_unwrap_module so frozen ES module namespaces
     become mutable; this PR extends the same wrap to every module compiled
     while spy_exports is on (i.e., the entire dependency graph during a
     vtz test run). Without it, cli.ts → await import('@vertz/compiler')
     bypassed the spy installed by cli.test.ts.

  2. Restore initial impl on mockRestore() for mock(impl). vtz had
     mockRestore = mockReset for plain mocks, which dropped the
     factory-supplied implementation to null. This broke the common pattern
     vi.mock('m', () => ({ fn: mock(() => obj) })) + vi.restoreAllMocks()
     in afterEach — the first cleanup nuked fn's impl for every following
     test. Now matches vitest: "for vi.fn(impl), mockRestore reverts to
     impl". mockReset still clears, as documented.

  3. Union synthetic-polyfill exports into the mock proxy. When mocking a
     bare specifier with a vtz polyfill (esbuild, node:*), the proxy module
     only exported names declared on disk + names returned by the factory.
     CJS modules like esbuild expose nothing the regex-based extractor can see,
     so transitive imports of unmocked exports (import { transformSync } from 'esbuild' in @vertz/ui-server/bun-plugin) failed at import time with
     "module does not provide an export named transformSync" — even when the
     call path never reached transformSync() at runtime. The proxy now
     advertises the full polyfill surface (values are undefined unless the
     factory supplied them), preserving spec-compliant import resolution.

     Unskipped 3 test blocks that had been parked on this:
     packages/cli/src/__tests__/cli.test.ts (codegen command action),
     packages/cli/src/production-build/__tests__/orchestrator.test.ts
     (BuildOrchestrator), and
     packages/cli/src/production-build/__tests__/ui-build-pipeline.test.ts
     (buildUI). 133/134 tests pass; one buildUI assertion that expects an actual
     Brotli .br sidecar remains skipped because vtz's node:zlib polyfill is a
     passthrough — tracked separately as a runtime polyfill gap, not a mock issue.

• #2749 d5d0a76 Thanks @viniciusdacal! - fix(vtz): node:http.createServer() + listen() + fetch() + close() no longer hangs under the vtz test runner (resolves Test runtime gap: node:http server tests in @vertz/ui-server hang under vtz #2718, happy-dom GlobalRegistrator state doesn't persist from preload into test body in @vertz/docs #2720)

  The synthetic node:http module exposed createServer() whose listen()
  implementation treated globalThis.__vtz_http.serve() as asynchronous —
  but serve() is a synchronous op that returns the server object directly.
  The resulting .then() on a non-thenable threw a TypeError that was
  swallowed by the new Promise((resolve) => server.listen(0, resolve))
  idiom, so the listen callback never fired and tests hung at the 120 s
  watchdog. The same bug existed in the CJS require('http') shim.

  Fixing the shim surfaced three secondary defects in the underlying op
  layer:

  • close() aborted the axum task immediately, cancelling in-flight
    response futures mid-reply so clients hung on fetch(). Replaced the
    abort-handle teardown with axum's with_graceful_shutdown(...) signal
    so existing connections drain before the task exits.
  • op_http_serve_respond keyed the pending oneshot map per server,
    so replying after close (which removed the ServerInstance from state)
    silently dropped the response. Moved the pending-responses map onto
    HttpServeState and keyed it globally by request_id so in-flight
    replies work across close.
  • op_http_serve_accept and op_http_serve_respond returned an
    "Unknown server id" error when the JS accept loop re-polled after
    close(), poisoning the event loop and failing unrelated tests. Both
    ops now treat a missing server as a soft null/no-op.

  The JS createServer() shim also gained proper Node-compatible semantics:
  listen(cb) invokes the callback via queueMicrotask; close(cb)
  defers the callback until all in-flight requests finish; new connections
  received after close() receive a 503 instead of entering the user
  handler.

  Previously-quarantined packages/ui-server/src/__tests__/node-handler.local.ts
  and packages/docs/src/__tests__/docs-cli-actions.local.ts are restored
  to .test.ts and now run under vtz test. The test:integration npm
  scripts that fell back to bun for these files are removed.

@vertz/schema@0.2.70

Patch Changes

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

@vertz/server@0.2.70

Patch Changes

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

@vertz/testing@0.2.70

Patch Changes

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

@vertz/theme-shadcn@0.2.70

Patch Changes

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

@vertz/tui@0.2.70

Patch Changes

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

@vertz/ui@0.2.70

Patch Changes

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

@vertz/ui-canvas@0.2.70

Patch Changes

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

@vertz/ui-primitives@0.2.70

Patch Changes

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

@vertz/ui-server@0.2.70

Patch Changes

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

vertz@0.2.70

Patch Changes

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

@vertz/compiler@0.2.70

@vertz/create-vertz-app@0.2.70

@vertz/errors@0.2.70

@vertz/icons@0.2.70

@vertz/test@0.2.70

@vertz-benchmarks/vertz-app@0.0.68

Patch Changes

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

@vertz-examples/task-manager@0.2.70

Patch Changes

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

@vertz/cli-runtime@0.2.70

Patch Changes

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

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

@vertz/native-compiler-darwin-arm64

0.2.65

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

@vertz/native-compiler-darwin-x64

0.2.65

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

@vertz/native-compiler-linux-arm64

0.2.65

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

@vertz/native-compiler-linux-x64

0.2.65

@vertz/runtime-darwin-arm64@0.2.70

@vertz/runtime-darwin-x64@0.2.70

@vertz/runtime-linux-arm64@0.2.70

@vertz/runtime-linux-x64@0.2.70