Skip to content

feat(deps): upgrade upstream dependencies - #2500

Merged
fengmk2 merged 4 commits into
mainfrom
deps/upstream-update
Aug 19, 2026
Merged

feat(deps): upgrade upstream dependencies#2500
fengmk2 merged 4 commits into
mainfrom
deps/upstream-update

Conversation

@voidzero-guard

Copy link
Copy Markdown
Contributor

Summary

  • Automated upgrade of upstream dependencies: Vitest 4.1.10 -> 4.1.11 (all @vitest/* packages), Oxlint 1.78.0 -> 1.79.0, Oxfmt 0.63.0 -> 0.64.0, the oxc family 0.144.0 -> 0.145.0, and @vitejs/devtools0.4.12 -> 0.5.0.
  • rolldown (v1.2.4) and vite (v8.2.1) are unchanged; tsdown stays at 0.22.14, so no CLI option sync or workspace re-merge was needed.
  • PTY snapshots re-recorded for the new Vitest banner, the new react/* rules emitted by oxlint 1.79.0, and the migration dependency table.
  • Snapshot runner now pins pnpm's minimumReleaseAge to 0 so freshly published toolchain packages are not quarantined on the day of a bump.

Dependency updates

PackageFromTo
vitest4.1.104.1.11
@vitest/browser4.1.104.1.11
@vitest/browser-playwright4.1.104.1.11
@vitest/browser-preview4.1.104.1.11
@vitest/browser-webdriverio4.1.104.1.11
@vitest/expect4.1.104.1.11
@vitest/mocker4.1.104.1.11
@vitest/pretty-format4.1.104.1.11
@vitest/runner4.1.104.1.11
@vitest/snapshot4.1.104.1.11
@vitest/spy4.1.104.1.11
@vitest/utils4.1.104.1.11
oxfmt0.63.00.64.0
oxlint1.78.01.79.0
@oxlint/plugins1.73.01.79.0
@oxc-project/runtime0.144.00.145.0
@oxc-project/types0.144.00.145.0
oxc-minify0.144.00.145.0
oxc-parser0.144.00.145.0
oxc-transform0.144.00.145.0
@vitejs/devtools0.4.120.5.0
VITEST_VERSION constant4.1.104.1.11
README vitest pins4.1.104.1.11
Unchanged dependencies
  • rolldown: v1.2.4 (483c648)
  • vite: v8.2.1 (4216158)
  • tsdown: 0.22.14
  • @tsdown/css: 0.22.14
  • @tsdown/exe: 0.22.14
  • lightningcss: ^1.33.0
  • @oxc-node/cli: 0.1.0
  • @oxc-node/core: 0.1.0
  • oxlint-tsgolint: 7.0.2001

Code changes

  • crates/vp_cli_snapshots/tests/cli_snapshots/main.rs: set PNPM_CONFIG_MINIMUM_RELEASE_AGE and pnpm_config_minimum_release_age to 0 in the baseline snapshot env. pnpm >= 11 defaults minimumReleaseAge to 24 hours, which quarantines the just-published toolchain packages in real-install fixtures and writes exact-version minimumReleaseAgeExclude entries into the generated pnpm-workspace.yaml.
  • crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/command_tool_help/snapshots/command_tool_deep_help_delegation.md: vitest banner 4.1.10 -> 4.1.11.
  • crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/migration_npmx_dev/snapshots/migration_npmx_dev.md: dependency table now lists vitest, @vitest/browser-playwright and @vitest/coverage-v8 upgrades, with realigned columns.
  • crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/new_create_vite_migrates_eslint_prettier/snapshots/new_create_vite_migrates_eslint_prettier.md: records the additional react/* rules emitted by oxlint 1.79.0.
  • packages/cli/src/migration/migrator/catalog.ts, packages/cli/src/migration/migrator/setup.ts: oxfmt 0.64.0 rewrites invisible Unicode characters in comments (U+2009 thin space -> two spaces, U+200B zero-width space -> backslash escape). Comment text only.
  • README.md, packages/cli/README.md, docs/guide/migrate.md, packages/cli/src/utils/constants.ts, packages/core/package.json, pnpm-workspace.yaml, pnpm-lock.yaml: version pins and lockfile.

Build status

  • sync-remote-and-build: success
  • build-upstream: success

- vitest: 4.1.10 -> 4.1.11
- @vitest/browser: 4.1.10 -> 4.1.11
- @vitest/browser-playwright: 4.1.10 -> 4.1.11
- @vitest/browser-preview: 4.1.10 -> 4.1.11
- @vitest/browser-webdriverio: 4.1.10 -> 4.1.11
- @vitest/expect: 4.1.10 -> 4.1.11
- @vitest/mocker: 4.1.10 -> 4.1.11
- @vitest/pretty-format: 4.1.10 -> 4.1.11
- @vitest/runner: 4.1.10 -> 4.1.11
- @vitest/snapshot: 4.1.10 -> 4.1.11
- @vitest/spy: 4.1.10 -> 4.1.11
- @vitest/utils: 4.1.10 -> 4.1.11
- oxfmt: 0.63.0 -> 0.64.0
- oxlint: 1.78.0 -> 1.79.0
- @oxlint/plugins: 1.73.0 -> 1.79.0
- @oxc-project/runtime: 0.144.0 -> 0.145.0
- @oxc-project/types: 0.144.0 -> 0.145.0
- oxc-minify: 0.144.0 -> 0.145.0
- oxc-parser: 0.144.0 -> 0.145.0
- oxc-transform: 0.144.0 -> 0.145.0
- @vitejs/devtools: 0.4.12 -> 0.5.0
- VITEST_VERSION constant: 4.1.10 -> 4.1.11
- README vitest pins: 4.1.10 -> 4.1.11
rolldown (v1.2.4, 483c648) and vite (v8.2.1, 4216158) are unchanged.
Code changes:
- crates/vp_cli_snapshots/tests/cli_snapshots/main.rs: set
PNPM_CONFIG_MINIMUM_RELEASE_AGE / pnpm_config_minimum_release_age to 0 in
the baseline snapshot env so pnpm's 24h minimumReleaseAge default does not
quarantine freshly published toolchain packages and emit
minimumReleaseAgeExclude entries into fixture output.
- crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/command_tool_help/snapshots/command_tool_deep_help_delegation.md:
vitest banner 4.1.10 -> 4.1.11.
- crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/migration_npmx_dev/snapshots/migration_npmx_dev.md:
dependency table now lists vitest, @vitest/browser-playwright and
@vitest/coverage-v8 upgrades, with realigned columns.
- crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/new_create_vite_migrates_eslint_prettier/snapshots/new_create_vite_migrates_eslint_prettier.md:
records the additional react/* rules emitted by oxlint 1.79.0.
- packages/cli/src/migration/migrator/catalog.ts,
packages/cli/src/migration/migrator/setup.ts: oxfmt 0.64.0 rewrites
invisible Unicode characters in comments (U+2009 -> two spaces,
U+200B -> backslash escape).
@voidzero-guard

Copy link
Copy Markdown
ContributorAuthor

✅ No upstream CLI help changes detected

Compared normalized --help output for the upstream CLIs mirrored by Vite+.

➖ Vite: no version update (8.2.1)

No version update was detected, so there is no CLI help diff.

✅ Vitest: no CLI help changes (4.1.10 → 4.1.11)

The version was updated, but the normalized CLI help output has no differences.

✅ Oxlint: no CLI help changes (1.78.0 → 1.79.0)

The version was updated, but the normalized CLI help output has no differences.

✅ Oxfmt: no CLI help changes (0.63.0 → 0.64.0)

The version was updated, but the normalized CLI help output has no differences.

➖ tsdown: no version update (0.22.14)

No version update was detected, so there is no CLI help diff.

@netlify

netlifyBot commented Aug 19, 2026

Copy link
Copy Markdown

Deploy Preview for viteplus-preview canceled.

NameLink
🔨 Latest commitc05f9ae
🔍 Latest deploy loghttps://app.netlify.com/projects/viteplus-preview/deploys/6a85c4113258730008154317

@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: c05f9ae

@socket-security

socket-securityBot commented Aug 19, 2026

Copy link
Copy Markdown

@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Native binary sizes (c05f9ae)

Final release artifacts built by the canonical build-upstream and build-windows-cli actions.

ArtifactFormatBasePRChange
vp (Linux x64)Binary10.70 MiB10.70 MiB0 B (0.00%)
vp (Linux x64)gzip -94.63 MiB4.63 MiB0 B (0.00%)
NAPI (Linux x64)Binary32.03 MiB32.03 MiB0 B (0.00%)
NAPI (Linux x64)gzip -912.61 MiB12.61 MiB0 B (0.00%)
vp (macOS ARM64)Binary8.00 MiB8.00 MiB0 B (0.00%)
vp (macOS ARM64)gzip -94.04 MiB4.04 MiB0 B (0.00%)
NAPI (macOS ARM64)Binary39.68 MiB39.68 MiB0 B (0.00%)
NAPI (macOS ARM64)gzip -916.92 MiB16.92 MiB+1 B (+0.00%)
vp (Windows x64)Binary8.59 MiB8.59 MiB0 B (0.00%)
vp (Windows x64)gzip -93.75 MiB3.75 MiB+1 B (+0.00%)
NAPI (Windows x64)Binary26.91 MiB26.91 MiB0 B (0.00%)
NAPI (Windows x64)gzip -910.69 MiB10.69 MiB+8 B (+0.00%)
Trampoline (Windows x64)Binary216.50 KiB216.50 KiB0 B (0.00%)
Trampoline (Windows x64)gzip -9104.34 KiB104.34 KiB0 B (0.00%)
Installer (Windows x64)Binary4.48 MiB4.48 MiB0 B (0.00%)
Installer (Windows x64)gzip -92.10 MiB2.10 MiB-1 B (-0.00%)

@fengmk2fengmk2 self-assigned this Aug 19, 2026
@fengmk2fengmk2 added the preview-build Publish this PR's commits to the registry bridge as preview builds label Aug 19, 2026
@github-actions

github-actionsBot commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Registry bridge build (c05f9ae)

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

PackageVersion
vite-plus0.0.0-commit.c05f9ae9fd34ca943667bcfd54c5e12c3735bc96
@voidzero-dev/vite-plus-core0.0.0-commit.c05f9ae9fd34ca943667bcfd54c5e12c3735bc96

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

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

Or download the standalone Windows installer built from this commit:

ArchitectureInstaller
x64vp-setup-x86_64-pc-windows-msvc.exe
Arm64vp-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.c05f9ae9fd34ca943667bcfd54c5e12c3735bc96"--registry "https://registry-bridge.viteplus.dev/"

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

vp migrate

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

Package managerRegistry 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.c05f9ae9fd34ca943667bcfd54c5e12c3735bc96",
"vite": "npm:@voidzero-dev/vite-plus-core@0.0.0-commit.c05f9ae9fd34ca943667bcfd54c5e12c3735bc96"
}
}

@github-actions

Copy link
Copy Markdown
Contributor

🐳 Docker preview image

Built from this PR's registry bridge build:

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

Quick check:

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

See docs/guide/docker.md for usage.

@fengmk2fengmk2 added preview-build Publish this PR's commits to the registry bridge as preview builds and removed preview-build Publish this PR's commits to the registry bridge as preview builds labels Aug 19, 2026
@fengmk2
fengmk2 merged commit a44405f into mainAug 19, 2026
115 of 142 checks passed
@fengmk2
fengmk2 deleted the deps/upstream-update branch August 19, 2026 15:41
fengmk2 pushed a commit that referenced this pull request Aug 24, 2026
…1.4 support (#2536)
Fresh installs now use a split directory layout instead of a single
`~/.vite-plus` root. Unix follows the XDG base directory specification,
and Windows uses the standard `%LOCALAPPDATA%` and `%APPDATA%` folders.
Existing `~/.vite-plus` installs keep their current directory layout.
`vp migrate` also converts `tsup` projects, and `vp` now sends Bun `1.4`
package-manager commands to `bun` directly. The published npm package
shrank by about half, and the upgrade check no longer delays each
command.
### Breaking Changes
- Fresh installs now use a split directory layout instead of a single
root: XDG base directories on Unix, and the standard known folders on
Windows. Existing `~/.vite-plus` installs keep their current layout, and
the installer does not move their files. `VP_HOME` still selects the
single-root layout
([#2346](#2346)), by
@forehalo
| Category | Unix default | Windows default | Single-root (`VP_HOME`) |
| --- | --- | --- | --- |
| bin | `~/.local/share/vite-plus/bin` | `%LOCALAPPDATA%\vite-plus\bin`
| `<root>/bin` |
| data | `~/.local/share/vite-plus` | `%LOCALAPPDATA%\vite-plus\data` |
`<root>` |
| cache | `~/.cache/vite-plus` | `%LOCALAPPDATA%\vite-plus\cache` |
`<root>/cache` |
| config | `~/.config/vite-plus` | `%APPDATA%\vite-plus` | `<root>` |
| state | `~/.local/state/vite-plus` | `%LOCALAPPDATA%\vite-plus\state`
| `<root>` |
The installer configures your shell for the new location, and CI that
installs through `setup-vp` keeps the single-root layout automatically.
Update each hard-coded `~/.vite-plus/bin` path, such as a path in a
Dockerfile.
### Highlights
- `vp migrate` now converts `tsup` projects. It replaces the `tsup`
dependency and script with `vp pack`. It also changes `tsup.config.ts`
to a `tsdown.config.ts` that imports from `vite-plus/pack`
([#2434](#2434)), by
@KTrain5169
- Shell integrations now accept the global `-C` flag. `vp -C <dir> env
use` changes the environment of your current shell. The `-C<dir>` and
`-C=<dir>` forms also work. In zsh, Fish, Nushell, and PowerShell, `vpr`
completion keeps the working directory when it changes the command to
`vp run` ([#2508](#2508)),
by @simulacre7
- The published `vite-plus` npm package shrank from 1.05 MB to 516 kB, a
51% reduction. It now includes only Markdown files from the
documentation workspace. It no longer includes VitePress tooling,
images, or deployment files
([#2480](#2480)), by
@liangmiQwQ
### Features
- With Bun `1.4` or later, Vite+ forwards these commands and flags to
`bun`. Earlier Bun versions keep their fallback or unsupported behavior
and report the required Bun version
([#2513](#2513)), by
@jong-kyung
- `vp dedupe` runs `bun dedupe`, including `--check`
- `vp pm prune` runs `bun prune`
- `vp pm audit --fix` runs `bun audit fix`
- `vp add`, `vp remove`, and `vp update` send `--filter` to `bun`
- `vp add --save-catalog` sends `--catalog` to `bun`
- The upgrade check no longer delays fast commands. It runs in a
separate process. It reports an available update during a later command,
and commands no longer wait for the registry
([#2380](#2380)), by
@liangmiQwQ
- Upgrade the bundled toolchain
([#2443](#2443),
[#2500](#2500),
[#2504](#2504),
[#2519](#2519),
[#2532](#2532)), by
@voidzero-guard[bot]:
- `vite`: `8.2.1` to `8.2.2`
- `rolldown`: `1.2.3` to `1.2.5`
- `vitest`: `4.1.10` to `4.1.11`
- `oxlint`: `1.77.0` to `1.79.0`
- `oxfmt`: `0.62.0` to `0.64.0`
- Oxc packages and crates: `0.143.0` to `0.146.0`
- Vite+ now accepts `@vitejs/devtools` `0.5.x`. The optional peer range
is `^0.4.0 || ^0.5.0`. This repository uses `0.5.2`.
- `oxfmt` and `oxlint` can report new issues after the upgrade. Run `vp
check` locally. Use `vp fmt` to fix formatting changes.
- `vp toolchain` draws its tree with Unicode glyphs. It no longer uses
ASCII connectors
([#2442](#2442)), by
@liangmiQwQ
### Fixes & Enhancements
- At a workspace root, bare app commands now use `defaultPackage` or
detected root configuration before they select a member package. A
workspace without member packages runs the command in the root
([#2530](#2530),
[#2533](#2533)), by
@fengmk2
- `vp up` no longer changes `"vite": "catalog:"` to a version alias
under `pnpm`. Catalog references now stay unchanged during an update.
Run `vp migrate` once to correct an existing project
([#2425](#2425)), by
@fengmk2
- If the server accepts range requests, an interrupted runtime download
continues from the bytes on disk. It does not start again
([#2452](#2452)), by
@tarikermis
- The local CLI shows the install instructions when you run a
global-only command such as `env`, `upgrade`, or `implode`
([#2522](#2522)), by
@jong-kyung
- `vp up -g` asks npm for globally installed package versions. A
project-level setting no longer makes the lookup fail and hide an
available update
([#2438](#2438)), by
@jong-kyung
- When hooks are disabled through `HUSKY=0`, `VP_GIT_HOOKS=0`, or
`VITE_GIT_HOOKS=0`, `vp config` skips the Git lookup. This lets `vp
config` run in a container without Git
([#2458](#2458)), by
@tarikermis
- `vp create vite:monorepo` now asks once about Git and runs `git init`
once ([#2417](#2417)), by
@jong-kyung
- `vp create` does not ask about pre-commit hooks when you choose not to
initialize Git
([#2477](#2477)), by
@liangmiQwQ
- `vp pack --no-config` does not read the Vite config. A local
`vite.config.*` file, its `pack` options, and its hooks no longer run
([#2486](#2486)), by
@jong-kyung
- `vp pack --help` shows the supported `--no-config` options
([#2487](#2487)), by
@jong-kyung
- `vp staged --no-concurrent` works again. `--concurrent` accepts
`true`, `false`, or a number greater than `0`. It rejects other values.
Vite+ also rejects `--no-cwd`, `--no-diff`, and `--no-diff-filter`
([#2501](#2501)), by
@RSS1102
- `vp` reads about 450 kB less JavaScript at start. It loads the
`--init` and `--migrate` helpers only when a command needs them
([#2490](#2490)), by
@jong-kyung
- The standalone `vp` binary is smaller. Vite+ no longer copies the
package-manager command tree, and it disables unused tar and dialoguer
features ([#2507](#2507)),
by @liangmiQwQ
- A generated Fish environment file escapes the special characters in a
path ([#2492](#2492)), by
@fengmk2
- A generated POSIX shell environment file escapes the special
characters in a path. It also removes each duplicate Vite+ bin entry
([#2494](#2494)), by
@fengmk2
- The generated `cmd.exe` wrapper preserves the exit status from `vp env
use`. It does not apply output after a failed command
([#2496](#2496)), by
@fengmk2
- `vp exec` resolves a relative `PATH` entry such as
`./node_modules/.bin` against the working directory of the command
([#2350](#2350)), by
@RSS1102
- Older GitLab `setup-vp` templates continue to work. The installer
selects the legacy layout for them. A template can select the new layout
with `VP_VPDIRS_AWARE=1`
([#2520](#2520)), by
@fengmk2
- The Windows installer checks the directory variables and the requested
version before it downloads a payload. It also repairs a broken
`current` junction
([#2505](#2505)), by
@fengmk2
- `install.sh` does not show shell configuration warnings when `CI=true`
([#2511](#2511)), by
@fengmk2
- On Windows, `vp implode` can remove Vite+ roots that contain long or
locked paths. A native helper does this work, and it retries cleanup and
writes an error log if cleanup fails
([#2510](#2510)), by
@fengmk2
- A Windows trampoline sidecar must have a `vite-plus-shim-v1` header.
The trampoline rejects one without that header instead of guessing the
install layout
([#2526](#2526)), by
@fengmk2
### Docs
- Document the `vite-plus/test` import surface
([#2413](#2413)), by
@jong-kyung
- Add `vp hooks` to the README command list
([#2446](#2446)), by
@lyzno1
### Chore
- Add Yii to the core team
([#2435](#2435)), by
@forehalo
- Include install e2e in the aggregate CI status
([#2439](#2439)), by
@jong-kyung
- Use the catalog for shared dependencies
([#2447](#2447)), by
@liangmiQwQ
- Replace `husky` with `vp` git hooks in this repo
([#1001](#1001)), by
@Arthie
- Exclude test fixtures from Renovate scanning
([#2457](#2457)), by
@fengmk2
- Keep the binary size report in the job summary for fork PRs
([#2448](#2448)), by
@fengmk2
- Update crate-ci/typos action to v1.49.0
([#2467](#2467)), by
@renovate[bot]
- Update GitHub Actions
([#2474](#2474)), by
@renovate[bot]
- Update the `napi` crate to `3.12.2`
([#2527](#2527)), by
@fengmk2
- Ignore every `vite-task` git dependency in Renovate
([#2478](#2478)), by
@fengmk2
- Link preview installers and pin install scripts in CI
([#2499](#2499)), by
@fengmk2
- Cover PowerShell setup in tests
([#2495](#2495)), by
@fengmk2
- Cover Nushell file-based use in tests
([#2497](#2497)), by
@fengmk2
- Remove redundant dist/test inclusion from the CLI package
([#2506](#2506)), by
@jong-kyung
- Redact the `bun` build hash in snapshots
([#2514](#2514)), by
@jong-kyung
- Align the command-routing RFC with the current global CLI
([#2528](#2528)), by
@jong-kyung
- Fold v0.2.9 release learnings into the release-manager skill
([#2429](#2429)), by
@fengmk2
- Add `vp_pm_cli_macros` and `vp_toolchain` to the repo map
([#2524](#2524)), by
@jong-kyung
### Bundled Versions
| Tool | Version | Source |
| --------------- | ---------- |
---------------------------------------------------------------------------------
|
| vite | `8.2.2` |
[`de1111a`](vitejs/vite@de1111a)
|
| rolldown | `1.2.5` |
[`84c904b`](rolldown/rolldown@84c904b)
|
| tsdown | `0.22.14` | [npm](https://npmx.dev/package/tsdown/v/0.22.14)
|
| vitest | `4.1.11` | [npm](https://npmx.dev/package/vitest/v/4.1.11) |
| oxlint | `1.79.0` | [npm](https://npmx.dev/package/oxlint/v/1.79.0) |
| oxlint-tsgolint | `7.0.2001` |
[npm](https://npmx.dev/package/oxlint-tsgolint/v/7.0.2001) |
| oxfmt | `0.64.0` | [npm](https://npmx.dev/package/oxfmt/v/0.64.0) |
### Upgrade
```bash
vp upgrade
```
### New Contributors
@simulacre7
**Full Changelog**:
v0.2.9...v0.3.0
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

preview-buildPublish 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

@fengmk2