This repository was archived by the owner on Jul 2, 2020. It is now read-only.
Update @springworks/test-harness to the latest version 🚀 #255
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
Author
Version 1.5.6 just got published.Update to this version instead 🚀 Release Notesv1.5.6<a name"1.5.6"> 1.5.6 (2017-04-08)Bug Fixes |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Version 1.5.6 of @springworks/test-harness just got published.
The version 1.5.6 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @springworks/test-harness.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v1.5.6<a name"1.5.6">
1.5.6 (2017-04-08)
Bug Fixes
Commits
The new version differs by 11 commits .
1ff94fefix: use semver caret ranges281bc75fix(package): update should to version 11.2.1cacc3aaMerge pull request #269 from Springworks/greenkeeper/coveralls-2.12.0f9349a5Merge branch 'master' into greenkeeper/coveralls-2.12.07fed3a9chore(package): update eslint to version 3.17.187e7eabchore(package): update coveralls to version 2.12.0ee4c273chore(package): update eslint to version 3.16.1defd4b4chore(package): update eslint to version 3.16.0e4fd18echore(package): update pre-git to version 3.14.0e483fa3chore(package): update pre-git to version 3.13.07435649chore(package): update pre-git to version 3.12.1See 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 🌴