🚨 [security] Upgrade loader-utils: 1.2.3 → 3.2.0 (major) #66
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
🚨 Your current dependencies have known security vulnerabilities 🚨
This dependency update fixes known security vulnerabilities. Please see the details below and assess their impact carefully. We recommend to merge and deploy this as soon as possible!
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ loader-utils (1.2.3 → 3.2.0) · Repo · Changelog
Security Advisories 🚨
🚨 Prototype pollution in webpack loader-utils
Release Notes
3.2.0
3.1.3
3.1.2
3.1.1
3.1.0
3.0.0
2.0.3
2.0.2
2.0.0
1.4.0
1.3.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 44 commits:
chore(release): 3.2.0chore(deps): update (#200)feat: hash uniformity for base digestschore(release): 3.1.3fix: crash with md4 hash (#198)chore(release): 3.1.2fix: bug with unicode characters (#196)chore(release): 3.1.1fix: base64 and unicode charactersdocs: update (#194)chore(release): 3.1.0feat: added `md4` (wasm version) and `md4-native` (`crypto` module version) algorithmsdocs: fix readmechore(release): 3.0.0fix: allow `interpolateName` works without optionstest: fixrefactor!: use `xxhash64` by default for `[hash]`/`[contenthash]` and `getHashDigest` APIrefactor!: added `isUrlRequest` again, but now it ignores only absolute URLs and `#hash` requests, `data URI` and root relative request are handled as requestable due webpack v5 support themchore: deps updaterefactor!: `parseString` was removed in favor `new URLSearchParams(loaderContext.resourceQuery.slice(1))` where `loaderContext` is `this` in loader functionrefactor!: `parseString` was removed in favor `JSON.parse`ci: fix name of github actionrefactor!: `stringifyRequest` was removed in favor `JSON.stringify(loaderContext.utils.contextify(this.context, request))` where `loaderContext` is `this` inside loader function, also it will be cachable and fasterrefactor!: `isUrlRequest` was removed, webpack since version v5 supports absolute data URI/URLs/paths, anyway if you don't want to handle absolute URLs you can handle it on `loader` side using `/^[a-z][a-z0-9+.-]*:/i.test(url)` regexprefactor!: `[emoji]` was removed without replacements, please use custom function if you need thischore!: minimum supported Node.js verison is `12.13.0`refactor!: remove `getOptions` in favor `loaderContext.getOptions` (`loaderContext` is `this` inside loader function), note - special query parameters like `?something=true` is not supported, if you need this please do it on `loader` side, but we strongly recommend avoid it, as alternative you can use `?something=1` and handle `1` as `true` in `loader`refactor!: remove `getRemainingRequest` in favor `loaderContext.remainingRequest` (`loaderContext` is `this` inside loader function)refactor!: remove `getCurrentRequest` in favor `loaderContext.currentRequest` (`loaderContext` is `this` inside loader function)ci: updatechore(deps): updatechore(deps): updatechore(release): 2.0.0refactor: switch to `md4` by default (#168)refactor: the `getOptions` method returns empty object on empty query (#167)chore: minimum required `Node.js` version is `8.9.0` (#166)chore: upgrade json5 to fix a vulnerability (#165)chore(release): 1.4.0feat: the `resourceQuery` is passed to the `interpolateName` method (#163)chore(release): 1.3.0feat: support the `[query]` template for the `interpolatedName` method (#162)chore: funding.yml config and CI fix (#159)Set up CI with Azure Pipelinesdocs: small grammar change (#144)👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
depfu/.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands