Package manager/ecosystem
npm, Javascript
Manifest contents prior to update
Link https://github.com/Lucaslah/InkStatus/pull/40/files
Updated dependency
systeminformation
What you expected to see, versus what you actually saw
It updated systeminformation in the package-lock.json but not in the package.json, I wanted it to update it in my package.json as well.
Images of the diff or a link to the PR, issue or logs
Link to pull request that dependabot opened: https://github.com/Lucaslah/InkStatus/pull/40
Link to package-lock.json https://github.com/Lucaslah/InkStatus/blob/master/package-lock.json
Link to package.json: https://github.com/Lucaslah/InkStatus/blob/master/package.json
You can set the versioning-strategy to increase as per these docs: https://docs.github.com/en/free-pro-team@latest/github/administering-a-repository/configuration-options-for-dependency-updates#versioning-strategy
Ok, I鈥檒l try that out.
It now has been one day since I changed the dependabot.yml file, still no open pull requests to bump systeminformation up to date.
Any ideas?
It now has been one day since I changed the dependabot.yml file, still no open pull requests to bump systeminformation up to date.
Any ideas?
That dependency is already on the latest version (https://www.npmjs.com/package/systeminformation/v/4.27.7) so it cannot/does not need to be updated.
https://github.com/Lucaslah/InkStatus/blob/cb169bc36d38b1cbc1afa2cd79d5efa06bfd6f0c/package.json#L30 shows that in package.json, systeminformation is at 4.27.3 not 4.27.7.
In package-lock.json dependabot updated systeminformation to 4.27.7, but not in my package.json.
The ^4.27.3 means use any version greater than 4.27.3 but smaller than 5.0, the package.lock is what holds the actual version that's being used.
The
^4.27.3means use any version greater than4.27.3but smaller than5.0, thepackage.lockis what holds the actual version that's being used.
Ok, Thanks
I did not know that.