-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgraded dependency exists in yarn resolutions but is different version #1792
Comments
What was the "before" value for that dependency in |
Original value of the package: {
"dependencies": {
"@scope/package": "~2.23.0"
}
} The change proposed by Renovate pull request:
The resolution remains the same: {
"resolutions": {
"@scope/package": "2.23.1"
}
} The -"@scope/[email protected]", "@scope/package@^2.0.0", "@scope/package@^2.15.0", "@scope/package@^2.19.0", "@scope/package@^2.21.1", "@scope/package@^2.7.1", "@scope/package@~2.23.0":
+"@scope/[email protected]", "@scope/package@^2.0.0", "@scope/package@^2.15.0", "@scope/package@^2.19.0", "@scope/package@^2.21.1", "@scope/package@^2.7.1":
version "2.23.1"
dependencies:
@@ -554,6 +554,16 @@
+"@scope/package@~2.25.0":
+ version "2.25.0"
+ dependencies: Sorry for the obfuscation for the package name. |
what do you suggest the new resolution version should be? 2.25.0 as per the locked version? |
When you specify a package like Therefore, the owner of the application may have intended for their application to use the latest version of In that case, Renovate is working as expected. In our particular case, however, our application intended for their application, and all their transitive dependencies, to use the same version of In our case, our application no longer needs the resolution (they are in the process of upgrading past a patch they really needed to use), so our need for a resolution to this scenario no longer exists. I will close out the issue (We can always re-open if the use case arises again). |
This is a:
I'm using:
Please describe the issue:
An on-premise Renovate App instance is emitting a
WARN
log with the following message -Upgraded dependency exists in yarn resolutions but is different version
In the repository being renovated, the
package.json
file contains a resolution for a dependency.Renovate has just filed a pull request to update that dependency, but has only updated the
dependency
list, and not the resolution.Since Renovate is emitting a warning, I'm wondering what I should be doing. This does seem like maybe an issue that the repository owner will need to address. Can Renovate address it for them? Or should Renovate ask them to address it through a PR comment? Or... it this not really an actionable issue?
The text was updated successfully, but these errors were encountered: