| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Lockfile updates currently fail because the gitignored sibling clones (rolldown/, vite/) are not present in Renovate's worktree but are referenced by pnpm-workspace.yaml (patches) and Cargo.toml (path member). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
✅ Deploy Preview for viteplus-preview canceled.
|
Sorry, something went wrong.
…list (#1744) ## Why Since #1536, `.github/renovate.json` disabled **all** npm and cargo updates, so nothing gets updated and security alerts persist. The disable was a workaround for lockfile refresh failing (the vendored `vite/` and `rolldown/` dirs that lockfiles depend on are gitignored). ## What Replace the blanket disable with a targeted ignore-list, keeping everything else enabled: - **Ignored npm** (managed upstream): `rolldown`, `oxc-*`, `@oxc-node/*`, `@oxc-project/*`, `@vitejs/devtools`, `oxfmt`, `oxlint`, `oxlint-tsgolint`, `tsdown`, `vite`, `vitest`, `vitest-dev`. - **Ignored cargo**: `oxc` crates and the vite-task git deps (`fspy`, `vite_glob`, `vite_path`, `vite_powershell`, `vite_str`, `vite_task`, `vite_workspace`). - **Everything else** updates again, so security alerts get remediation PRs. ## Note Lockfile refresh still can't succeed in Renovate (vendored dirs are gitignored), but that no longer blocks the PR: Renovate opens it with an "Artifact update problem" note, and the lockfile is regenerated manually (`just init && pnpm install` / `cargo update`) before merge.
| Back | FazBrowse Home | New Git URL |
Renovate bot cannot process npm and cargo due to our clone repo approach.