Skip to content
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

v6.0.0-0 changelog #3614

Closed
wants to merge 10 commits into from
Closed

v6.0.0-0 changelog #3614

wants to merge 10 commits into from

Conversation

boneskull
Copy link
Member

This is everything going in so far for the prerelease, which will be v6.0.0-0 and published as with the next tag, i.e., npm install mocha@next.

I went ahead and pulled in remark, because by far the most tedious part of this process is hand-editing the links. That's also prone to screwups. I chose to eliminate the references and just use inline links, because since it's now automated, it's less of a pain to deal with.

scripts/linkify-changelog.js is the implementation.

I also made this script part of the version npm lifecycle script.

@boneskull boneskull added area: documentation anything involving docs or mochajs.org semver-patch implementation requires increase of "patch" version number; "bug fixes" labels Dec 13, 2018
@boneskull boneskull added this to the v6.0.0 milestone Dec 13, 2018
@boneskull
Copy link
Member Author

I evidently rebased poorly.

@boneskull
Copy link
Member Author

If you want any other PR to make it in, please assign it to the v6.0.0 milestone.

I'm hoping not to add anything that isn't a bug fix before the final v6.0.0 release... sound fair? @mochajs/core

@coveralls
Copy link

coveralls commented Dec 14, 2018

Coverage Status

Coverage remained the same at 90.536% when pulling eff10ff on v6.0.0-changelog into ee6d576 on master.

@boneskull boneskull force-pushed the v6.0.0-changelog branch 3 times, most recently from 89c74ef to 5fc92bd Compare December 19, 2018 18:42

- `--extension` is now an alias for `--watch-extensions` and affects _non-watch-mode_ test runs as well. For example, to run _only_ `test/*.coffee` (not `test/*.js`), you can do `mocha --require coffee-script/register --extensions coffee`.

- [#3352](https://github.com/mochajs/mocha/issues/3352): `tap` reporter is now TAP13-capable ([**@plroebuck**](https://github.com/plroebuck))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be #3552 and should also credit @mollstam

- `--compilers` is no longer supported; attempting to use will cause Mocha to fail with a link to more information
- `-d` is no longer an alias for `--debug`; `-d` is currently ignored
- [#3275](https://github.com/mochajs/mocha/issues/3275): `--watch-extensions` no longer implies `js`; it must be explicitly added ([**@TheDancingCode**](https://github.com/TheDancingCode))
- [#2908](https://github.com/mochajs/mocha/issues/2908): `tap` reporter emits error messages ([**@chrmod**](https://github.com/chrmod))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

emits thrown error messages


## :bug: Fixes

- [#3346]: Exit correctly from `before` hooks when using `--bail` ([@outsideris])
- [#3356](https://github.com/mochajs/mocha/issues/3356): `--no-timeouts` and `--timeout 0` now does what you'd expect ([**@boneskull**](https://github.com/boneskull))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Incorrect issue#. #3556?

- [#2095](https://github.com/mochajs/mocha/issues/2095), [#3521](https://github.com/mochajs/mocha/issues/3521): Do not log `stdout:` prefix in browser console ([**@Bamieh**](https://github.com/Bamieh))
- [#3595](https://github.com/mochajs/mocha/issues/3595): Fix mochajs.org deployment problems ([**@papandreou**](https://github.com/papandreou))
- [#3518](https://github.com/mochajs/mocha/issues/3518): Improve `utils.isPromise()` ([**@fabiosantoscode**](https://github.com/fabiosantoscode))
- [#3320](https://github.com/mochajs/mocha/issues/3320): Fail gracefully when non-extensible objects are thrown in async tests ([**@fargies**](https://github.com/fargies))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is both @plroebuck and @fargies.


## :book: Documentation

- [#3328]: Mocha-flavored [API docs](https://mochajs.org/api/)! ([@Munter])
- [#3525](https://github.com/mochajs/mocha/issues/3525): Improvements to `.github/CONTRIBUTING.md` ([**@markowsiak**](https://github.com/markowsiak))
- [#3466](https://github.com/mochajs/mocha/issues/3466): Update description of `slow` option ([**@finfin**](https://github.com/finfin))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is both @plroebuck and @finfin

- [#2095](https://github.com/mochajs/mocha/issues/2095), [#3521](https://github.com/mochajs/mocha/issues/3521): Do not log `stdout:` prefix in browser console ([**@Bamieh**](https://github.com/Bamieh))
- [#3595](https://github.com/mochajs/mocha/issues/3595): Fix mochajs.org deployment problems ([**@papandreou**](https://github.com/papandreou))
- [#3518](https://github.com/mochajs/mocha/issues/3518): Improve `utils.isPromise()` ([**@fabiosantoscode**](https://github.com/fabiosantoscode))
- [#3320](https://github.com/mochajs/mocha/issues/3320): Fail gracefully when non-extensible objects are thrown in async tests ([**@fargies**](https://github.com/fargies))
Copy link
Contributor

@plroebuck plroebuck Dec 19, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[#3532](https://github.com/mochajs/mocha/issues/3532): Refactored JSONStream reporter to be consistent with output stream usage.

@plroebuck
Copy link
Contributor

Still waiting on @sindresorhus to review chalk/supports-color#90; assuming he accepts and we bump that dependency afterwards, it will close longstanding issue #1304.

- [#3375]: Add support for comments in `mocha.opts` ([@plroebuck])
Enhancements introduced in [#3556](https://github.com/mochajs/mocha/issues/3556):

- Mocha now supports "RC" files in JS, JSON, YAML, or `package.json`-based (using `mocha` property) format
Copy link
Contributor

@Alhadis Alhadis Dec 21, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RC = RunCom ("run commands")

Historic artefact from 1960s-era computing. That being said, it isn't stopping me from reading this as Moch Arc, but hey.

@cgalvarez, be glad I slacked off on rehauling atom-mocha: I was about to kill off support for package.json configs in favour of mocha.opts, now upstream has deprecated the latter in favour of the former. 😀

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, "mocha.opts" is rcfile-like; the new ones are strictly configuration files.

@sindresorhus
Copy link
Contributor

Still waiting on @sindresorhus to review chalk/supports-color#90; assuming he accepts and we bump that dependency afterwards, it will close longstanding issue #1304.

Sorry about the delay. Done now: https://github.com/chalk/supports-color/releases/tag/v6.0.0 :)

Signed-off-by: Christopher Hiller <boneskull@boneskull.com>
@boneskull boneskull removed this from the v6.0.0 milestone Jan 1, 2019
@boneskull boneskull closed this Jan 18, 2019
@boneskull boneskull deleted the v6.0.0-changelog branch January 18, 2019 22:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: documentation anything involving docs or mochajs.org semver-patch implementation requires increase of "patch" version number; "bug fixes"
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants