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 html-minifier is breaking the build 🚨 #25

Open
greenkeeper bot opened this issue Oct 25, 2018 · 1 comment
Open

An in-range update of html-minifier is breaking the build 🚨 #25

greenkeeper bot opened this issue Oct 25, 2018 · 1 comment

Comments

@greenkeeper
Copy link

greenkeeper bot commented Oct 25, 2018

The devDependency html-minifier was updated from 3.5.20 to 3.5.21.

🚨 View failing branch.

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

html-minifier 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).

Commits

The new version differs by 11 commits.

  • 5494091 Version 3.5.21
  • c6ecb90 Support <!doctypehtml> in the parser
  • c3f5168 Update build
  • f625991 Merge pull request #970 from mathiasbynens/doctype
  • cf55c51 Merge pull request #965 from mathiasbynens/fix-ampersand
  • 7e8406e Use <!doctypehtml> (without the space) where possible
  • 9b0c7cc Prevent data loss when using decodeEntities
  • df720b3 handle clean-css errors correctly (#955)
  • dcb6941 fix STDIN handling of CLI (#956)
  • 1f8df44 fix --minify-urls in CLI (#957)
  • 2d34ad5 Update README.md (#954)

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 Oct 25, 2018

After pinning to 3.5.20 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