You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a pretty vanilla repo with a single package.json, and a single pnpm-lock.yaml (no package-lock.json). Dependabot makes a branch like dependabot/npm_and_yarn/vite-6.3.4 with a lockfile-only update which it claims is bumping vite to the latest version:
One other clue might be the npm_and_yarn in the branch name? I'm not sure if it should use a different branch name when pnpm is the package manager, but from what I can read, it's supposed to be supported now.
The package is using pnpm 9.
Here's the full diff of the original PR dependabot created:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We have a pretty vanilla repo with a single
package.json
, and a singlepnpm-lock.yaml
(nopackage-lock.json
). Dependabot makes a branch likedependabot/npm_and_yarn/vite-6.3.4
with a lockfile-only update which it claims is bumping vite to the latest version:One other clue might be the
npm_and_yarn
in the branch name? I'm not sure if it should use a different branch name when pnpm is the package manager, but from what I can read, it's supposed to be supported now.The package is using pnpm 9.
Here's the full diff of the original PR dependabot created:
If I run
pnpm update vite
, the expected lockfile updates get made. If it matters, this is an indirect, vs. direct, dependency.We are seeing similar issues with other packages.
The lockfile has the following:
Beta Was this translation helpful? Give feedback.
All reactions