Front: upgrade outdated sub-dependencies #182
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I do not know how to test that. At least it still builds :D
We still have @quasar/cli's dependencies, but those are too ancient to be upgraded it seems.
@quasar/cli is in version 1.3.2 (up to date)
download-git-repo is in version 3.0.2 (up to date)
download is in version 7.1.0 (most recent 7.x release) ; most recent version does not fix the vulnerability
got is in version 8.3.1 but patch is in version 11.8.5
The only meaningful thing we can do is upgrade got to version 11.8.5, but I'm afraid the jump from version 8.3.1 might contain breaking change.
update-notifier is in version 5.1.0 (most recent 5.x release) ; first version that fixes the vuln is 6.0.1
latest-version is in version 5.1.0 (most recent 5.x release) ; first version that fixes the vuln is 7.0.0
package-json is in version 6.3.0 ; first version that fixes the vuln is 8.0.0
got is in version 9.6.0 but patch is in version 11.8.5
Same comment as above. Maybe we can have more luck with the other dependencies.
There is nothing to do. Good luck with that.