chore: update versions

[vland-bot]

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

@rrlab/biome-plugin@1.2.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

Patch Changes

• #276 db8398e Thanks @rqbazan! - rr plugins add biome scaffolds a biome.json that passes rr jsc: in Biome's own format, with $schema pointing at the installed Biome's schema (./node_modules/@biomejs/biome/configuration_schema.json). It used to fail the format check, and its pinned 2.4.4 schema URL drew a version-mismatch note against the ^2.0.0 it installs.
• Updated dependencies [3e70f16]:
  • @variablelab/clibuddy@0.8.0

@rrlab/cli@1.4.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

Patch Changes

• #276 db8398e Thanks @rqbazan! - rr plugins add writes run-run.config.mts with its imports together, in Biome's order, and with a final newline, so rr jsc and oxfmt pass on it. Each new import used to go first, so they ended up in reverse order of adding, and the file had no final newline.

• #276 db8398e Thanks @rqbazan! - rr plugins add without a terminal (an agent, a script, CI) takes the defaults, as with --yes, instead of prompting: it used to wait on the prompt, or exit 13 with the plugin half installed. rr plugins remove without a terminal and without --yes stops with an error that asks for --yes, since it deletes files and dependencies. Both count as a terminal only when stdin and stdout are TTYs.

• #267 bb67697 Thanks @rqbazan! - List @rrlab/vitest-plugin in the README's table of official plugins.

• Updated dependencies [3e70f16]:

  • @variablelab/clibuddy@0.8.0
  • @variablelab/loggy@0.3.0

@rrlab/oxc-plugin@1.2.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

Patch Changes

• #276 db8398e Thanks @rqbazan! - rr lint, rr jsc and rr check run oxlint without --check, a flag it doesn't have, so they failed wherever oxc provides lint. rr format --fix runs oxfmt --write, since oxfmt has no --fix either.

• #269 cdb7137 Thanks @rqbazan! - rr plugins add oxc installs oxlint-tsgolint@^7.0.2004, and the peer range now starts at >=0.24.0. oxlint-tsgolint@0.23.0 bundles a typescript-go whose macOS realpath can fail under concurrency, so rr tsc reports random TS2307 on installed modules (microsoft/typescript-go#4060). The new install range also matches the >=7.0.2003 peer that current oxlint requires.

  rr plugins add oxc installs oxfmt@^0.73.0, and the peer range now starts at >=0.67.0. oxfmt up to 0.66.0 pins tinypool@2.1.0, which has two critical advisories (GHSA-5gmw-xhrv-c9v3, GHSA-85c8-ppgw-ccpr).

  Both new peer floors exist only to warn about broken or vulnerable versions: if a project is still on oxlint-tsgolint@0.23.0 or oxfmt below 0.67.0, pnpm warns about it when @rrlab/oxc-plugin is updated.

• Updated dependencies [3e70f16]:

  • @variablelab/clibuddy@0.8.0

@rrlab/ts-plugin@1.2.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

Patch Changes

• #276 db8398e Thanks @rqbazan! - rr plugins add ts defaults to the React preset when the package depends on react (in dependencies, devDependencies or peerDependencies), and to the Node.js app preset otherwise. That's what --yes and a run without a terminal pick, and where the prompt starts. Before, they always picked the Node.js preset, which can't type-check a React app.
• Updated dependencies [3e70f16]:
  • @variablelab/clibuddy@0.8.0

@rrlab/tsdown-config@0.2.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

@rrlab/tsdown-plugin@1.2.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

Patch Changes

• Updated dependencies [3e70f16]:
  • @variablelab/clibuddy@0.8.0

@rrlab/vitest-plugin@0.2.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

Patch Changes

• Updated dependencies [3e70f16]:
  • @variablelab/clibuddy@0.8.0

@variablelab/clibuddy@0.8.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

@variablelab/loggy@0.3.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

@variablelab/vland@0.4.0

Minor Changes

• #272 3e70f16 Thanks @rqbazan! - Require Node.js 22.18.0 or newer (engines.node was >=20.0.0).

  rr loads run-run.config.{ts,mts} with Node's native type stripping, which is on by default only from Node 22.18.0. Without it rr stops with ERR_UNKNOWN_FILE_EXTENSION as soon as it reads the config: Node 20 has no type stripping at all, and 22.6 to 22.17 only behind --experimental-strip-types. So the old >=20.0.0 was never true for rr. CI now tests 22.18.0 and Node 24.

• #271 03b1373 Thanks @rqbazan! - Projects from vland init follow Variable Lab's current standard:

  • mise pins Node.js 24 and pnpm 10.30.3, with a mise.lock that needs mise 2026.9.16 or later. .node-version is gone.
  • engines.node is >=22.18.0, the first Node.js that strips types without a flag, which rr needs to load run-run.config.mts.
  • CI sets up with jdx/mise-action and runs rr check. Every action is pinned by SHA, checkout keeps no credentials, and a new workflow-audit.yml runs zizmor. The monorepo gets a CI workflow, which tests and builds only what a PR affects.
  • Changesets 3, with commit: true and format: false. The library's release workflow runs changesets/action v2 as vland-bot, so its repo needs the VLAND_BOT_CLIENT_ID variable and the VLAND_BOT_PRIVATE_KEY secret.
  • The changelog links to withvariablelab/<name> for a public library and variableland/<name> otherwise, not <name>/<name>.
  • pnpm waits a day before installing a new release, and runs lefthook's postinstall on every install, so the git hooks get installed.
  • @rrlab/cli is ^1.3.4. The ^0.1.0 the templates asked for doesn't exist, so pnpm install failed.
  • The backend's pnpm dev runs node --watch and loads .env, without tsx.
  • The library's published exports point at what rr pack builds (index.mjs and index.d.mts), and its README at the scoped package name.
  • Every generated file passes both oxfmt and Biome (with @rrlab/biome-config), including package.json key order with private after version, so rr check starts green with either. The READMEs explain how to pair the oxc plugin with ts.

Patch Changes

• #271 03b1373 Thanks @rqbazan! - vland init runs git init before installing dependencies, so the git hooks a dependency sets up on install (the templates' lefthook ones) land in the new repo. Before, the install ran first, found no repo and skipped them, so a generated project's lefthook.yml never ran until a manual lefthook install. The first commit skips those hooks, because it's the template as generated.

• #271 03b1373 Thanks @rqbazan! - vland init makes the first commit as your own git identity, the user.name and user.email git resolves for the new repo. Before, it always committed as vland <noreply@variable.land>, so the commit wasn't yours and a signed one showed as "Unverified" on GitHub. It still falls back to vland and noreply@variable.land for whichever of the two git has no value for.

• Updated dependencies [3e70f16]:

  • @variablelab/clibuddy@0.8.0
  • @variablelab/loggy@0.3.0