An in-range update of js-joda-timezone is breaking the build π¨
greenkeeper opened this issue Β· 1 comments
The devDependency js-joda-timezone was updated from 2.0.2
to 2.0.3
.
π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
js-joda-timezone 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 17 commits.
b4bc9d0
Bump package version
43d5e44
Add HowTo
1c8876e
Merge remote-tracking branch 'origin/master'
3945d60
Add PR number
98d9aa1
Merge pull request #74 from js-joda/greenkeeper/eslint-6.0.0
a7b030d
chore(package): update lockfile package-lock.json
7af3018
chore(package): update eslint to version 6.0.0
2b1df89
Merge pull request #73 from JKillian/smaller-builds
46c66c5
fix karma conf
2a2844e
try to check in the correct packaage-lock.json
cc96c44
lint
ac7b27f
add a little bit of readme info
69bd0d3
clean up
a3ade7a
Add TypeScript typings
271a1dd
check-in dist files
There are 17 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 π΄
After pinning to 2.0.2 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.