## 1.9.0 - March 2022

* Closes #15, Allowing mixing different error level.
  * This bug required that the same rule can be defined with different error levels, that is not possible at the moment on eslint. Error level is not available at plugin level (as indicate by ESLint official documentation: "Keep in mind that the error level is not part of context.options, as the error level cannot be known or modified from inside a rule"). So I came up a different approach, which not only **allows to use "the same" rule with different error levels**, but also **allows Mixing custom set of regex rules**, this is useful for creating package/libraries/plugins with your own set of rules and sharing it with others.
* Improves project configuration.
  * Now uses [`any-eslint-parser`](https://www.npmjs.com/package/any-eslint-parser)
* Improves documentation.
  * Mixing.

Author: gmullerb

.eslintrc-any.json

@@ -0,0 +1,5 @@
+{
+  "extends": [ "plugin:base-style-config/common-rules" ],
+  "plugins": [ "base-style-config" ],
+  "parser": "any-eslint-parser"
+}

CHANGELOG.md

@@ -1,5 +1,14 @@
 # ESLint Plugin Regex Change Log
 
+## 1.9.0 - March 2022
+
+* Closes #15, Allowing mixing different error level.
+  * This bug required that the same rule can be defined with different error levels, that is not possible at the moment on eslint. Error level is not available at plugin level (as indicate by ESLint official documentation: "Keep in mind that the error level is not part of context.options, as the error level cannot be known or modified from inside a rule"). So I came up a different approach, which not only **allows to use "the same" rule with different error levels**, but also **allows Mixing custom set of regex rules**, this is useful for creating package/libraries/plugins with your own set of rules and sharing it with others.
+* Improves project configuration.
+  * Now uses [`any-eslint-parser`](https://www.npmjs.com/package/any-eslint-parser)
+* Improves documentation.
+  * Mixing
+
 ## 1.8.0 - August 2021
 
 * Closes #11, Improves the specification of the number of the line of the found error for the final report, Thanks to Maxim-Mazurok for His collaboration.