Release v1.8.1, webpack/0.2.5 #353
Conversation
|
I think we should probably separate submodule changelogs. Either by putting the core module's changelog first, then the resolvers (with a "table of contents" at the top of the page), or in separate files (I would choose option one). And it would be nice to have the same diff links ( Though we can do this all at a late time, and this LGTM ;) |
|
Yeah, the resolvers have been kindof a pain in the changelog. Esp. because I can't create one of those diff links for a subtree (...right?). I'd probably put them in their own file, but they have been changing somewhat infrequently so I haven't bothered. 😅 |
You could, if you prepend them with something like ## [resolvers/webpack-0.2.5] - 2016-05-23
[resolvers/webpack-0.2.5]: ./foo |
* Added handling for multiple Webpack configs If the Webpack config is an array, then use the first config that includes a resolve section. * Adding unit test for multiple webpack configs * Fixed unit test for multiple webpack configs * Remove only call from unit test * Added 'config-index' setting for resolving multiple configs * Added documentation and release notes for multiple config support * Fixed documentation for config-index; Fixed JSON in YAML examples
|
🎉 |
|
took long enough 😅 |
Releasing bugfixes + minor improvements to core plugin + Webpack resolver.
#332 feels semver-minor because it's large, but in all likelihood it just hasn't impacted anyone before @jkimbo brought it up. So probably valid semver-patch.
Tasks: