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 node-polyglot is breaking the build 🚨 #645

Open
greenkeeper bot opened this issue Jun 21, 2019 · 1 comment
Open

An in-range update of node-polyglot is breaking the build 🚨 #645

greenkeeper bot opened this issue Jun 21, 2019 · 1 comment

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Jun 21, 2019

The dependency node-polyglot was updated from 2.3.0 to 2.3.1.

🚨 View failing branch.

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

node-polyglot 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).

Commits

The new version differs by 11 commits.

  • 8187877 v2.3.1
  • 2526b26 [Tests] on node v12, v11, v10
  • cdd920e [Dev Deps] update chai, eslint, eslint-config-airbnb-base, eslint-plugin-import, safe-publish-latest, uglify-js
  • f05f4ff [Deps] update warning
  • 6c4faa1 [Performance] Remove unnecessary dollar signs replacement
  • 9e2dcf2 Remove unnecessary dollar signs replacement
  • 7002784 [Docs] fix typo in the Czech example
  • 423c90a Merge pull request #119 from bullgare/patch-1
  • 0fdafb5 [Tests] add additional tests
  • 5d66e94 Fixes plurals for russian when number is greater than 100
  • 623b9ea [Docs] update docs HTML

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 Jun 21, 2019

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