This repository was archived by the owner on Feb 21, 2020. It is now read-only.
Open
Conversation
Author
Version 1.7.0 just got published.Update to this version instead 🚀 Release Notesv1.7.0Bug Fixes
Features
CommitsThe new version differs by 11 commits0.
false See the full diff |
Author
Version 1.7.1 just got published. |
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.
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.6.0 of karma just got published.
The version 1.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 karma.
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.6.0Bug Fixes
Features
Commits
The new version differs by 33 commits .
03958cechore: release v1.6.0af32d0cchore: update contributors2685e13fix(middleware): does not work with mootools (#2591)3263c06Merge pull request #2639 from twolfson/dev/better.launch.fail.errors.sqwished17c2c43fix(reporter): keep users exact formatError resultdb9682cMerge pull request #2642 from maksimr/chore-file-list-tests332ac4bMerge pull request #2643 from maksimr/chore-remove-pending-testsb1de55fMerge pull request #2620 from chriscasola/fix/file-cache74bfdf3fix(file-list): always use file from first matcher83a6be2chore: remove skipped tests85a1769chore: Remove unhandled rejection Error from unit testsbcfac8aMerge pull request #2641 from chriscasola/fix/test-line-nums67d1cfechore: ensure test failures show correct line number7d33398feat(launcher): output stderr for failing launchersde55bc6Merge pull request #2637 from maksimr/issue-2192There are 33 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 🌴