Update jasmine-core to the latest version 🚀 #62
Closed
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.1 of jasmine-core just got published.
The version 2.6.1 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.1Please see the release notes
Commits
The new version differs by 13 commits0.
2835ca3
Bump version to 2.6.1
120c484
Merge branch 'patch-1' of https://github.com/reinrl/jasmine into reinrl-patch-1
1d62504
Check for
process.listeners
as well, for GlobalErrors055d88e
Merge branch 'UziTech-ensure-function-or-undefined'
d2b33e0
allow undefined as function
0c7f36a
Merge branch 'UziTech-remove-evil'
686d815
remove eval to create spy wrapper
b771c08
No longer try to use
nextTick
since node.js gets upsetfbd2ffc
Build distribution for keys lookup fix
b3c8fb9
Merge branch 'seanparmelee-keys-fix'
ef3cfe7
skip the test when we can’t get the propertyDescriptor
0d6ecbe
iterate through keys with a regular for loop
7e4b8d4
Update README.md
false
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 🌴