Skip to content

Update Vite packages - #765

Closed
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vite-packages
Closed

Update Vite packages#765
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/vite-packages

Conversation

@renovate

@renovate renovate Bot commented Jun 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@tailwindcss/vite (source) 4.3.1 → 4.3.3 age confidence
vite (source) 0.1.24 → 0.2.7 age confidence
vite (source) 8.0.16 → 8.2.0 age confidence
vite-plus (source) 0.1.24 → 0.2.7 age confidence

Release Notes

tailwindlabs/tailwindcss (@​tailwindcss/vite)

v4.3.3

Compare Source

Fixed
  • Support --watch --poll[=ms] in @tailwindcss/cli when filesystem events are unreliable or unavailable (#​20297)
  • Canonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white) (#​20298)
  • Prevent Preflight from overriding Firefox's native iframe:focus-visible outline styles (#​20292)
  • Ensure theme('colors.foo') in JS plugins resolves correctly when both --color-foo and --color-foo-bar exist (#​20299)
  • Ensure fractional opacity modifiers work with named shadow sizes like shadow-sm/12.5, text-shadow-sm/12.5, drop-shadow-sm/12.5, and inset-shadow-sm/12.5 (#​20302)
  • Parse selectors like [data-foo]div as two selectors instead of one (#​20303)
  • Ensure @tailwindcss/postcss rebuilds when a preprocessor like Sass changes the input CSS without changing the input file on disk (#​20310)
  • Ensure CSS nesting is handled even when Lightning CSS isn't run, such as in @tailwindcss/browser and Tailwind Play (#​20124)
  • Prevent achromatic theme colors from shifting hue when mixed in polar color spaces like oklch (#​20314)
  • Ensure --spacing(0) is optimized to 0px instead of 0 so it remains a <length> when used in calc(…) (#​20319)
  • Load @parcel/watcher only when needed in @tailwindcss/cli --watch mode, so one-off builds and --watch --poll work when @parcel/watcher can't be loaded (#​20325)
  • Use explicit platform fonts instead of system-ui and ui-sans-serif so CJK text respects the page's lang attribute on Windows (#​20318)
  • Prevent @tailwindcss/upgrade from rewriting ignored files when run from a subdirectory (#​20329)
  • Ensure earlier @source rules pointing to nested files are scanned when later @source rules point to files in parent folders (#​20335)
  • Prevent @tailwindcss/vite from triggering full page reloads when scanned files are processed by Vite but haven't been loaded as modules yet (#​20336)

v4.3.2

Compare Source

Fixed
  • Support bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16) (#​20229)
  • Prevent @tailwindcss/cli in --watch mode from crashing on Windows when @source points to a directory that doesn't exist (#​20242)
  • Prevent @tailwindcss/vite from crashing in Deno v2.8.x when context.parentURL is not a valid URL (#​20245)
  • Ensure @tailwindcss/cli in --watch mode rebuilds when the input CSS file changes in an ignored directory (#​20246)
  • Allow @variant rules used in addBase(…) to use custom variants defined later (#​20247)
  • Prevent @tailwindcss/vite from crashing during HMR when scanned files or directories are deleted (#​20259)
  • Generate font-size instead of color declarations for text-[--spacing(…)] (#​20260)
  • Prevent @source patterns from scanning unrelated sibling files and folders (#​20263)
  • Extract class candidates adjacent to Template Toolkit delimiters like %]…[% in .tt, .tt2, and .tx files (#​20269)
  • Extract class candidates from conditional Maud syntax like p.text-black[condition] (#​20269)
  • Prevent @position-try rules from triggering unknown at-rule warnings when optimizing CSS (#​20277)
  • Support class suggestions for named opacity modifiers from --opacity theme values (#​20287)
  • Prevent type errors in @tailwindcss/postcss when used with newer PostCSS patch releases (#​20289)
voidzero-dev/vite-plus (vite)

v0.2.7: vite-plus v0.2.7: Clearer guidance for built-in commands and scripts

Compare Source

This release points users to vpr <name> when a Vite+ built-in command and package script share a name, adds concurrency control to vp pack, and smooths migrations and package-manager setup.

Highlights
  • Point users to vpr <name> when a Vite+ built-in command and package.json script share a name (#​2259, #​2262, #​2265, vite-task#570), by @​wan9chi
  • Add --concurrency to vp pack to limit parallel Rolldown builds, and update tsdown 0.22.13 -> 0.22.14 and Vite DevTools 0.4.2 -> 0.4.5 (#​2233), by @​voidzero-guard[bot]
  • Add read-only Svelte rune globals to migrated Oxlint overrides, preventing false no-undef errors (#​2192), by @​naokihaba
  • Install package managers from npm tarballs with nonstandard top-level directories, fixing Yarn 1.22.19 installation (#​2264), by @​TheAlexLichter
Fixes & Enhancements
  • Prevent the Oxc language server from crashing when contributors open the Vite+ workspace in VS Code (#​2245), by @​jong-kyung
Docs
  • Document the full procedure for removing Vite+ commit hooks (#​2218), by @​TheAlexLichter
  • Document per-process and per-machine ways to disable Vite+ commit hooks without uninstalling them (#​2230), by @​TheAlexLichter
  • Clarify when to use built-in vp commands versus package scripts through vp run or vpr, including migration and agent guidance (#​2255), by @​wan9chi
  • Document GitLab CI/CD setup with the reusable setup-vp template (#​2258), by @​naokihaba
Chore
  • Run Semgrep security scans on pull requests and pushes to main (#​2223), by @​Boshen
  • Re-enable Vitest browser-mode CLI snapshot coverage on every supported platform (#​2275), by @​wan9chi
  • Stabilize Windows CLI snapshot tests for interrupted installs and browser port fallback (#​2282), by @​wan9chi
  • Replace deprecated shared JavaScript and TypeScript VS Code settings with their current js/ts.* names (#​2246), by @​jong-kyung
Bundled Versions
Tool Version Source
vite 8.1.5 5e7fe12
rolldown 1.2.0 03e1e34
tsdown 0.22.14 npm
vitest 4.1.10 npm
oxlint 1.75.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.60.0 npm
Upgrade
vp upgrade

Full Changelog: voidzero-dev/vite-plus@v0.2.6...v0.2.7

Published Packages
  • @voidzero-dev/vite-plus-core@0.2.7
  • vite-plus@0.2.7
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.

View the full commit: c17e1c3

Docker:

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

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

v0.2.6: vite-plus v0.2.6: Stable type-aware linting and more reliable task caching

Compare Source

This release moves Vite+'s type-aware linting to the stable tsgolint 7 engine, updates the bundled build and formatting tools, strengthens vp run caching and workspace discovery, and removes the redundant vp build startup banner.

Highlights
  • Move bundled type-aware linting to stable tsgolint 7, and update Vite 8.1.4 -> 8.1.5, Rolldown 1.1.5 -> 1.2.0, tsdown 0.22.7 -> 0.22.13, Oxlint 1.73.0 -> 1.75.0, oxlint-tsgolint 0.24.0 -> 7.0.2001, and Oxfmt 0.58.0 -> 0.60.0 (#​2214), by @​voidzero-guard[bot]
  • Improve vp run reliability by caching much larger automatically tracked input sets, discovering npm workspaces whose patterns start with ./, and providing more accurate error messages (vite-task#554, vite-task#547, vite-task#552, #​2215), by @​wan9chi and @​liangmiQwQ
  • Remove the redundant Vite startup banner from vp build output and fail fast when upstream Vite changes invalidate Vite+ branding patches (#​2200, #​2205), by @​liangmiQwQ
Refactor
Docs
  • Fix broken documentation anchors and add Migration Rules to the Migrate sidebar (#​2203), by @​charpeni
Chore
  • Stabilize vp create build-approval snapshots by removing package-age timing from those fixtures (#​2224), by @​wan9chi
  • Remove the temporary release workflow dispatch used for the previous release (#​2193), by @​wan9chi
  • Share package-manager fixtures across CLI tests (#​2197), by @​jong-kyung
  • Remove stale raw Oxlint and Oxfmt development dependencies that bypassed repository editor configuration (#​2187), by @​liangmiQwQ
Bundled Versions
Tool Version Source
vite 8.1.5 5e7fe12
rolldown 1.2.0 03e1e34
tsdown 0.22.13 npm
vitest 4.1.10 npm
oxlint 1.75.0 npm
oxlint-tsgolint 7.0.2001 npm
oxfmt 0.60.0 npm
Upgrade
vp upgrade
New Contributors

Welcome @​charpeni.

Full Changelog: voidzero-dev/vite-plus@v0.2.5...v0.2.6

Published Packages
  • @voidzero-dev/vite-plus-core@0.2.6
  • vite-plus@0.2.6
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.

View the full commit: cd064c6

Docker:

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

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

v0.2.5: vite-plus v0.2.5: Cleaner environments and more reliable workflows

Compare Source

This release adds cleanup and package version commands, supports TypeScript 7 declaration generation, reduces the standalone binary size, and hardens task tracking, CLI output, package-manager routing, Docker workflows, and project scaffolding.

Highlights
Fixes & Enhancements
  • Reduce standalone vp binary sizes by about 5% on Linux and macOS and 19% on Windows (#​2043), by @​fengmk2
  • Keep the Docker image non-root by default while allowing passwordless sudo for Playwright browser dependencies and system packages (#​2088), by @​fengmk2
  • Ignore .env and .env.* in generated projects while keeping .env.example trackable (#​2095), by @​forehalo
  • Create vp-use.cmd after the Windows environment bin directory is ready and document its Command Prompt-only usage (#​2128), by @​liangmiQwQ
  • Render user-facing process statuses and paths without Rust debug wrappers (#​2130), by @​liangmiQwQ
  • Make vp dedupe fall back to yarn install with a warning on Yarn Classic (#​2139), by @​jong-kyung
  • Ensure package-manager child processes, including Bun, can always find the managed Node.js runtime (#​2158), by @​BlankParticle
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.1.4 a477454
rolldown 1.1.5 f09947a
tsdown 0.22.7 npm
vitest 4.1.10 npm
oxlint 1.73.0 npm
oxlint-tsgolint 0.24.0 npm
oxfmt 0.58.0 npm
Upgrade
vp upgrade
New Contributors

Welcome @​yukinoshi and @​BlankParticle.

Full Changelog: voidzero-dev/vite-plus@v0.2.4...v0.2.5

Published Packages
  • @voidzero-dev/vite-plus-core@0.2.5
  • vite-plus@0.2.5
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.

View the full commit: 93dc59a

Docker:

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

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

v0.2.4: vite-plus v0.2.4: Vitest security hotfix

Compare Source

This hotfix updates the bundled Vitest Browser Mode packages to 4.1.10, which includes the fix for GHSA-p63j-vcc4-9vmv. The advisory is critical and affects @vitest/browser <=4.1.9.

Highlights
  • Critical Vitest Browser Mode advisory fixed: bundled vitest and @vitest/browser* move from 4.1.9 to 4.1.10, addressing GHSA-p63j-vcc4-9vmv, where provider commands could bypass the file access permission gate (#​2089), by @​voidzero-guard[bot]
Chore
  • Add the standard release-manager skill for vite-plus release operations (#​2019), by @​fengmk2
Bundled Versions
Tool Version Source
vite 8.1.3 578ffb8
rolldown 1.1.4 6cbd233
tsdown 0.22.3 npm
vitest 4.1.10 npm
oxlint 1.72.0 npm
oxlint-tsgolint 0.24.0 npm
oxfmt 0.57.0 npm
Upgrade
vp upgrade
New Contributors

No new contributors in this release.

Full Changelog: voidzero-dev/vite-plus@v0.2.3...v0.2.4

Published Packages
  • @voidzero-dev/vite-plus-core@0.2.4
  • vite-plus@0.2.4
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.2.4 vp build

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

v0.2.3: vite-plus v0.2.3: config extraction, create, and vp run reliability fixes

Compare Source

A patch release that fixes static config extraction for vite.config.ts files whose defineConfig comes from a preset or custom wrapper (no longer misread as Vite+'s own), fixes vp create for org templates on registries that strip custom package fields, cleans up terminal output after Ctrl-C during vp run, and updates bundled Vite to 8.1.3.

Highlights
  • Custom VP_HOME is honored on every run: the global vp now respects a user-set VP_HOME for its home directory instead of falling back to ~/.vite-plus, and persists it in the generated env files, so a custom install location no longer produces multiple instances or unusable packages (#​2029), by @​liangmiQwQ
Features
  • Upgrade bundled Vite from 8.1.2 to 8.1.3 (inlined CSS after the shebang line, CSS preload for nested dynamic imports, SSR stacktrace column fix) (#​2042), by @​voidzero-guard[bot]
Fixes & Enhancements
  • vp run no longer misreads a vite.config.ts when its defineConfig comes from a preset or a custom wrapper instead of vite-plus or vite. Such configs are now evaluated at runtime rather than assumed to be Vite+'s own, so projects that use them no longer wrongly report Task "build" not found (#​2060, #​2075), by @​liangmiQwQ and @​fengmk2
  • Killing a vp run task with Ctrl-C no longer leaves odd OSC escape sequences in the terminal; vp defers its own Ctrl-C handling until the child process exits (#​2079), by @​forehalo
  • vp migrate: rewriting a package.json prettier script now emits a single --check, so scripts that combined --check with --list-different / -l / -c no longer produce a duplicated vp fmt --check --check (#​2044), by @​shulaoda
  • vp create @&#8203;org:name: read the org template catalog (createConfig) from the published tarball when the registry (e.g. GitHub Packages) strips custom fields from packument metadata (#​2063), by @​hiro-daikin
  • vp run: missing env vars requested through @voidzero-dev/vite-task-client now return undefined instead of null, preserving Vite production NODE_ENV semantics when builds run through vp run (vite-task#508, via #​2076), by @​wan9chi
Refactor
  • static_config: drop the unreachable vite.config.json branch (#​2045), and remove unused exported CLI helpers (#​2046), by @​shulaoda
Docs
Chore
Bundled Versions
Tool Version Source
vite 8.1.3 578ffb8
rolldown 1.1.4 6cbd233
tsdown 0.22.3 npm
vitest 4.1.9 npm
oxlint 1.72.0 npm
oxlint-tsgolint 0.24.0 npm
oxfmt 0.57.0 npm
Upgrade
vp upgrade
New Contributors

@​wan-kong and @​hiro-daikin made their first contributions.

Full Changelog: voidzero-dev/vite-plus@v0.2.2...v0.2.3

Published Packages
  • @voidzero-dev/vite-plus-core@0.2.3
  • vite-plus@0.2.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.2.3 vp build

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

v0.2.2: vite-plus v0.2.2: Vite+ Beta

Compare Source

Vite+ is now in Beta: stable and ready for production adoption, fully open source under MIT. Read the announcement to see what Vite+ is about and where it is headed: Announcing Vite+ Beta.

On top of the Beta milestone, this release brings cross-version upgrades via vp migrate, an official Docker toolchain image on GHCR, zero-config runner-aware vp build caching, and PGP-verified managed Node.js downloads.

Highlights
  • vp migrate upgrades existing Vite+ projects across versions: previous release notes told users not to run vp migrate for upgrades. It now runs from the global CLI when the local one is older, re-pins vite-plus and the vite -> @voidzero-dev/vite-plus-core alias across dependencies, overrides/resolutions, and catalogs in every workspace package, aligns vitest / @vitest/* by actual usage, and defaults to a version-only upgrade (pass --full to also run the first-time setup bucket: hooks, editor, agent files, lint migration) (#​1891), by @​fengmk2
  • Official Vite+ Docker toolchain image: ghcr.io/voidzero-dev/vite-plus bundles vp plus a native build toolchain on debian:bookworm-slim (amd64/arm64, non-root). Since vp provisions the exact Node.js from .node-version, one image builds any project, and a documented multi-stage build copies the resolved Node.js into a small vp-free runtime stage (#​1944), by @​fengmk2
  • Zero-config vp build caching via runner-aware Vite: Vite reports its inputs, outputs, and tracked env reads to the vp runner over the new @voidzero-dev/vite-task-client IPC (vite#22453), so vp build caches correctly with no hand-written cache config: outputs are tracked and restored automatically, and a changed VITE_* env var invalidates the cache and is named in the cache-miss message (#​1774), by @​wan9chi
  • PGP-verified Node.js downloads: installing a managed Node.js now verifies the release's clearsigned SHASUMS256.txt.asc against the vendored Node.js release keyring (pure Rust, no gpg required) before trusting any checksum, so a tampered archive is rejected before install; unsigned sources (musl builds, custom mirrors) fall back to checksum-only verification (#​1848), by @​fengmk2
Features
  • vp check: a check block in vite.config.ts (check.fmt / check.lint) can make plain vp check skip formatting or linting by default, mirroring --no-fmt / --no-lint; standalone vp fmt / vp lint and git hooks are unaffected, and a note: line keeps the config-based skip discoverable (#​1981), by @​fengmk2
  • vp env list-remote: highlight installed versions (color, or a * prefix when piped) and label the project-resolved current and global default versions; --json gains installed / current / default fields (#​1907), by @​semimikoh
  • vpr ships as a vite-plus package bin, so the vp run shorthand works on clean installs without global PATH shims (Vercel build image, generic CI runners) (#​1988), by @​kvnwolf
  • Vite Task: dependsOn can select tasks from dependency packages, e.g. dependsOn: [{ "task": "build", "from": "dependencies" }] (vite-task#479), by @​wan9chi
  • Vite Task: a task's env / untrackedEnv glob patterns support ! negation (e.g. ["VITE_*", "!VITE_SECRET"]) (vite-task#425), and an env-caused cache miss now names the variable inline, e.g. cache miss: env 'NODE_ENV' changed (vite-task#438), by @​wan9chi
  • Upgrade upstream dependencies: vite 8.0.16 -> 8.1.2, rolldown 1.1.1 -> 1.1.4, oxlint 1.70.0 -> 1.72.0, oxfmt 0.55.0 -> 0.57.0, oxlint-tsgolint 0.23.0 -> 0.24.0, and the oxc toolchain 0.136.0 -> 0.138.0 (#​1924, #​1989, #​2000, #​2009), by @​voidzero-guard[bot]
Fixes & Enhancements
  • Windows: vp run no longer hangs CI when a node_modules/.bin .cmd shim is routed through PowerShell; the npm/pnpm/yarn .ps1 wrappers read stdin and block forever on a non-TTY pipe, so the PowerShell rewrite is now skipped when stdin is not an interactive terminal (vite-task#491, via #​1973), by @​fengmk2
  • Vite Task: the task cache is stored in a per-schema-version directory (e.g. node_modules/.vite/task-cache/v13/), so switching between branches that pin different Vite+ versions no longer fails with Unrecognized database version (vite-task#433), by @​fengmk2
  • Vite Task: env values in cache fingerprints are stored only as SHA-256 digests and env cache-miss details report names without values (vite-task#455); prefix env assignments like PATH=... command now affect executable lookup during planning (vite-task#440); package.json / pnpm-workspace.yaml files with a UTF-8 BOM parse correctly (vite-task#424), by @​wan9chi
  • vp upgrade: run the pinned pnpm with a managed Node.js LTS directly instead of re-entering vp install, so an incompatible session/project/system runtime can no longer make pnpm skip optional native binaries and leave the upgraded CLI broken (#​1900), by @​liangmiQwQ
  • Global package installs: each install writes to an immutable packages/<name>#<uuid> prefix that is activated via metadata after npm succeeds, so an interrupted reinstall can no longer leave the active package unavailable (#​1906), and stale interrupted-install directories are swept with file-lock protection for concurrent installs (#​1945), by @​liangmiQwQ
  • lazyPlugins(): skip plugin factories only while config metadata is being resolved instead of keying off VP_COMMAND, so builds spawned under vp run / vp exec keep the user's plugins and vp format no longer loads them (#​1939), by @​fengmk2
  • vp migrate (pnpm): add a direct vite devDep aliased to the core override wherever vite-plus is depended on, so vitest's vite peer binds to @voidzero-dev/vite-plus-core instead of pulling in a second upstream vite that broke the vp test cache (#​1933), by @​fengmk2
  • vp pack: bundle @tsdown/exe and @tsdown/css into core so --exe and CSS bundling work without a resolvable top-level tsdown; the native lightningcss becomes an optional peer loaded lazily with an actionable error (#​1919), by @​fengmk2
  • vp env: invalidate stale shim resolve cache entries when the project's Node.js version source changes (#​1951), by @​jong-kyung
  • Node shim: when the project declares npm via packageManager / devEngines.packageManager, child processes spawned from node resolve the managed npm instead of the Node-bundled one (#​1938); vp env which reports bins linked by an intercepted npm install -g (e.g. tsc) instead of "not found" (#​1968); bins with uppercase names (e.g. vitePlus) dispatch correctly (#​1963), by @​liangmiQwQ
  • vp-setup: pass the configured npm registry to the inner pnpm install so setup works behind custom registries (#​1795), by @​daflyinbed
  • Native binding: declare the platform packages' true ABI floor engines.node >=20.0.0 so engine-strict package managers (pnpm) no longer skip the optional native dependency and fail with Cannot find native binding when a consumer's Node floor lands in a product-policy gap (#​1993), by @​fengmk2
  • vp create: run git init without creating an initial commit, so commitlint-configured templates no longer reject the hardcoded message and template placeholders are not baked into history (#​2008), by @​forehalo
  • vp staged --debug: inline the bundled lint-staged version so debug logging no longer crashes reading a package.json that does not exist in the bundle (#​1925), by @​rokuosan
  • Installer: retry downloads truncated mid-body in HttpClient::get_bytes (the platform-tarball path for vp upgrade and the standalone installer) (#​1940), and clean up the temp dir when a package-manager install fails instead of leaking .tmpXXXX directories (#​1949), by @​shulaoda
  • Windows/msys: normalize backslashes in the env.fish fallback path (#​1954), by @​Aalivexy
  • install.ps1: detect the missing VC++ runtime (0xC0000135) and print VC++ Redistributable guidance instead of a generic failure; interactive irm | iex installs keep the shell open (#​1962), by @​cheezone
  • vp migrate: preserve comments, key order, and trailing commas in existing .vscode / .zed JSONC configs by patching the original text instead of re-serializing it (#​1956), by @​fengmk2
  • Migration: link the git hook warning to the migration guide (#​1902), by @​naokihaba
  • vp info / vp view: use package-manager-native commands (pnpm view, bun info, yarn npm info) instead of routing every lookup through npm view (#​1895), by @​jong-kyung
  • Correct overused ErrorConfig error types across the codebase (#​1934), by @​liangmiQwQ
Refactor
Docs
  • Document Vite Task automatic tracking (fs tracking and cache-reporting tools), reusing the task cache with GitHub Actions cache, and dependsOn: [{ task, from: "dependencies" }] (#​1992), by @​wan9chi
  • Rewrite the "Upgrading Vite+" guide: preview builds install through the registry bridge as ordinary 0.0.0-commit.<sha> npm versions, and vp migrate is the recommended way to upgrade a project or move it onto a preview build (#​1965), by @​fengmk2
  • Describe how to switch back to the release version from nightly (#​1887), by @​situ2001
  • Clarify Git hook tool migration (#​1901), by @​naokihaba
  • Add a global installation explanation (#​1915), update the vp env help output (#​1969), and add liangmiQwQ as a team member ([#​1911](https:/

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "after 10pm every weekday,before 6am every weekday"
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 17, 2026 •
edited
Loading

Copy link
Copy Markdown

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Updated (UTC)
❌ Deployment failed
View logs		 vuefes-japan-speakers de63b7e Jul 31 2026, 09:04 AM

@renovate
renovate Bot force-pushed the renovate/vite-packages branch 2 times, most recently from 24d9413 to 860e328 Compare June 18, 2026 18:47
@renovate renovate Bot changed the title Update Vite packages to v0.2.0 Update Vite packages to v0.2.1 Jun 18, 2026
@renovate
renovate Bot force-pushed the renovate/vite-packages branch 4 times, most recently from e71a4b0 to b986117 Compare June 23, 2026 12:54
@renovate renovate Bot changed the title Update Vite packages to v0.2.1 Update Vite packages Jun 23, 2026
@renovate
renovate Bot force-pushed the renovate/vite-packages branch 9 times, most recently from a120570 to 853b967 Compare June 30, 2026 13:03
@renovate
renovate Bot force-pushed the renovate/vite-packages branch 10 times, most recently from 8210d8d to 819871b Compare July 7, 2026 17:32
@renovate
renovate Bot force-pushed the renovate/vite-packages branch 8 times, most recently from 61e44da to 6d30121 Compare July 16, 2026 05:11
@renovate
renovate Bot force-pushed the renovate/vite-packages branch 11 times, most recently from 30e9f8b to 9bc0f8b Compare July 23, 2026 09:32
@renovate
renovate Bot force-pushed the renovate/vite-packages branch 7 times, most recently from 656a508 to 8c3ba3e Compare July 30, 2026 15:58
@renovate
renovate Bot force-pushed the renovate/vite-packages branch from 8c3ba3e to de63b7e Compare July 31, 2026 09:03
@yamanoku yamanoku closed this Aug 2, 2026
@yamanoku
yamanoku deleted the renovate/vite-packages branch August 2, 2026 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

@yamanoku yamanoku

Labels

dependencies

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@yamanoku