-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Release 2.3.0 #837
Release 2.3.0 #837
Conversation
enhanced-resolve has been bumped to 3.0.
[Tests] make package tests more robust by only checking .js files
* Update no-dynamic-require.md
Correct very minor typo (one character)
* Add `newlines` option to `newline-after-import` * Add tests for `newline-after-import` option and fix linter errors in test file * Fix broken tests, add docs * Update CHANGELOG * Add schema and further testing for `newlines` option on `newline-after-import` * Change `newlines` option to `count` for `newline-after-import` rule * Fix missing plural in docs * Add links in changelog and thank @ntdb :) * Add links to rules in changelog
Fix "default is a reserved keyword" error no-named-default tests
Docs required a close reading to realize that the glob array actually *disables* errors for the config option for matching files. This changes the description to be more explicit about what "activation" means for matching files.
Clarify docs for glob arrays
I'm confused; what's in this branch that isn't already in master? I'm not familiar with this flow for releasing. |
@@ -6,6 +6,19 @@ This change log adheres to standards from [Keep a CHANGELOG](http://keepachangel | |||
## Unreleased | |||
|
|||
|
|||
## 0.8.1 - 2017-01-19 | |||
### Changed | |||
- official support for Webpack 2.2.0 (RC), thanks [@graingert] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👏
I gave this a basic look-over and didn't see any show-stoppers. The boat has sailed on the constituent PRs so I'm not commenting on implementation. The Readme and Changelog changes appear to be complete. |
@ljharb: nothing. I just do this to get a final confirmation CI is working + it highlights the set of commits since the last release. I'll merge and publish when I get to my desk. |
published! |
anything obviously necessary pre-publish? I'd like to just get it pushed if there are no red flags.