-
-
Notifications
You must be signed in to change notification settings - Fork 143
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
chore(deps): update dependency async to 3.2.2 [security] #495
Conversation
A patch level sub-dependency bump under We are seeing the same expected number (2) of test failures, so I think this is okay to be merged? Maybe @confused-Techie can confirm these are the specific same two tests we expect to fail? Again, we should look to see if this dependency is new enough to avoid the issue in our main lite-approve from me ✅, since it presumably does no harm even if |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah I'm on board with approving this PR.
- The failing tests within
settings-view
are exactly what we have failing onmaster
. The same two tests that are disabled over on Disable Failing Tests #477 - The change here is only to the
package-lock.json
which is not used for the actual building of Pulsar as far as I'm aware. It exists only for when building a specific package. - Lastly this bumps the patch version of
async
which already is defined within the package as^3.2.0
which during installation should already be bumped to the highest patch version possible, meaning we should be getting this fix in Pulsar already.
So with that said, this PR essentially does nothing but ensure that when someone is developing the settings-view
package, they are free of this concern. But otherwise anyone on a recent version of Pulsar (e.g. 1.104.0) already should be
Thanks for confirming these are the same failing tests as on
Looks like we are getting an even newer version, 3.2.4, in the main app: Lines 2264 to 2267 in 868f569
(Though there are also older versions floating around as dependencies of some other packages somewhere in the mix. But not anything I would want to spend the time to get into right about now, personally speaking.) |
With @DeeDeeG's lite approval, and my approval, and lack of real change for end users I'm gonna go ahead and merge this one. |
This PR contains the following updates:
3.2.0
->3.2.2
GitHub Vulnerability Alerts
CVE-2021-43138
A vulnerability exists in Async through 3.2.1 for 3.x and through 2.6.3 for 2.x (fixed in 3.2.2 and 2.6.4), which could let a malicious user obtain privileges via the
mapValues()
method.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.