-
Notifications
You must be signed in to change notification settings - Fork 3
An in-range update of luxon is breaking the build 🚨 #147
Comments
After pinning to 1.8.0 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 |
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 17 commits.
There are 17 commits in total. See the full diff |
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 CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 6 commits.
See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 CommitsThe new version differs by 24 commits.
There are 24 commits in total. See the full diff |
Your tests are passing again with this update. Explicitly upgrade to this version 🚀 |
The dependency luxon was updated from
1.8.0
to1.8.1
.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
luxon 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
Commits
The new version differs by 3 commits ahead by 3, behind by 1.
93a8fdc
rereleasing as 1.8.1
f38823e
bump to 1.8.0
af1c686
Add support for Unix timestamps in seconds. (#371)
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: