yeoman-assert@2.2.0 breaks build 🚨 #10
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Coverage remained the same at 14.407% when pulling 8a1d47ece32233ded3e789db59ea56847f1e4a23 on greenkeeper-yeoman-assert-2.2.0 into c85b6a2 on master. |
fossamagna
force-pushed
the
greenkeeper-yeoman-assert-2.2.0
branch
from
8a1d47e
to
97a069f
Compare
|
Coverage remained the same at 14.407% when pulling 97a069fe0a422d77b49ddf17b7685051b7453a08 on greenkeeper-yeoman-assert-2.2.0 into ddb2aaf on master. |
fossamagna
force-pushed
the
greenkeeper-yeoman-assert-2.2.0
branch
from
97a069f
to
603620e
Compare
|
Coverage remained the same at 14.407% when pulling 603620edb9e316ac0b98939259b325346d02ba63 on greenkeeper-yeoman-assert-2.2.0 into 234c6ce on master. |
fossamagna
force-pushed
the
greenkeeper-yeoman-assert-2.2.0
branch
from
603620e
to
39434b5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello 👋
🚨🚨🚨
yeoman-assert just published its new version 2.2.0, which is covered by your current version range. After updating it in your project the build went from success to failure.
This means your software is now malfunctioning, because of this update. Use this branch to work on adaptions and fixes.
Happy fixing and merging 🌴
GitHub Release
assert.noObjectContent()andassert.noJsonFileContent()The new version differs by 21 commits .
66718392.2.04db399eAdd assert.noObjectContent() and assert.noJsonFileContent() (#16)aa6a7272.1.25d4e4c8Merge pull request #14 from kierans/master859d0ddFixes yeoman/yeoman-assert#13dd0f355Update for jsonFileContent6f008f2Merge pull request #9 from zckrs/use-generator-node53998b0Apply generator-node to manage library31092e22.1.1a525655Merge pull request #8 from yeoman/jsonFileContent3ac566fUsingjsonFileContentinstead.8edcd5aMerge pull request #7 from johnnyicarus/patch-1cddd36aFix typos345e140Update readme588d3072.1.0There are 21 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? Upgrade to the supporter plan! You'll also get your pull requests faster ⚡It keeps your software up to date, all the time.