-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update mochawesome to the latest version 🚀 #1
base: master
Are you sure you want to change the base?
Conversation
Version 2.0.1 just got published.Update to this version instead 🚀 CommitsThe new version differs by 7 commits (ahead by 7, behind by 1).
See the full diff. |
Version 2.0.3 just got published. |
Version 2.0.4 just got published.Update to this version instead 🚀 CommitsThe new version differs by 12 commits .
See the full diff. |
Version 2.0.5 just got published.Update to this version instead 🚀 CommitsThe new version differs by 8 commits .
See the full diff. |
Version 2.1.0 just got published.Update to this version instead 🚀 CommitsThe new version differs by 9 commits0.
false See the full diff |
Version 2.2.0 just got published. |
Version 2.2.1 just got published. |
Version 2.3.0 just got published.Update to this version instead 🚀 Release Notes2.3.0See the changelog for release notes |
Version 3.0.0 just got published. |
Version 3.0.1 just got published. |
Version 3.0.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 9 commits.
See the full diff |
|
|
Update to this version instead 🚀 Release Notes for 3.1.2Fixes #276 |
|
|
|
|
|
|
|
Version 2.0.0 of mochawesome just got published.
The version 2.0.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 mochawesome.
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.0.0New Features in 2.0.0
Breaking Changes
Upgrading to v2 should be seamless. However there is one change to be aware of:
reportName
option has been renamed toreportFilename
Commits
The new version differs by 58 commits .
d7c8402
Merge branch 'release/2.0.0'
569f1bd
add gitter badge
0b58c00
update code climate settings
c7c983e
update deps
941be64
update changelog
dd83666
Merge branch 'feature/2.0' into develop
22f4a30
update docs
dbbb9dc
Merge branch 'master' of github.com:adamgruber/mochawesome into develop
f6fd56c
update docs
ff47c8b
bump marge version
f70d5be
add context to test
89423be
more context test cases
091fa8e
Merge branch 'feature/2.0' of github.com:adamgruber/mochawesome into feature/2.0
139020d
update dist
256f8ab
config options; code climate stuff
There are 58 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 🌴