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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update jsdom to the latest version 馃殌 #13132

Merged
merged 2 commits into from Jan 30, 2018
Merged

Conversation

greenkeeper[bot]
Copy link
Contributor

@greenkeeper greenkeeper bot commented Jan 30, 2018

Version 11.6.2 of jsdom was just published.

Dependency jsdom
Current Version 11.6.1
Type devDependency

The version 11.6.2 is not covered by your current version range.

If you don鈥檛 accept this pull request, your project will work just like it did before. However, you might be missing out on a bunch of new features, fixes and/or performance improvements from the dependency update.

It might be worth looking into these changes and trying to get this project onto the latest version of jsdom.

If you have a solid test suite and good coverage, a passing build is a strong indicator that you can take advantage of these changes directly by merging the proposed change into your project. If the build fails or you don鈥檛 have such unconditional trust in your tests, this branch is a great starting point for you to work on the update.


Commits

The new version differs by 4 commits.

  • 1cd4831 Version 11.6.2
  • 71dc01b Update maintainer and repository information
  • f32113b Further fix <style> and <script> evaluation semantics
  • dbda070 Fix <style> and <script> parsing to wait for their close tag

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don鈥檛 help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper bot 馃尨

@googlebot
Copy link

So there's good news and bad news.

馃憤 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

馃槙 The bad news is that it appears that one or more commits were authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this State. It's up to you to confirm consent of the commit author(s) and merge this pull request when appropriate.

@rsimha
Copy link
Contributor

rsimha commented Jan 30, 2018

/to @cramforce

@cramforce cramforce merged commit 5733276 into master Jan 30, 2018
@greenkeeper greenkeeper bot deleted the greenkeeper/jsdom-11.6.2 branch January 30, 2018 04:39
RanAbram pushed a commit to RanAbram/amphtml that referenced this pull request Mar 12, 2018
* chore(package): update jsdom to version 11.6.2

* chore(package): update lockfile

https://npm.im/greenkeeper-lockfile
protonate pushed a commit to protonate/amphtml that referenced this pull request Mar 15, 2018
* chore(package): update jsdom to version 11.6.2

* chore(package): update lockfile

https://npm.im/greenkeeper-lockfile
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.

None yet

4 participants