An in-range update of standard-version is breaking the build π¨
greenkeeper opened this issue Β· 2 comments
Version 4.3.0 of standard-version was just published.
Branch | Build failing π¨ |
---|---|
Dependency | standard-version |
Current Version | 4.2.0 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
standard-version 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
Commits
The new version differs by 8 commits.
9a99607
chore(release): 4.3.0
4fd3bc2
feat: do not update/commit files in .gitignore (#230)
c5e1ee2
feat: publish only if commit+push succeed (#229)
45fcad5
feat(format-commit-message): support multiple %s in the message
b37bc66
test(format-commit-message): add failing test cases
3fdd7fa
fix: use the
skip
default value for skip cli arg (#211)709dae1
fix: recommend
--tag
prerelease for npm publish of prereleases (#196)958daf4
chore: add link to community slack (#202)
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 4.2.0 your tests are passing again. Downgrade this dependency π.
The failed test run was due to a situational network problem. No need to downgrade the dependency.