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 dot is breaking the build 🚨 #511

Open
greenkeeper bot opened this issue Dec 7, 2019 · 1 comment
Open

An in-range update of dot is breaking the build 🚨 #511

greenkeeper bot opened this issue Dec 7, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 7, 2019

The dependency dot was updated from 1.1.2 to 1.1.3.

🚨 View failing branch.

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

dot is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.1.3

Tests for doT.process
Patch code injection via prototype pollution (#291)

Commits

The new version differs by 12 commits.

  • 6adbd81 docs: note
  • d00300e 1.1.3
  • 87ccef3 test: update travis versions
  • 4cc3253 chore: update dependencies
  • 320e847 test: missing test files
  • ef5f353 docs: security considerations
  • c531369 test: exclude unused code from coverage
  • b4fd211 test: doT.process
  • fa3890d test: use doT required via the main module
  • 2cf2226 fix: prevent possibility of execution of the code injected via prototype pollution when undefined is passed to compiled template function, closes #291
  • 299b4da Merge pull request #237 from EdwardBetts/spelling
  • 2dfe1af correct spelling mistake

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
Contributor Author

greenkeeper bot commented Dec 7, 2019

After pinning to 1.1.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