Skip to content

chore(deps): plan Vite 8.x upgrade #381

Description

@oaslananka

Goal

Plan the Vite 8.x major dependency upgrade without bundling it into unrelated maintenance PRs.

Current state

  • Current version: ^6.5.0\ (managed by Renovate)
  • Target version: ^8.0.0\
  • Depends on vitepress supporting Vite 8.x

Upstream status (verified 2026-08-02)

  • Stable VitePress is 1.6.4 and still depends on Vite ^5.4.14.
  • The VitePress next channel is 2.0.0-alpha.18 and depends on Vite ^8.1.3.
  • The stable documentation toolchain therefore does not yet support Vite 8. The upgrade remains intentionally blocked; an alpha VitePress migration is out of scope for routine dependency maintenance.

Risk

  • Breaking API changes in Vite 8.x
  • vitepress compatibility with Vite 8.x
  • Build/dev bundle changes
  • CI matrix compatibility
  • No runtime impact (Vite is dev-only, not shipped in VSIX)

Validation required

  • \pnpm install --frozen-lockfile\
  • \pnpm run typecheck\
  • \pnpm run lint\
  • \pnpm run test\
  • \pnpm run build\
  • \pnpm run check\
  • CI matrix (all platforms)

Notes

  • Blocked on a stable VitePress release compatible with Vite 8.x.
  • Do not approve the Renovate vite-8.x branch while compatibility requires an alpha VitePress line.
  • Re-verify the stable VitePress dependency range before creating the migration PR.
  • Requires Renovate Dashboard approval only after the blocker is cleared.

Out of scope

  • Unrelated dependency upgrades
  • Release/publish changes
  • Weakening CI or security checks
  • Changing KiCad support policy
  • Moving MCP server implementation into this repo

Acceptance criteria

  • Migration notes reviewed
  • Minimal code changes identified
  • Full validation green
  • Rollback path documented

Activity

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

Metadata

Metadata

Labels

area:dxDeveloper experience and local workflowsdependenciesDependency update pull requestsdependency-lifecycleDependency update policy, canary tests, and version lifecycle managementpriority:P2Medium-priority scheduled workproduct:repoRepository-wide governance, CI, release, and documentationrisk:highMajor, runtime, protocol, security, or compatibility-sensitive dependency updatetype:taskOperational or maintenance task

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions