greenkeeper[bot]
commented
6 years ago After pinning to 1.4.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Open greenkeeper[bot] opened 6 years ago
greenkeeper[bot]
commented
6 years ago After pinning to 1.4.4 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
greenkeeper[bot]
commented
6 years ago Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 18 commits.
1612518 1.6.0253499b docs(CHANGELOG): add CHANGELOG for 1.6.0b36e80e Merge pull request #109 from power-assert-js/es20189027c48 chore: apply minimal set of transforms as possible9544bdc chore: disable .babelrc lookup for independence006637d chore: farewell PhantomJS (cont'd)9226f07 chore: set embedAst to false to test embedded parser53a3ae8 chore: update package-lock.json9aceab1 chore: update dependencies to ensure ES2018 support1f40b8e test: rename tests since it's not only ES68eb797b chore: farewell PhantomJS45f63eb test: testing ES2018 syntax0439759 chore(travis): drop Node4 due to its EOL2035a6f chore(travis): update CI settings since Node10 has been released52445bd Merge pull request #105 from falsandtru/travisThere are 18 commits in total.
See the full diff
greenkeeper[bot]
commented
6 years ago Your tests are still failing with this version. Compare the changes 🚨
The new version differs by 8 commits.
e549955 1.6.163043bc docs: add CHANGELOG for 1.6.1389e525 chore(travis): drop Node9 from CI8bd962e chore: update package-lock.json04ff9fd chore: update empower to ^1.3.176af2b7 chore: avoid concatenating undefined170892e chore: fix failing tests due to the change in assertion message since Node v10.7.09455634 test: Object Rest/Spread in assertion expressionSee the full diff
☝️ Greenkeeper’s updated Terms of Service will come into effect on April 6th, 2018.
Version 1.5.0 of power-assert was just published.
This version is covered by your current version range and after updating it in your project the build failed.
power-assert 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 failed [Details](https://travis-ci.org/imaya/zlib.js/builds/360141501?utm_source=github_status&utm_medium=notification)Commits
The new version differs by 27 commits.
140c4311.5.0bcbc5b0docs(CHANGELOG): add CHANGELOG for 1.5.0795c2c2docs(README): refer to "strict mode" document2d388c1docs(README): add Jest to "KNOWN TO WORK" list0d24c6echore: update copyright yeare3b4e62Merge pull request #104 from power-assert-js/assert-strict-mode41b3feafix:strictproperty of strict mode assert should also be an empowered one12b0d1ftest: structural compatibility between strict mode and legacy mode8f194a0feat:strictmode assert function should also havestrictproperty92b5ee7refactor: prefer nativestrictimplementationfa2df87feat:strictmode assert should also be a function9f86bc6feat: support "Strict mode"c4e49c5chore(travis): add Node9, remove Node7, update EOL of LTSf9ca847docs(README): pull API section upe5d43afdocs(README): link to Node Assert API docsThere are 27 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: