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

An in-range update of parse5 is breaking the build 🚨 #508

Open
greenkeeper bot opened this issue Nov 5, 2017 · 1 comment
Open

An in-range update of parse5 is breaking the build 🚨 #508

greenkeeper bot opened this issue Nov 5, 2017 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Nov 5, 2017

Version 3.0.3 of parse5 was just published.

Branch Build failing 🚨
Dependency parse5
Current Version 3.0.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

parse5 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes v3.0.3

Changelog: http://inikulin.github.io/parse5/#3-0-3

Commits

The new version differs by 14 commits.

  • 723d782 v3.0.3
  • 8d38fda Merge pull request #212 from gfx/patch-1
  • 89e6b04 loosen the dependency version of @types/node
  • fee4018 Merge pull request #207 from inikulin/escape-zero-char
  • 67f0099 Escape NUL character in feedback tests
  • 2aff591 Merge pull request #198 from stevenvachon/master
  • 02d9fee Improve location info documentation
  • ae7b8a0 Merge pull request #196 from stevenvachon/master
  • d0769db Fix empty stream parsing with ParserStream (closes #195)
  • fabc6d8 Bring no-trailing-spaces eslint rule back
  • d9c0881 Merge pull request #186 from HTMLParseErrorWG/master
  • ed932c8 Calculate offset in position tracker
  • c7f1193 Refactor location info parser mixin
  • 549218b Refactor location info tokenizer mixin

See the full diff

FAQ and help

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


Your Greenkeeper Bot 🌴

@greenkeeper
Copy link
Author

greenkeeper bot commented Nov 5, 2017

After pinning to 3.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

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

No branches or pull requests

0 participants