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 tape is breaking the build 🚨 #26

Open
greenkeeper bot opened this issue Dec 16, 2019 · 4 comments
Open

An in-range update of tape is breaking the build 🚨 #26

greenkeeper bot opened this issue Dec 16, 2019 · 4 comments

Comments

@greenkeeper
Copy link
Contributor

greenkeeper bot commented Dec 16, 2019

The devDependency tape was updated from 4.11.0 to 4.12.0.

🚨 View failing branch.

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

tape 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).

Commits

The new version differs by 9 commits.

  • 42c84d6 v4.12.0
  • 3e0a341 [Deps] update is-regex, string.prototype.trim
  • ba7e2b2 [Dev Deps] update eslint
  • f3a5925 [Tests] use shared travis-ci configs
  • 6e94800 [Deps] update deep-equal, glob, object-inspect, resolve, string.prototype.trim
  • 8150c3b [Refactor] use is-regex instead of instanceof RegExp
  • 24487cb add tap-nyc to pretty-reporters
  • c283615 [New] when the error type is wrong, show the message and stack
  • 44cbbf5 [Tests] add a test for the wrong kind of error

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 16, 2019

After pinning to 4.11.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Dec 24, 2019

  • The devDependency tape was updated from 4.12.0 to 4.12.1.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 4 commits.

  • 25bcbc6 v4.12.1
  • 9094271 [Fix] error stack file path can contain parens/spaces
  • b765bba [Deps] update resolve
  • 949781f [Dev Deps] update eslint

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Jan 8, 2020

  • The devDependency tape was updated from 4.12.1 to 4.13.0.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 6 commits.

  • 1fba54a v4.13.0
  • e0e2542 [New] tape binary: Add -i flag to ignore files from gitignore (#492)
  • 0f15085 [Deps] update resolve
  • 0330d82 [New] add t.match() and t.doesNotMatch(), new in node v13.6
  • 21ac403 [Tests] handle stack trace variation in node <= 0.8
  • d7c2fd3 [lint] fix object key spacing

See the full diff

@greenkeeper
Copy link
Contributor Author

greenkeeper bot commented Mar 2, 2020

  • The devDependency tape was updated from 4.13.0 to 4.13.2.

Your tests are still failing with this version. Compare changes

Commits

The new version differs by 9 commits.

  • 2914a7b v4.13.2
  • c4119c2 [patch] Print name of test that didnt end (#498)
  • 98b2695 [Tests] sync new test cases from master
  • d686aa2 [eslint] enable quotes rule
  • 4526b39 [Tests] add tests for edge cases and numerics
  • 398503c [Deps] update resolve
  • e6b6f11 [Refactor] remove unused code
  • 333c636 v4.13.1
  • 8af61fd [Fix] match/doesNotMatch: when passing, ensure the proper default assert message shows up

See the full diff

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