-
Notifications
You must be signed in to change notification settings - Fork 4
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 🚨 #24
Comments
After pinning to 4.7.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Version 4.9.0 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 27 commits.
There are 27 commits in total. See the full diff |
Version 4.9.1 just got published.Your tests are still failing with this version. Compare the changes 🚨 CommitsThe new version differs by 10 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 11 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 60 commits.
There are 60 commits in total. See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 7 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v4.11.0CommitsThe new version differs by 8 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 9 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Version 4.8.0 of tape just got published.
This version is covered by your current version range and after updating it in your project the build failed.
As tape 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 💪
Status Details
Commits
The new version differs by 4 commits.
342c89a
v4.8.0
c82c593
[Dev Deps] update
js-yaml
b50084c
[Deps] update
resolve
,object-inspect
bd6db7b
updates README.md and adds tap-html
See the full diff
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
The text was updated successfully, but these errors were encountered: