Closed greenkeeper[bot] closed 7 years ago
After pinning to 3.1.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Your tests are still failing with this version. Compare the changes 🚨
Version 3.2.0 of eslint-plugin-html just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As eslint-plugin-html is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Status Details
- ❌ **bitHound - Code** 3 failing files. [Details](https://www.bithound.io/github/logan-engineering/limited-10-builder/df881ee46efcb46fae91a95d29226325111891f2/files#filter-failing-file) - ✅ **bitHound - Dependencies** No failing dependencies. [Details](https://www.bithound.io/github/logan-engineering/limited-10-builder/df881ee46efcb46fae91a95d29226325111891f2/dependencies/npm?status=passing)Commits
The new version differs by 9 commits.
fd2465d
3.2.0
ed838d8
chore: update changelog
9db785e
fix: eslint-comments plugin compatibility
03ce563
doc: add a troubleshooting section
de25cbd
feature: ignore the first line of the script tag
e08a9de
chore: format js with prettier
551647c
ci: don't use bash-specific syntax in package scripts
9b960de
chore: drop yarn support
ee6551f
chore: add package-lock.json and upgrade dependencies
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: