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
What you expected to see, versus what you actually saw
The PR says both packages were updated and that's reflected in the lock file, but it's not reflected in the package.json file where only the first package's version is updated.
There's different automatic versioning strategies for apps & libraries, but I would not expect a widening of a version for a dev dependency which both vitest & tailwindcss are. On top of that, this repo's versioning strategy set to increase which, unless I'm mistaken, means the versions in package.json should always change.
Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
Is there an existing issue for this?
Package ecosystem
npm
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
real repo
minimal repo
dependabot.yml content
real repo
minimal repo
Updated dependency
Both went from 3.0.6 to 3.0.7
Both went from 4.0.0-beta.5 to 4.0.9
What you expected to see, versus what you actually saw
The PR says both packages were updated and that's reflected in the lock file, but it's not reflected in the package.json file where only the first package's version is updated.
There's different automatic versioning strategies for apps & libraries, but I would not expect a widening of a version for a dev dependency which both vitest & tailwindcss are. On top of that, this repo's versioning strategy set to
increase
which, unless I'm mistaken, means the versions in package.json should always change.Native package manager behavior
No response
Images of the diff or a link to the PR, issue, or logs
real repo
minimal repo
Smallest manifest that reproduces the issue
minimal repro with both sets of packages
https://github.com/xt0rted-test/dependabot-verions-not-increasing
The text was updated successfully, but these errors were encountered: