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

deps(snyk): update snyk snapshot #7392

Merged
merged 1 commit into from
Mar 11, 2019
Merged

deps(snyk): update snyk snapshot #7392

merged 1 commit into from
Mar 11, 2019

Conversation

snyk-bot
Copy link
Contributor

@snyk-bot snyk-bot commented Mar 6, 2019

Why this PR?

a weekly update of the vulnerabilities snapshot for lighthouse

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

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

will need to sort out test failures

@@ -58,7 +58,7 @@
],
"jquery":[
{"id":"npm:jquery:20160529","severity":"low","semver":{"vulnerable":["=3.0.0-rc.1"]}},
{"id":"npm:jquery:20150627","severity":"medium","semver":{"vulnerable":["<3.0.0-beta1 >1.12.3 || <1.12.0 >=1.4.0"]}},
{"id":"npm:jquery:20150627","severity":"medium","semver":{"vulnerable":["<1.12.2",">=1.12.3 <2.2.2",">=2.2.3 <3.0.0"]}},
Copy link
Collaborator

Choose a reason for hiding this comment

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

I'm not a semver parsing expert, but our sample artifacts changed because our jquery 2.1.1 inclusion changed. Shouldn't it not have changed ?

Before
✅ 2.1.1 < 3.0.0-beta1
✅ 2.1.1 > 1.12.3

After
✅ 2.1.1 < 2.2.2
✅ 2.1.1 >= 1.12.3

🤔

Copy link
Member

@paulirish paulirish Mar 6, 2019

Choose a reason for hiding this comment

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

looks like we got a bug :/

image

i'll put up a fix

edit: fix is up at #7402

Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

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

looks good after the fix in #7402

@patrickhulce patrickhulce merged commit 3a8b59c into GoogleChrome:master Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants