-
Notifications
You must be signed in to change notification settings - Fork 69
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 keytar is breaking the build 🚨 #71
Comments
After pinning to 4.2.1 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results. |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 12 commits.
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 ahead by 7, behind by 1.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 13 commits.
See the full diff |
Your tests are still failing with this version. Compare changes CommitsThe new version differs by 5 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v4.4.2CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v4.5.0
|
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes Release Notes for v4.10.0CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes Release Notes for v4.11.0
CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are still failing with this version. Compare changes |
Your tests are still failing with this version. Compare changes |
The dependency keytar was updated from
4.2.1
to4.3.0
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
keytar 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
Release Notes for v4.3.0
Commits
The new version differs by 24 commits.
581c974
4.3.0
dcb7416
Merge pull request #126 from atom/add-newer-nodes-for-prebuild
86731a9
upgrade prebuild to latest version
f460390
add specific node-abi dependency so we can prebuild against Electron 3
abab53b
add newer node tags to prebuild scripts
e48b67d
Merge pull request #119 from atom/bump-to-use-node-10
da73b19
use Node 10 on CI for testing and packaging
f2d481f
Merge pull request #118 from atom/audit-cleanup
ea93b40
automated npm audit fix
fa18efc
Merge pull request #117 from atom/bump-prebuild-again
c5927ae
some more lockfile updates
84455a0
new prebuild, new life
4447c1a
Merge pull request #115 from atom/upgrade-dependencies
f35f1cb
upgrade prebuild-install to latest version
d31e3ff
migrate away from deprecated mocha flag
There are 24 commits in total.
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 🌴
The text was updated successfully, but these errors were encountered: