Skip to content

chore(deps): update dependency vite-plus to v1 - #2938

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vite+
Open

chore(deps): update dependency vite-plus to v1#2938
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/major-vite+

Conversation

@renovate

@renovate renovate Bot commented Oct 8, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vite-plus (source) 0.0.0-commit.11393b1a9ec1739c5897fefd418bdb095a34db7e → 1.1.0 age adoption passing confidence

Release Notes

voidzero-dev/vite-plus (vite-plus)

v1.1.0: vite-plus v1.1.0: faster vp dev startup and clearer interactive prompts

Compare Source

Vite+ 1.1 starts vp dev faster and makes the interactive prompts clearer, alongside fixes for vp migrate, package-manager commands, and Windows terminals.

Highlights
  • vp dev reaches its local URL about 24% sooner and uses about 30% less memory in the parent process, because Vite+ no longer loads Vite and Vitest there before starting the dev server (#​2851), by @​camc314.
  • Interactive prompts render boxes, logs, and wrapped text consistently, with clearer hints, validation, and navigation instructions (#​2870), by @​cpojer.
Features
  • vp run sets npm_execpath and npm_config_user_agent for npm, pnpm, and Yarn, so tools such as npm-run-all2 use the project's package manager instead of falling back to npm (#​2895), by @​naokihaba and @​tarikermis.
  • Upgrade vite@8.3.1 to vite@8.3.3, rolldown@1.2.11 to rolldown@1.2.12, vitest@5.0.1 to vitest@5.0.3, oxlint@1.85.0 to oxlint@1.87.0, and oxfmt@0.70.0 to oxfmt@0.72.0. The new lint and format versions can flag code that passed before, so run vp fmt after upgrading if CI runs vp check. vp migrate now keeps the React Refresh allowCompoundComponents option because the bundled Oxlint supports it (#​2871, #​2896, #​2904), by @​voidzero-guard[bot].
Fixes & Enhancements
  • vp migrate keeps Oxlint rules written with plugin aliases (such as @typescript-eslint/*, react-hooks/*, and import-x/*) and removes rules the bundled Oxlint does not support, listing them in a warning (#​2820, #​2906), by @​TheAlexLichter and @​yusuke99.
  • vp migrate leaves projects without a declared package manager unpinned, keeps existing declarations, and points to vp env pin when it infers one (#​2817), by @​TheAlexLichter.
  • vp migrate reports a short error for a directory without package.json instead of an ENOENT stack trace (#​2821), by @​TheAlexLichter.
  • vp create in an existing pnpm workspace adds the catalog entries the new application needs, so installation no longer fails with ERR_PNPM_CATALOG_ENTRY_NOT_FOUND_FOR_SPEC (#​2808), by @​SaKaNa-Y.
  • On Windows, one Ctrl+C stops vpr scripts and managed Bun, pnpm, npm, and Yarn commands without leaving cmd.exe stuck at Terminate batch job (Y/N)? (#​2890), by @​fengmk2.
  • vp pack --watch on Windows rebuilds with the new options after the config file changes (#​2826), by @​liangmiQwQ.
  • vp test doctor and vp test complete run the Vitest subcommands instead of being treated as test file filters (#​2879), by @​liangmiQwQ.
  • With isolated dependency layouts such as pnpm's global virtual store, vp pack finds installed Vue language tools and TypeScript Go for declaration generation, and Playwright browser provider options keep their types (#​2868, #​2865), by @​liangmiQwQ.
  • Package-manager commands fail when the project's package manager does not support a named option, instead of silently dropping it and continuing. Bun 1.4.1+ receives --offline and --prefer-offline, and Yarn Classic accepts a single --filter for vp remove (#​2775), by @​jong-kyung.
  • vp pm config in Bun projects falls back to npm, as its warning says (#​2899), by @​jong-kyung.
  • vp pm approve-builds states that Yarn Berry disables third-party build scripts by default from 4.14.0, not in every version (#​2902), by @​jong-kyung.
  • vp implode asks you to type boom instead of uninstall to confirm (#​2901), by @​fengmk2.
  • Global package installs and updates print a green +, and removals a red -, with bold package names in both (#​2828), by @​liangmiQwQ.
  • Setup headings and command hints keep their colors when the installer captures stdout (#​2829), by @​liangmiQwQ.
Refactor
  • Replace semver with verkit in the CLI, reducing the bundled CLI JavaScript by about 26 KB (#​2837), by @​liangmiQwQ.
  • Share the shim filename logic between setup and vp env doctor, and remove unused config migration metadata (#​2876, #​2894), by @​jong-kyung.
Docs
Chore
Bundled Versions
Tool Version Source Changelog
vite 8.3.3 fea5b21 8.3.2, 8.3.3
rolldown 1.2.12 45e407b 1.2.12
tsdown 0.23.0 npm unchanged
vitest 5.0.3 npm 5.0.2, 5.0.3
oxlint 1.87.0 npm 1.86.0, 1.87.0
oxlint-tsgolint 7.0.2003 npm unchanged
oxfmt 0.72.0 npm 0.71.0, 0.72.0
Upgrade
vp upgrade
New Contributors

@​hyunbinseo

Full Changelog: v1.0.0...v1.1.0

Published Packages
  • @voidzero-dev/vite-plus-core@1.1.0
  • vite-plus@1.1.0
Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:1.1.0 vp build

Run any vp command without installing it; see the Docker guide for more.

v1.0.0: vite-plus v1.0.0: Vite+ 1.0 is stable

Compare Source

Vite+ 1.0 is stable (announcement). This release promotes v1.0.0-rc.1 to stable with no code changes.

Notable changes since v0.3.3

v1.0.0 includes everything from the two release candidates below. See each release's notes for the full list of changes.

  • v1.0.0-rc.0: vp test moves to vitest@5.0.1, and the CLI now requires Node.js ^22.18.0 || ^24.11.0 || >=26.0.0. vp staged has new Node.js and Git minimums. Standalone installs and vp upgrade verify release provenance.
  • v1.0.0-rc.1: task cache settings in run.tasks move under cache. vp lint and vp fmt run from a package directory now use the same config as your editor.

Projects on v1.0.0-rc.1 need no changes. Projects on v1.0.0-rc.0 whose tasks set env, untrackedEnv, input, or output should run vp migrate to move those settings under cache. For a Vite+ 0.3 project, follow Upgrade from Vite+ 0.3 to 1.0 and run vp migrate before you update the project's dependencies.

Bundled Versions
Tool Version Source
vite 8.3.1 39ddf7c
rolldown 1.2.11 8df4219
tsdown 0.23.0 npm
vitest 5.0.1 npm
oxlint 1.85.0 npm
oxlint-tsgolint 7.0.2003 npm
oxfmt 0.70.0 npm
Upgrade
vp upgrade

Full Changelog: v1.0.0-rc.1...v1.0.0

Published Packages
  • @voidzero-dev/vite-plus-core@1.0.0
  • vite-plus@1.0.0
Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:1.0.0 vp build

Run any vp command without installing it; see the Docker guide for more.

v0.3.3: vite-plus v0.3.3: Homebrew setup and workspace dependency fixes

Compare Source

This release fixes Homebrew setup, Windows installation, and workspace dependency commands. It also updates Rolldown, Oxlint, and Oxfmt.

Fixes & Enhancements
  • Homebrew installations complete setup once, retain their bundled CLI, and direct upgrades to brew upgrade vite-plus (#​2729), by @​fengmk2.
  • Windows installations decode remote legacy PowerShell scripts correctly (#​2701), by @​james-elicx.
  • vp migrate removes the unsupported React Refresh allowCompoundComponents option and warns about possible lint errors (#​2702), by @​fengmk2.
  • New monorepo packages use the root lint configuration without a conflicting nested configuration (#​2667), by @​semimikoh.
  • Yarn Classic rejects filtered additions and removals instead of changing unintended dependencies (#​2705), by @​jong-kyung.
  • Yarn Berry rejects unsupported filtered updates and respects filters during recursive removal (#​2709, #​2712), by @​jong-kyung.
  • Yarn and Bun warn when a command does not support --workspace-root. Yarn Classic accepts root additions through vp add and vp install <packages> (#​2713), by @​jong-kyung.
  • vp dedupe warns about unsupported check options (#​2717), by @​jong-kyung.
  • Rust command output respects NO_COLOR (#​2716), by @​liangmiQwQ.
  • Windows commands find lowercase shims in directories with case-sensitive file names (#​2727), by @​fengmk2.
Dependency Updates
  • Update rolldown@1.2.8 to rolldown@1.2.9, oxlint@1.82.0 to oxlint@1.83.0, and oxfmt@0.67.0 to oxfmt@0.68.0. The new lint and format versions can flag code that passed before. Run vp fmt after upgrading if CI runs vp check (#​2725), by @​voidzero-guard[bot].
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.3.0 434e8e9
rolldown 1.2.9 5b4746e
tsdown 0.23.0 npm
vitest 4.1.11 npm
oxlint 1.83.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.68.0 npm
Upgrade
vp upgrade
New Contributors

@​james-elicx

Full Changelog: v0.3.2...v0.3.3

Published Packages
  • @voidzero-dev/vite-plus-core@0.3.3
  • vite-plus@0.3.3
Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.3.3 vp build

Run any vp command without installing it; see the Docker guide for more.

v0.3.2: vite-plus v0.3.2: independent package-manager versions and Oxlint plugin APIs

Compare Source

vp env use now sets each package manager's version independently. This release also adds Oxlint plugin APIs and fixes migration, installation, and template extraction.

Breaking Changes
Package-manager overrides

Direct package-manager commands no longer use VP_PACKAGE_MANAGER. Use the matching version variable in shell profiles, CI jobs, and Dockerfiles:

Previous override for a direct command New override
VP_PACKAGE_MANAGER=npm@<version> VP_NPM_VERSION=<version>
VP_PACKAGE_MANAGER=pnpm@<version> VP_PNPM_VERSION=<version>
VP_PACKAGE_MANAGER=yarn@<version> VP_YARN_VERSION=<version>
VP_PACKAGE_MANAGER=bun@<version> VP_BUN_VERSION=<version>

VP_PACKAGE_MANAGER still selects the manager and version for vp install and related commands. vp env use pnpm@10 now changes only the direct pnpm commands. To override vp install, set VP_PACKAGE_MANAGER explicitly.

The old .session-package-manager file is no longer read or migrated. Run vp env use again to create the new session files. Projects that use only project pins or global defaults need no changes. See the environment guide (#​2658, #​2659), by @​liangmiQwQ.

Installer preferences

VP_NODE_MANAGER now controls only Node.js. Existing installations retain saved preferences during upgrades, so vp upgrade needs no configuration changes. For scripted installations, set VP_PM_MANAGER to apply the same choice to package managers:

Previous combined setting New combined setting
VP_NODE_MANAGER=no VP_NODE_MANAGER=no VP_PM_MANAGER=no
VP_NODE_MANAGER=yes VP_NODE_MANAGER=yes VP_PM_MANAGER=yes

Update installer commands in CI jobs and Dockerfiles. Use VP_NPM_MANAGER, VP_PNPM_MANAGER, VP_YARN_MANAGER, or VP_BUN_MANAGER for individual preferences. The interactive prompt retains its combined choice. See the installer variables guide (#​2681), by @​liangmiQwQ.

Vite DevTools

Projects that install @vitejs/devtools must update its dependency range from ^0.4.0 || ^0.5.0 to ^0.7.1. Projects without this optional dependency need no changes. This requirement comes with the Vite upgrade listed below.

Highlights
  • Installers and vp upgrade share setup behavior across platforms, which simplifies maintenance. The installers retain support for older releases (#​2611), by @​liangmiQwQ.
  • Custom Oxlint rules can import their APIs from vite-plus/lint/plugins and vite-plus/lint/plugins-dev. vp migrate updates supported existing imports (#​2328), by @​fengmk2.
  • vp install and vp add now honor --ignore-scripts for named packages and managed global installations (#​2682), by @​jong-kyung.
Features
  • The bundled tools update from vite@8.2.2 to vite@8.3.0 and from rolldown@1.2.7 to rolldown@1.2.8. They also update from oxlint@1.81.0 to oxlint@1.82.0 and from oxfmt@0.66.0 to oxfmt@0.67.0. The new linter and formatter can flag code that passed before. Run vp fmt after the upgrade if CI runs vp check (#​2670), by @​fengmk2.
Fixes & Enhancements
  • vp create rejects malformed registry versions that could place organization template files outside the cache directory (#​2665), by @​fengmk2.
  • vp env pin updates an active local .nvmrc and preserves its comments. Use --target nvmrc to select this file explicitly (#​2676), by @​ywenhao.
  • vp migrate reports unsupported ESLint rules that it skips, so users can review the missing checks (#​2689), by @​yusuke99.
  • vp migrate imports leftover tsdown configuration when a project already uses Vite+ (#​2646), by @​TheAlexLichter.
  • vp migrate accepts single-line JSON formatter configuration with a final newline (#​2643), by @​TheAlexLichter.
  • vp migrate avoids a redundant playwright dependency when the project already declares @playwright/test (#​2637), by @​yusuke99.
  • Newly scaffolded local generators honor --no-interactive and report missing arguments without prompts. Existing generators need the updated entrypoint (#​2677), by @​SaKaNa-Y.
  • vp upgrade installs its dependencies correctly when the installation directory is inside a pnpm workspace (#​2644), by @​fengmk2.
  • Nested package-manager commands retain the selected Node runtime and package-manager versions (#​2631), by @​lyzno1.
  • Built-in tools reuse the Node executable that starts the CLI. Editor lint and format servers work when node is absent from PATH (#​2673), by @​fengmk2.
  • The npm command wrapper enables Node's compile cache before it loads the CLI, which reduces repeated startup work (#​2648), by @​pablog12.
  • Package-manager commands suppress pnpm, npm, and supported Yarn update notices. Yarn 4 daily tips are also hidden (#​2649, #​2650, #​2651), by @​fengmk2.
  • Invalid package.json errors include the affected file's path (#​2683), by @​adamaveray.
Docs
  • The README task example uses the supported env field (#​2653), by @​SaKaNa-Y.
  • Migration guidance tells pnpm users to retain the generated vite and vitest dependencies (#​2660), by @​naokihaba.
  • Lint and format guides explain root configuration and overrides for monorepos. They clarify that nested configuration is not supported (#​2668), by @​liangmiQwQ.
Chore
Bundled Versions
Tool Version Source
vite 8.3.0 434e8e9
rolldown 1.2.8 9704b56
tsdown 0.23.0 npm
vitest 4.1.11 npm
oxlint 1.82.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.67.0 npm
Upgrade
vp upgrade
New Contributors

@​yusuke99, @​pablog12, @​SaKaNa-Y, @​ywenhao, @​adamaveray

Full Changelog: v0.3.1...v0.3.2

Published Packages
  • @voidzero-dev/vite-plus-core@0.3.2
  • vite-plus@0.3.2
Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.3.2 vp build

Run any vp command without installing it; see the Docker guide for more.

v0.3.1: vite-plus v0.3.1: manage package-manager versions with vp env

Compare Source

vp env now manages Node.js and package-manager versions together. This release also fixes TanStack Start routing and stale Vitest aliases.

Breaking Changes
Package-manager setup

Vite+ replaces Corepack with managed npm, pnpm, yarn, and bun commands. It removes the corepack shim and legacy global package-manager installations (#​2391), by @​liangmiQwQ.

Replace Corepack setup commands in shell profiles, CI jobs, and Dockerfiles:

Previous setup Replacement
corepack enable vp env setup
vp install -g pnpm@<version> vp env default pnpm@<version>
vp install -g yarn@<version> vp env default yarn@<version>
vp install -g bun@<version> vp env default bun@<version>
vp install -g corepack Use the managed package-manager commands directly

Use vp env pin <manager>@<version> to set a project version.

vp env command scope and JSON output

Unscoped vp env commands now operate on Node.js and package managers. Package managers support independent defaults, project pins, session overrides, and installation commands (#​2398), by @​liangmiQwQ.

Add node to limit an operation to Node.js, for example, vp env off node or vp env unpin node. Bare versions, such as vp env default 22.19.0, still select Node.js.

Update scripts that read JSON output:

Command New output structure
vp env current --json node and package_manager objects
vp env list --json, vp env list-remote --json node and package_managers groups

See the environment guide.

vp pack migration to tsdown@0.23

vp pack now uses tsdown@0.23, which removes deprecated options and changes defaults (#​2614), by @​fengmk2.

  1. Run vp migrate to update supported static configurations and package scripts, including projects that already use Vite+.
  2. Check migration warnings in vite.config.*, tsdown.config.*, and package.json.
  3. Update dynamic configurations manually. Arrays built with .map() require manual changes, even when migration reports no warning.
  4. Run vp pack to check the result.
Previous option Replacement
bundle: false unbundle: true
outExtension outExtensions
publicDir / --public-dir copy / --copy
removeNodeProtocol: true nodeProtocol: 'strip'
injectStyle css.inject
inlineOnly / deps.onlyAllowBundle deps.onlyBundle
noExternal deps.alwaysBundle
skipNodeModulesBundle: true / deps.skipNodeModulesBundle: true deps.neverBundle: true
dts.tsgo: true / dts.oxc: true dts.generator: 'tsgo' / dts.generator: 'oxc'

Migration preserves the previous defaults for dependency resolution and ATTW.

tsdown no longer supports Node.js 25. Use Node.js ^22.18.0, ^24.11.0, or >=26.0.0. The programmatic build() API now returns { bundles, watch }.

See the complete migration guide for declaration and TypeScript module-resolution changes.

CLI argument validation

vp staged, vp config, vp hooks, vp migrate, and vp create now reject unsupported options and extra positional arguments (#​2523), by @​fengmk2.

Remove unsupported arguments from scripts. For example, replace vp config --hooks-only with vp config --no-agent.

Highlights
  • Fix TanStack Start HTTP 404 responses caused by separate Vite runtime copies (#​2617), by @​fengmk2.
  • Reduce the Windows vp-shim.exe size from 214 KiB to 14 KiB (#​2466), by @​fengmk2.
  • Add vp check --quiet to hide lint warning diagnostics while retaining errors and summary counts (#​2593), by @​RSS1102.
Features
  • Add vp sync-versions --json so automation can request dependency alignment plans from manifest snapshots without changing project files (#​2600), by @​afonsojramos.
  • Make vp create --git suggest an initial commit command after Git initialization (#​2581), by @​fengmk2.
  • Make vp migrate replace frozen voidzero-dev/setup-vp@v1 workflow references with the supported version pin (#​2540), by @​fengmk2.
  • Upgrade rolldown from 1.2.5 to 1.2.7, tsdown from 0.22.14 to 0.23.0, and Oxc from 0.146.0 to 0.148.0. Upgrade oxlint from 1.79.0 to 1.81.0 and oxfmt from 0.64.0 to 0.66.0. These versions can flag code that passed before. Run vp fmt after upgrading if CI runs vp check (#​2580, #​2613), by @​voidzero-guard[bot].
Fixes & Enhancements
  • Resolve package-manager versions without rewriting package.json. Use vp env pin or vp env unpin to change project declarations explicitly (#​2399), by @​liangmiQwQ.
  • Let vp migrate repair stale vitest aliases that previously prevented the CLI from starting (#​2605), by @​fengmk2.
  • Keep Vite DevTools within the version ranges supported by the bundled Vite (#​2559), by @​fengmk2.
  • Keep automatic Vitest upgrades on the supported 4.x major (#​2612), by @​fengmk2.
  • Remove a deprecated tsdown option from the prompts package build (#​2597), by @​jong-kyung.
Refactor
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.2.2 de1111a
rolldown 1.2.7 26b4c6e
tsdown 0.23.0 npm
vitest 4.1.11 npm
oxlint 1.81.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.66.0 npm
Upgrade
vp upgrade
New Contributors

@​afonsojramos, @​joschuba

Full Changelog: v0.3.0...v0.3.1

Published Packages
  • @voidzero-dev/vite-plus-core@0.3.1
  • vite-plus@0.3.1
Installation

macOS/Linux:

curl -fsSL https://vite.plus | bash

Windows:

irm https://vite.plus/ps1 | iex

Or download and run vp-setup.exe from the assets below.

Docker:

docker run --rm -it -v "$PWD:/app" -w /app ghcr.io/voidzero-dev/vite-plus:0.3.1 vp build

Run any vp command without installing it; see the Docker guide for more.

v0.3.0: vite-plus v0.3.0: XDG install layout, tsup project migration, and Bun 1.4 support

Compare Source

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), 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.

    vp upgrade leaves an existing install where it is. To move one to the split layout, remove it and install again:

    vp implode
unset VP_HOME VP_DATA_DIR VP_BIN_DIR VP_CACHE_DIR
curl -fsSL https://vite.plus | bash

    On Windows, run vp implode, then Remove-Item Env:\VP_HOME, Env:\VP_DATA_DIR, Env:\VP_BIN_DIR, Env:\VP_CACHE_DIR -ErrorAction SilentlyContinue, then irm https://vite.plus/ps1 | iex. Also delete any persistent VP_HOME or VP_*_DIR definition from your shell profile or system environment, because a fresh install still honors them and VP_HOME selects the single-root layout.

    vp implode removes every Vite+ managed Node.js runtime, global package, configuration file, and cache. Stay on your current layout if you would rather not rebuild that state. See Move an existing install to the split directory layout.

Highlights

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Asia/Shanghai)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@github-actions

github-actions Bot commented Oct 8, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

✅ Staging deployment successful!

Preview: https://viteplus-staging.void.app/
Commit: 7cb4561

@renovate
renovate Bot force-pushed the renovate/major-vite+ branch 17 times, most recently from 0932865 to 4ee3978 Compare October 9, 2026 08:36
@renovate
renovate Bot force-pushed the renovate/major-vite+ branch from 4ee3978 to 7cb4561 Compare October 9, 2026 08:42

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants