Bump vite-task git dependency to the latest main commit. Use when you need to update the vite-task crates (fspy, vite_glob, vite_path, vite_str, vite_task, vite_workspace) in vite-plus.
Update the vite-task git dependency in Cargo.toml to the latest commit on the vite-task main branch, fix any breaking changes, and create a PR.
Cargo.toml and find the current rev = "..." for any vite-task git dependency (e.g., vite_task, vite_path, fspy, vite_glob, vite_str, vite_workspace). They all share the same revision.git ls-remote https://github.com/voidzero-dev/vite-task.git refs/heads/main
Cargo.toml. There are 6 crate entries that reference the same vite-task revision: fspy, vite_glob, vite_path, vite_str, vite_task, vite_workspace.cargo check requires the ./rolldown and ./vite directories to exist (many workspace path dependencies point to ./rolldown/crates/...).packages/tools/.upstream-versions.json..github/actions/clone action.cargo check to ensure the new vite-task compiles without errors.cargo test -p vite_command -p vite_error -p vite_install -p vite_js_runtime -p vite_migration -p vite_shared -p vite_static_config -p vite-plus-cli -p vite_global_cli to run the vite-plus crate tests.vite_install::package_manager tests, vite_global_cli::commands::env tests). These may fail in sandboxed environments. Verify they also fail on the main branch before dismissing them.cargo test -p vite_task will NOT work because vite_task is a git dependency, not a workspace member.vite-task changes often affect CLI output, which means snap tests need updating. Common output changes:
vp run that show up in help outputTo update snap tests:
Snap test files are at packages/cli/snap-tests/*/snap.txt and packages/cli/snap-tests-global/*/snap.txt.
CHANGELOG.md diff between old and new commits to see what changed:
https://raw.githubusercontent.com/voidzero-dev/vite-task/<new-hash>/CHANGELOG.md
docs/ (e.g., docs/guide/, docs/config/).docs/config/run.md, docs/config/build.md)docs/guide/cache.md)chore: bump vite-task to <short-hash>chore: bump vite-task to <short-hash>https://github.com/voidzero-dev/vite-task/compare/<old-hash>...<new-hash>#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed
Wait for CI and ensure the done check passes. Key checks to monitor:
The only required status check for merging is done, which aggregates the other checks (excluding Cargo Deny).
pnpm bootstrap-cli) requires the rolldown Node.js package to be built first, which is complex. Prefer relying on CI for snap test generation.Cargo.lock is automatically updated by cargo when you change the revision in Cargo.toml.