This repository has been archived by the owner on Sep 4, 2020. It is now read-only.
Update jasmine-core to the latest version 馃殌 #109
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
![greenkeeper[bot]](https://avatars.githubusercontent.com/in/505?s=60&v=4){kind=small}
Codecov Report
@@ Coverage Diff @@
## master #109 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 53 53
Lines 779 779
Branches 55 55
=====================================
Hits 779 779Continue to review full report at Codecov.
|
Version 2.6.1 just got published.Update to this version instead 馃殌 Release Notes2.6.1Please see the release notes CommitsThe new version differs by 13 commits0.
false See the full diff |
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 2.6.0 of jasmine-core just got published.
The version 2.6.0 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 jasmine-core.
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
2.6.0Please see the release notes
Commits
The new version differs by 79 commits0.
4b696fbBump version to 2.6.074511f5Merge pull request #1316 from rachelcarmena/update-introduction-url3e912f7Updating introduction url to last version19b83a7Throw a recognizable Error message whenfailoutside of a spec.98569baCache installed gems, so they don't need to be installed every time.7f11ecbMerge branch '1123-custom-error' of https://github.com/deckar01/jasmine into deckar01-1123-custom-error97f8db0Merge branch 'gdborton-afterAll-order'50880fc[lifecycle hooks] Make afterAll hooks operate in the fashion as afterEach.ddcae84Merge branch 'issue-1294' of https://github.com/toubou91/jasmine into toubou91-issue-12949d6a95dMerge pull request #1301 from toubou91/gitignore-update0d3b2b2Added iml files to gitignore08f046cAdded infinity methods, with tests90c8714Expect an undefined error to be passed to the expectation result25d9a39Test that custom matchers can supply custom errorsc42b197Allow the matcher provide a custom error messageThere are 79 commits in total.
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 馃尨