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

fix(preset): recommended-bump ESLint preset #295

Conversation

ingmarh
Copy link
Contributor

@ingmarh ingmarh commented Mar 2, 2018

In a project, we recently started to use conventional-recommended-bump (version 2.0.6) and it was giving us wrong results with npx conventional-recommended-bump -p eslint. The latest version that works with -p eslint seems to be 1.2.1 (with built-in presets).

It seems that the Angular preset was inadvertently copied into the ESLint package with commit 60815b5.

This corrects the conventional-recommended-bump ESLint preset in conventional-changelog-eslint to behave the same as the built-in ESLint preset that was removed with #270.

Related to #241

With commit 60815b5, it seems that the
Angular preset was inadvertently copied into the ESLint package.

This corrects the `conventional-recommended-bump` ESLint preset in
`conventional-changelog-eslint` to behave the same as the built-in
ESLint preset that was removed with conventional-changelog#270.

Related to conventional-changelog#241
@hutson hutson self-requested a review March 3, 2018 03:07
@hutson hutson self-assigned this Mar 3, 2018
@hutson hutson added the bug label Mar 3, 2018
@hutson
Copy link
Contributor

hutson commented Mar 3, 2018

I'm really sorry! This was definitely a big mistake on my part.

👍 This change looks good to me.

@hutson hutson merged commit acf9c19 into conventional-changelog:master Mar 3, 2018
@hutson
Copy link
Contributor

hutson commented Mar 3, 2018

Version 1.0.5 has been released.

@hutson hutson mentioned this pull request Mar 3, 2018
@ingmarh ingmarh deleted the fix/recommended-bump-eslint-preset branch March 3, 2018 15:54
@ingmarh
Copy link
Contributor Author

ingmarh commented Mar 3, 2018

Thanks for merging, and the quick release. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants