This repository was archived by the owner on Mar 22, 2023. It is now read-only.
jasmine-immutable-matchers@1.1.0 breaks build 🚨 #100
Closed
Conversation
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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 lovely humans,
jasmine-immutable-matchers just published its new version 1.1.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As jasmine-immutable-matchers 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 💪
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project ✨
You rock!
🌴
The new version differs by 29 commits .
2c724d6Bump version to v1.1.07d8aaddInclude TypeScript declarations, and refresh things a bit1d4f058Merge pull request #30 from unindented/greenkeeper-istanbul-instrumenter-loader-1.0.0552c04bchore(package): update istanbul-instrumenter-loader to version 1.0.07947859Merge pull request #29 from unindented/greenkeeper-karma-chrome-launcher-2.0.010d6e88chore(package): update karma-chrome-launcher to version 2.0.05b5319dMerge pull request #28 from unindented/greenkeeper-karma-1.0.0216a3ffchore(package): update karma to version 1.0.098fa6b2Merge pull request #25 from unindented/greenkeeper-karma-firefox-launcher-1.0.0aa43a34chore(package): update karma-firefox-launcher to version 1.0.010968edMerge pull request #26 from unindented/greenkeeper-karma-opera-launcher-1.0.0d4b32d8chore(package): update karma-opera-launcher to version 1.0.096ef598Merge pull request #22 from unindented/greenkeeper-karma-ie-launcher-1.0.0b6a0436chore(package): update karma-ie-launcher to version 1.0.0526ce0eMerge pull request #24 from unindented/greenkeeper-karma-coverage-1.0.0There are 29 commits in total. See the full diff.
This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? ⚡
greenkeeper upgrade