Skip to content

release: v1.7.0 - #3471

Merged
fengmk2 merged 3 commits into
mainfrom
release/v1.7.0
Nov 17, 2026
Merged

fengmk2 merged 3 commits into
mainfrom
release/v1.7.0

Conversation

@voidzero-guard

@voidzero-guard voidzero-guard Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Vite+ 1.7.0 runs type-aware linting and type checking on tsrs, a Rust port of the TypeScript 7 compiler, gives @voidzero-dev/vite-plus-core a version that encodes the bundled Vite version (8.3.8000 for Vite 8.3.8) so compatible vite plugins pass peer checks, and adds vp check --fix-dangerously.

Features

  • Type-aware linting and type checking in vp lint and vp check use tsrs, a Rust port of the TypeScript 7 compiler, through its tsrs-lint executable. Commands and configuration stay the same, and tsrs installs with vite-plus. In the benchmark on two projects, with the same CLI and Oxlint, type-aware vp lint and a full vp check took 18% to 53% less time with tsrs than with the previous backend, and used about half the peak memory (docs) (#3352), by @fengmk2:
    • tsrs targets TypeScript 7.1.0-beta, so type-check diagnostics can change.
    • With trustPolicy: no-downgrade in pnpm-workspace.yaml, pnpm rejects the bundled tsrs release (upstream issue). vp migrate adds tsrs@7.1.0-beta.tsrs2 to trustPolicyExclude, so run it if this policy blocks the upgrade.
  • @voidzero-dev/vite-plus-core has a version that encodes the bundled Vite version: 8.3.8000 for Vite 8.3.8 in this release. Projects alias vite to this package, so plugins whose vite peer range includes the bundled Vite, such as @vitejs/plugin-react with ^8.0.0, now pass peer checks. npm no longer prints ERESOLVE overriding peer dependency warnings, and npm and Bun projects that declare only vite-plus install one copy of Vite for Vitest and Vite+, about 20 MiB less in node_modules on macOS arm64 (#3317), by @fengmk2:
    • On pnpm 10.2.0 and later, vp migrate removes the broad vite rule from peerDependencyRules. A plugin whose vite peer range excludes the bundled Vite then reports a peer warning, and with strictPeerDependencies the install fails. Update that plugin, or allow its range for that plugin only (migration rules).
    • vite-plus and the core no longer share a version number. If you update them by hand or with a dependency bot, read the alias with npm view vite-plus@1.7.0 dependencies.vite, or run vp migrate to update both (docs).
  • vp check --fix-dangerously formats files and applies all lint fixes, including dangerous fixes and suggestions. It does not need --fix, and it works with --no-fmt and --continue-on-error. Review the changes before you commit them, because dangerous fixes can change program behavior (docs) (#3413), by @chbaefront.
  • vp create with a third-party create-xxx template asks about agent instructions, editor configs, Git, and commit hooks after the template's own CLI finishes, and checks what that CLI generated: it offers to append to an existing agent file, merges existing editor configs, and asks about Git only when the template did not create a repository. When the generated standalone project already depends on vite-plus, vp create keeps the template's choices, such as ESLint or its vite-plus version, and skips the migration. Set VP_FORCE_MIGRATE=1 to run it (#3424, #3435), by @liangmiQwQ.
  • Upgrade the bundled Vite, Rolldown, oxc-node, Oxlint, Oxfmt, and lint-staged (#3436, #3440, #3452, #3463, #3470), by @voidzero-guard[bot] and @fengmk2:
    • vite@8.3.7 to vite@8.3.8. Vite rejects CSS entry points when build.cssCodeSplit is false, imports Sass once instead of once per file, and no longer opens a console window for yarn config get on Windows.
    • rolldown@1.2.18 to rolldown@1.2.19. The linux-x64-gnu binding runs on older CPUs.
    • oxc-node@1.0.1 to oxc-node@1.0.2, the loader behind vpx for TypeScript files and vite-plus/register. TypeScript files with import and export in a CommonJS package run as CommonJS when tsconfig compiles them to CommonJS, package.json "type" selects the format of .ts files under module: node16 and nodenext, and vpx --watch on macOS no longer uses more memory each time a watched folder is replaced.
    • oxlint@1.93.0 to oxlint@1.94.0. Many fixes that can change program behavior are now suggestions or dangerous fixes, so vp check --fix applies fewer of them, and vp check --fix-dangerously applies them. typeCheck is no longer experimental, and no-misused-promises gets a flagUnions option.
    • oxfmt@0.78.0 to oxfmt@0.79.0. Oxfmt moves to Prettier 3.10.1 and fixes the output for several TypeScript, Vue, Angular, HTML, Markdown, CSS, and GraphQL cases, so formatting can change.
    • lint-staged@17.6.0 to lint-staged@17.6.1 in vp staged. The warning about hidden partially staged changes appears only when the changes are restored.
    • The new Oxfmt, Oxlint, and tsrs can flag code that passed before. If your CI runs vp check, run vp check --fix --continue-on-error after you upgrade: it formats files, applies the available lint fixes, formats again, and reports every error that remains.

Fixes & Enhancements

  • vp upgrade no longer deletes a version directory that it did not create when an installation fails, so vp upgrade --rollback still finds the previous version after a failed reinstall. vp upgrade, vp upgrade --rollback, and installer setup wait for each other, so two upgrades that run at the same time can no longer leave current pointing to a missing directory. vp upgrade also repairs an active version whose vp binary is missing (#3412), by @jong-kyung and @fengmk2.
  • An empty VP_NODE_SKIP_SIGNATURE_VERIFY, VP_NODE_DIST_MIRROR, or npm_config_registry (in either letter case) counts as unset, as in pnpm. Before, VP_NODE_SKIP_SIGNATURE_VERIFY="" turned off PGP verification of Node.js downloads, and an empty mirror or registry failed with relative URL without a base (#3444), by @jong-kyung.
  • With a token for the default npm registry in .npmrc, the package-manager shims again use cached dist-tags for a latest default and fall back to the cache offline, instead of waiting on the registry at each call and failing when it cannot be reached. Other authenticated registries still skip the cache (#3457), by @liangmiQwQ.
  • vp pack uses pack.envPrefix from vite.config.ts. Before, the default prefixes VITE_PACK_ and TSDOWN_ always replaced it, so variables under the configured prefix were not inlined and variables under the default prefixes were. The --env-prefix flag still takes precedence (#3454), by @jong-kyung.
  • vp migrate --full on a project that the first migration left on ESLint and Prettier no longer loses their settings. When vite.config.ts holds only the default lint and fmt blocks that vp migrate added, the converted settings replace them. When those blocks have your own settings, the converted .oxlintrc.json or Prettier stays in place with a warning (#3464), by @jong-kyung.
  • vp migrate writes npmPreapprovedPackages to .yarnrc.yml only for Yarn 4.10.0 and later. Older Yarn versions do not know this key and refused to run, so migrated Yarn 2 and 3 projects, and Yarn 4.0 to 4.9 projects whose Yarn upgrade failed, could not install (#3443), by @jong-kyung.
  • vp migrate merges the duplicate vite-plus imports that it creates when it rewrites vite imports, so import/no-duplicates no longer reports them. Comments, side-effect imports, and code between the imports stay in place (#3439), by @voidzero-bot[bot] and @fengmk2.
  • A second vp migrate run keeps oxlint in the dependencies of a package that publishes an Oxlint plugin, as the first run does (#3462), by @jong-kyung.
  • vp migrate warns when the root or a workspace package has turbo.json, turbo.jsonc, or a turbo dependency, because vp run does not read Turborepo configuration. The warning links to the task and cache guides for manual migration (#3300), by @voidzero-bot[bot] and @fengmk2.
  • When vp create adds a third-party template to a monorepo, it rewrites the new package's vite imports to vite-plus, so vp check no longer reports vite-plus/prefer-vite-plus-imports errors there (#3282), by @voidzero-bot[bot] and @fengmk2.
  • New monorepos from vp create reference their dependency catalog entries with catalog: and contain no unused entries, and the TypeScript and @types/node catalog versions match the generated packages (#3393), by @d4rshnn.
  • vp create works in projects pinned to Yarn 1.x: it runs templates with npx --yes, as vp dlx does, because Yarn Classic has no yarn dlx (#3468), by @jong-kyung.
  • vp env exec --node and vp env pin accept lts/*, lts/<codename>, and lts/-n, as vp env use does. vp env pin lts/* writes the resolved exact version (#3437), by @jong-kyung.
  • Ctrl+C or SIGTERM during a spinner in vp create and vp migrate ends the command by that signal, so the shell reports 130 or 143 instead of 0, as for the native spinners since 1.6.0. Escape no longer ends the command while a spinner is visible (#3432), by @jong-kyung.
  • The Vitest resolver that defineConfig adds declares a resolveId filter, so Rolldown builds skip it without a call into JavaScript for imports other than vitest, vitest/*, @vitest/*, and vite-plus/test. A synthetic build with 40,000 resolveId calls and no other work took 1.4 s instead of 1.9 s (#3434), by @jasonkuhrt.

Docs

  • Name vp test together with vp build as commands that support cooperative tracking in the cache guide (#3453), by @SaKaNa-Y.
  • Explain in the create guide what to do when no template fits: run the framework's own initializer, then follow the vp migrate guide (#3456), by @fengmk2.

Chore

  • Update npm dependencies. New generator projects from vp create vite:generator depend on bingo@^0.16.0 (#3392), by @renovate[bot].
  • Update Rust dependencies, including syn 3 and testing_macros 2 (#3312, #3460, #3461), by @renovate[bot].
  • The issue triage bot uses Conventional Commits PR titles and leaves assigned issues to their assignees (#3459, #3458), by @liangmiQwQ.
  • Compare User-Agent header names case-insensitively in an HTTP test (#3469), by @liangmiQwQ.
  • Refine the release-manager skill from the v1.5.0, v1.5.1, and v1.6.0 releases (#3348), by @fengmk2.

Bundled Versions

Tool Version Source Changelog
vite 8.3.8 b39e6e6 8.3.8
rolldown 1.2.19 b9c75dd 1.2.19
oxc-node 1.0.2 16c0f34 1.0.2
tsdown 0.23.4 npm unchanged
vitest 5.1.0 npm unchanged
oxlint 1.94.0 npm 1.94.0
tsrs 7.1.0-beta.tsrs2 npm 7.1.0-beta.tsrs2 (replaces oxlint-tsgolint)
oxfmt 0.79.0 npm 0.79.0

Upgrade

vp upgrade

In each project, run vp migrate to update vite-plus, the vite alias to @voidzero-dev/vite-plus-core@8.3.8000, and the Vitest pin together (guide).

New Contributors

@jasonkuhrt, @d4rshnn

Full Changelog: v1.6.0...v1.7.0


For a stable release, complete the HomebrewFormula/vp.rb update after publication by merging the generated release/homebrew-v1.7.0 PR.

Merging this PR will trigger the release workflow.

fengmk2 and others added 2 commits November 17, 2026 01:31
NAPI bakes the package.json version into binding/index.cjs version
checks. The prepare_release workflow bumps package.json but does not
regenerate this file, so the CI build's regeneration step produces a
diff that the post-build no-unexpected-changes guard rejects.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Update the pnpm and npx --package pins and the matching release text in
the migration guide and the setup, migration, and upgrade prompts.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 309b96a

@cloudflare-workers-and-pages

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview URL: https://release-v1-7-0-viteplus-dev.voidzero-docs.workers.dev (commit 309b96a)

This URL reflects your latest Preview deployment

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅
  • Deployment: Success ✅

View logs ↗
https://74c8c902-viteplus-dev.voidzero-docs.workers.dev 309b96a 2026-11-16T17:32:35.725Z Visit the dashboard ↗

@fengmk2 fengmk2 added the preview-build Publish this PR's commits to the registry bridge as preview builds label Nov 16, 2026
@github-actions

Copy link
Copy Markdown
Contributor

CLI artifact sizes (309b96a)

Final release artifacts built by the canonical build-upstream and build-windows-cli actions.
The dist rows use the Linux build. The core total excludes .node files to match the release artifact.

Artifact Format Base PR Change
packages/cli/dist Directory total 2.36 MiB 2.36 MiB 0 B (0.00%)
packages/core/dist Directory total 4.11 MiB 4.11 MiB 0 B (0.00%)
Combined package dist Directory total 6.47 MiB 6.47 MiB 0 B (0.00%)
vp (Linux x64) Binary 8.35 MiB 8.35 MiB 0 B (0.00%)
vp (Linux x64) gzip -9 3.82 MiB 3.82 MiB -32 B (-0.00%)
NAPI (Linux x64) Binary 37.06 MiB 37.06 MiB 0 B (0.00%)
NAPI (Linux x64) gzip -9 14.80 MiB 14.79 MiB -811 B (-0.01%)
vp (macOS ARM64) Binary 5.46 MiB 5.46 MiB 0 B (0.00%)
vp (macOS ARM64) gzip -9 3.25 MiB 3.25 MiB +74 B (+0.00%)
NAPI (macOS ARM64) Binary 43.65 MiB 43.65 MiB 0 B (0.00%)
NAPI (macOS ARM64) gzip -9 18.95 MiB 18.94 MiB -2.56 KiB (-0.01%)
vp (Windows x64) Binary 6.19 MiB 6.19 MiB 0 B (0.00%)
vp (Windows x64) gzip -9 2.86 MiB 2.86 MiB -1 B (-0.00%)
NAPI (Windows x64) Binary 33.03 MiB 33.03 MiB 0 B (0.00%)
NAPI (Windows x64) gzip -9 13.53 MiB 13.53 MiB +63 B (+0.00%)
Trampoline (Windows x64) Binary 13.50 KiB 13.50 KiB 0 B (0.00%)
Trampoline (Windows x64) gzip -9 7.09 KiB 7.09 KiB 0 B (0.00%)
Installer (Windows x64) Binary 4.69 MiB 4.69 MiB 0 B (0.00%)
Installer (Windows x64) gzip -9 2.25 MiB 2.25 MiB +1 B (+0.00%)

@github-actions

Copy link
Copy Markdown
Contributor

Preview binary sizes (309b96a)

Compared with the latest stable release, v1.6.0. Preview build.
Each row measures one binary. Negative changes mean a smaller preview binary.

Binary Latest release Preview Change
vp (macOS ARM64) 5.46 MiB 5.46 MiB +32 B (+0.00%)
NAPI (macOS ARM64) 43.39 MiB 43.61 MiB +226.23 KiB (+0.51%)
vp (macOS x64) 6.92 MiB 6.93 MiB +16.05 KiB (+0.23%)
NAPI (macOS x64) 48.76 MiB 49.00 MiB +245.23 KiB (+0.49%)
vp (Linux ARM64 GNU) 6.90 MiB 6.91 MiB +8.05 KiB (+0.11%)
NAPI (Linux ARM64 GNU) 32.68 MiB 32.92 MiB +248.02 KiB (+0.74%)
vp (Linux ARM64 musl) 6.97 MiB 6.99 MiB +10.73 KiB (+0.15%)
NAPI (Linux ARM64 musl) 31.89 MiB 32.13 MiB +248.52 KiB (+0.76%)
vp (Linux x64 GNU) 8.33 MiB 8.35 MiB +16.05 KiB (+0.19%)
NAPI (Linux x64 GNU) 36.69 MiB 36.98 MiB +292.00 KiB (+0.78%)
vp (Linux x64 musl) 8.41 MiB 8.42 MiB +8.81 KiB (+0.10%)
NAPI (Linux x64 musl) 35.90 MiB 36.18 MiB +290.47 KiB (+0.79%)
vp (Windows x64) 6.19 MiB 6.19 MiB 0 B (0.00%)
NAPI (Windows x64) 32.45 MiB 32.67 MiB +226.00 KiB (+0.68%)
Trampoline (Windows x64) 13.00 KiB 13.00 KiB 0 B (0.00%)
Installer (Windows x64) 4.69 MiB 4.69 MiB +5.00 KiB (+0.10%)
vp (Windows ARM64) 5.42 MiB 5.42 MiB +3.50 KiB (+0.06%)
NAPI (Windows ARM64) 28.66 MiB 28.85 MiB +202.00 KiB (+0.69%)
Trampoline (Windows ARM64) 13.00 KiB 13.00 KiB 0 B (0.00%)
Installer (Windows ARM64) 3.86 MiB 3.86 MiB +5.00 KiB (+0.13%)
gzip -9 sizes
Binary Latest release Preview Change
vp (macOS ARM64) 3.25 MiB 3.25 MiB +3.05 KiB (+0.09%)
NAPI (macOS ARM64) 18.85 MiB 18.93 MiB +84.79 KiB (+0.44%)
vp (macOS x64) 3.43 MiB 3.44 MiB +6.97 KiB (+0.20%)
NAPI (macOS x64) 20.12 MiB 20.22 MiB +101.60 KiB (+0.49%)
vp (Linux ARM64 GNU) 3.74 MiB 3.75 MiB +6.66 KiB (+0.17%)
NAPI (Linux ARM64 GNU) 13.93 MiB 14.02 MiB +85.20 KiB (+0.60%)
vp (Linux ARM64 musl) 3.77 MiB 3.77 MiB +7.01 KiB (+0.18%)
NAPI (Linux ARM64 musl) 13.64 MiB 13.72 MiB +81.96 KiB (+0.59%)
vp (Linux x64 GNU) 3.81 MiB 3.82 MiB +4.52 KiB (+0.12%)
NAPI (Linux x64 GNU) 14.65 MiB 14.75 MiB +102.50 KiB (+0.68%)
vp (Linux x64 musl) 3.84 MiB 3.84 MiB +2.97 KiB (+0.08%)
NAPI (Linux x64 musl) 14.33 MiB 14.43 MiB +96.56 KiB (+0.66%)
vp (Windows x64) 2.86 MiB 2.86 MiB -2.59 KiB (-0.09%)
NAPI (Windows x64) 13.31 MiB 13.39 MiB +83.07 KiB (+0.61%)
Trampoline (Windows x64) 7.14 KiB 7.14 KiB -1 B (-0.01%)
Installer (Windows x64) 2.25 MiB 2.25 MiB +1.97 KiB (+0.09%)
vp (Windows ARM64) 2.73 MiB 2.73 MiB +287 B (+0.01%)
NAPI (Windows ARM64) 12.62 MiB 12.70 MiB +80.33 KiB (+0.62%)
Trampoline (Windows ARM64) 6.93 KiB 6.93 KiB -1 B (-0.01%)
Installer (Windows ARM64) 2.14 MiB 2.14 MiB +3.28 KiB (+0.15%)

Raw sizes are uncompressed file sizes. gzip sizes recompress each binary at level 9; they are not package or download archive sizes.
The baseline uses published release files, including NAPI packages from npm at the same version. Build versions and toolchains can affect the difference.

@github-actions

Copy link
Copy Markdown
Contributor

Registry bridge build (309b96a)

This commit build is published to the registry bridge, which serves these as ordinary npm versions (every other package proxies to npmjs):

Package Version
vite-plus 0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440
@voidzero-dev/vite-plus-core 0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440
create-vite-plus 0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440

Install the Vite+ CLI built from this commit, then migrate a project:

# macOS / Linux
curl -fsSL https://raw.githubusercontent.com/voidzero-dev/vite-plus/309b96aaf065d95452ca218076c666671cf36440/packages/cli/install.sh | VP_PR_VERSION=3471 VP_LEGACY_INSTALLER_URL=https://raw.githubusercontent.com/voidzero-dev/vite-plus/309b96aaf065d95452ca218076c666671cf36440/packages/cli/install-legacy.sh bash
# Windows (PowerShell)
$env:VP_PR_VERSION="3471"; $env:VP_LEGACY_INSTALLER_URL="https://raw.githubusercontent.com/voidzero-dev/vite-plus/309b96aaf065d95452ca218076c666671cf36440/packages/cli/install-legacy.ps1"; irm https://raw.githubusercontent.com/voidzero-dev/vite-plus/309b96aaf065d95452ca218076c666671cf36440/packages/cli/install.ps1 | iex

Or install with Homebrew (macOS / glibc Linux):

These commands use the formula and binary from this published commit. Replace brew install with brew reinstall if the tap package is already installed.
If Homebrew Core’s vite-plus is installed, run brew uninstall vite-plus first. This keeps your user data; do not run vp implode to switch installations.

(
  set -eu
  export HOMEBREW_NO_AUTO_UPDATE=1
  export HOMEBREW_VP_PR_VERSION=309b96aaf065d95452ca218076c666671cf36440
  brew tap voidzero-dev/vite-plus https://github.com/voidzero-dev/vite-plus
  preview_tap="$(brew --repository voidzero-dev/vite-plus)"
  git -C "$preview_tap" fetch --depth=1 https://github.com/voidzero-dev/vite-plus.git "$HOMEBREW_VP_PR_VERSION"
  git -C "$preview_tap" switch --detach "$HOMEBREW_VP_PR_VERSION"
  brew install voidzero-dev/vite-plus/vp
  brew test voidzero-dev/vite-plus/vp
  "$(brew --prefix)/bin/vp"
)

The tap stays at the tested commit. Return it to main after testing:

git -C "$(brew --repository voidzero-dev/vite-plus)" switch main

Or download the standalone Windows installer built from this commit:

Architecture Installer
x64 vp-setup-x86_64-pc-windows-msvc.exe
Arm64 vp-setup-aarch64-pc-windows-msvc.exe

GitHub requires you to sign in and downloads each installer as a ZIP artifact. Extract vp-setup.exe, then run it against this preview build:

.\vp-setup.exe --version "0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440" --registry "https://registry-bridge.viteplus.dev/"

After installing, upgrade the current project's vite-plus to this test build with:

vp migrate

Or create a new project from this commit without installing the CLI:

export npm_config_registry=https://registry-bridge.viteplus.dev/ pnpm_config_registry=https://registry-bridge.viteplus.dev/
pnpm create vite-plus@0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440 # or: npm create vite-plus@0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440
$env:npm_config_registry="https://registry-bridge.viteplus.dev/"; $env:pnpm_config_registry="https://registry-bridge.viteplus.dev/"
pnpm create vite-plus@0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440 # or: npm create vite-plus@0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440

pnpm 11+ reads pnpm_config_registry, npm and older pnpm read npm_config_registry. The new project pins this build, so keep the registry set for later installs, or configure it as below.

Or point your package manager at the bridge registry https://registry-bridge.viteplus.dev/:

Package manager Registry config
npm / pnpm / Bun .npmrc: registry=https://registry-bridge.viteplus.dev/
Yarn (v2+) .yarnrc.yml: npmRegistryServer: "https://registry-bridge.viteplus.dev/"

Then pin the build (vite aliases to vite-plus-core; pnpm can use a catalog, npm an overrides entry):

{
  "devDependencies": {
    "vite-plus": "0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440",
    "vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.309b96aaf065d95452ca218076c666671cf36440"
  }
}

@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker preview image

Built from this PR's registry bridge build:

Image Compressed size
ghcr.io/voidzero-dev/vite-plus:pr-3471 229MB
# remove any stale local copy from a previous run, then pull fresh
docker rmi ghcr.io/voidzero-dev/vite-plus:pr-3471 2>/dev/null; docker pull ghcr.io/voidzero-dev/vite-plus:pr-3471

Quick check:

docker run --rm ghcr.io/voidzero-dev/vite-plus:pr-3471 vp --version

See docs/guide/docker.md for usage.

@fengmk2
fengmk2 merged commit a3f54d7 into main Nov 17, 2026
121 of 135 checks passed
@fengmk2
fengmk2 deleted the release/v1.7.0 branch November 17, 2026 02:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

preview-build Publish this PR's commits to the registry bridge as preview builds

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant