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

fix: update jasmine-reporters to v2.5.0 to fix xmldom vulnerability #2994

Merged
merged 1 commit into from
Oct 1, 2021

Conversation

wcalandro
Copy link
Contributor

PR Checklist

Please check if your PR fulfills the following requirements:

  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

N/A

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature (please, look at the "Scope of the project" section in the README.md file)
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Currently, @bazel/jasmine uses a version of jasmine-reporters that has a downstream vulnerability in xmldom

What is the new behavior?

jasmine-reporters has been updated, which uses @xmldom/xmldom, which has the vulnerability patched

Does this PR introduce a breaking change?

  • Yes
  • No

Copy link
Collaborator

@alexeagle alexeagle left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks!

@alexeagle alexeagle merged commit 8ca234b into bazel-contrib:stable Oct 1, 2021
@wcalandro wcalandro deleted the fix-jasmine branch October 4, 2021 17:40
alexeagle added a commit that referenced this pull request Oct 5, 2021
…bility (#2994)"

It broke our Windows CI

This reverts commit 8ca234b.
@alexeagle
Copy link
Collaborator

oops sorry @wcalandro this made our Windows CI tests go solid red
https://buildkite.com/bazel/rules-nodejs-nodejs/builds/10692#1ce7f7b0-619a-4737-aab0-bb2e1aa03776

I reverted the commit for now to get green again. Do you have time to open the PR again and try to diagnose why it broke?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants