An in-range update of release is breaking the build π¨
greenkeeper opened this issue Β· 1 comments
greenkeeper commented
Version 1.1.6 of release just got published.
Branch | Build failing π¨ |
---|---|
Dependency | release |
Current Version | 1.1.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As release 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
Release Notes
1.1.6Patches
Commits
The new version differs by 5 commits .
c6531ce
1.1.6
f6aeb20
Only require LTS version of Node
b5555a3
Moved core of package to binary
27663a6
Use
bluebird
instead of async/await9790b06
Don't add bots to credits
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 π΄
greenkeeper commented
Version 1.1.7 just got published.
Your tests are still failing with this version. Compare the changes π¨
Release Notes
1.1.7Patches
- Lowercased text files: f7e40f2
- Pinned dependencies: 39f3fd5
- Run tests before committing: 2874970
- Unneeded XO rules removed: 11afddd
- Fixed authentication flow: f35994f
- Better message for checking authentication: af61f4d
- Load
async-to-gen
properly: f79e66e - Updated dependencies to latest version: 3d0ee25
Commits
The new version differs by 9 commits .
e855628
1.1.7
3d0ee25
Updated dependencies to latest version
f79e66e
Load
async-to-gen
properlyaf61f4d
Better message for checking authentication
f35994f
Fixed authentication flow
11afddd
Unneeded XO rules removed
2874970
Run tests before committing
39f3fd5
Pinned dependencies
f7e40f2
Lowercased text files
See the full diff.