Skip to content
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

Merged
merged 1 commit into from
Apr 20, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 18, 2023

Mend Renovate

This PR contains the following updates:

Package Change
async 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@DeeDeeG
Copy link
Member

DeeDeeG commented Apr 18, 2023

A patch level sub-dependency bump under packages/settings-view. Shouldn't cause any issues.

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 yarn.lock, since I do not believe this package-lock.json is actually read when building the actual Pulsar app. Only if cding and locally npm installing in the packages/settings-view dir.


lite-approve from me ✅, since it presumably does no harm even if yarn will be ignoring this lockfile when actually building Pulsar. Would be willing to officially approve if I get a chance to verify the two failing tests are the same ones as on master branch.

Copy link
Member

@confused-Techie confused-Techie left a 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 on master. 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

@DeeDeeG
Copy link
Member

DeeDeeG commented Apr 18, 2023

Thanks for confirming these are the same failing tests as on master branch. 👍

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.

Looks like we are getting an even newer version, 3.2.4, in the main app:

pulsar/yarn.lock

Lines 2264 to 2267 in 868f569

async@3.2.4, async@^3.2.0, async@^3.2.3:
version "3.2.4"
resolved "https://registry.yarnpkg.com/async/-/async-3.2.4.tgz#2d22e00f8cddeb5fde5dd33522b56d1cf569a81c"
integrity sha512-iAB+JbDEGXhyIUavoDl9WP/Jj106Kz9DEn1DPgYw5ruDn0e3Wgi3sKFm55sASdGBNOQB8F59d9qQ7deqrHA8wQ==

(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.)

@renovate renovate bot changed the title fix(deps): update dependency async to v3.2.2 [security] chore(deps): update dependency async to 3.2.2 [security] Apr 18, 2023
@confused-Techie
Copy link
Member

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.

@confused-Techie confused-Techie merged commit 7dd09bd into master Apr 20, 2023
@renovate renovate bot deleted the renovate/npm-async-vulnerability branch April 20, 2023 19:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants