🚨 [security] Update async: 3.2.1 → 3.2.3 (patch) #96
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ async (3.2.1 → 3.2.3) · Repo · Changelog
Security Advisories 🚨
🚨 Prototype Pollution in async
Release Notes
3.2.3 (from changelog)
3.2.2 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 18 commits:
Version 3.2.3
Update built files
Update changelog for v3.2.3
fix: address edge case in comment stripping (#1780)
chore: remove unused Travis CI config (#1781)
ci: setup GitHub Actions (#1782)
Core: const, let, arrow-fn and unused variables (#1776)
Housekeeping (#1772)
Fix an inefficient regex in autoInject (#1767)
be explicit (#1769)
update docs
Version 3.2.2
Update built files
update changelog for 3.2.2
Fix prototype pollution vulnerability
Fix(docs): use plural `callbacks` word in `lib/map.js` (#1765)
regen docs
update changelog
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