bahlint 28.58.6934 → 28.58.693401

package/README.md

@@ -1,6 +1,6 @@
 [![npm version](https://img.shields.io/npm/v/bahlint.svg)](https://www.npmjs.com/package/bahlint)
 [![Downloads](https://img.shields.io/npm/dm/bahlint.svg)](https://www.npmjs.com/package/bahlint)
-[![Build Status](https://github.com/eslint/eslint/workflows/CI/badge.svg)](https://github.com/eslint/eslint/actions)
+[![Build Status](https://github.com/bahlint/bahlint/workflows/CI/badge.svg)](https://github.com/bahlint/bahlint/actions)
 <br>
 [![Open Collective Backers](https://img.shields.io/opencollective/backers/eslint)](https://opencollective.com/eslint)
 [![Open Collective Sponsors](https://img.shields.io/opencollective/sponsors/eslint)](https://opencollective.com/eslint)
@@ -166,7 +166,7 @@ Refer to the [Quick Start Guide](https://eslint.org/docs/latest/use/getting-star
 
 ### Where to ask for help?
 
-Open a [discussion](https://github.com/eslint/eslint/discussions) or stop by our [Discord server](https://eslint.org/chat).
+Open a [discussion](https://github.com/bahlint/bahlint/discussions) or stop by our [Discord server](https://eslint.org/chat).
 
 ### Why doesn't ESLint lock dependency versions?
 
@@ -180,35 +180,35 @@ The Twilio blog has a [deeper dive](https://www.twilio.com/blog/lockfiles-nodejs
 
 ## Releases
 
-We have scheduled releases every two weeks on Friday or Saturday. You can follow a [release issue](https://github.com/eslint/eslint/issues?q=is%3Aopen+is%3Aissue+label%3Arelease) for updates about the scheduling of any particular release.
+We have scheduled releases every two weeks on Friday or Saturday. You can follow a [release issue](https://github.com/bahlint/bahlint/issues?q=is%3Aopen+is%3Aissue+label%3Arelease) for updates about the scheduling of any particular release.
 
 ## Security Policy
 
-ESLint takes security seriously. We work hard to ensure that ESLint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full [security policy](https://github.com/eslint/.github/blob/master/SECURITY.md).
+Bahlint takes security seriously. We work hard to ensure that Bahlint is safe for everyone and that security issues are addressed quickly and responsibly. Read the full [security policy](https://github.com/bahlint/.github/blob/master/SECURITY.md).
 
 ## Semantic Versioning Policy
 
-ESLint follows [semantic versioning](https://semver.org). However, due to the nature of ESLint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for ESLint:
+Bahlint follows [semantic versioning](https://semver.org). However, due to the nature of Bahlint as a code quality tool, it's not always clear when a minor or major version bump occurs. To help clarify this for everyone, we've defined the following semantic versioning policy for Bahlint:
 
 - Patch release (intended to not break your lint build)
-    - A bug fix in a rule that results in ESLint reporting fewer linting errors.
+    - A bug fix in a rule that results in Bahlint reporting fewer linting errors.
     - A bug fix to the CLI or core (including formatters).
     - Improvements to documentation.
     - Non-user-facing changes such as refactoring code, adding, deleting, or modifying tests, and increasing test coverage.
     - Re-releasing after a failed release (i.e., publishing a release that doesn't work for anyone).
 - Minor release (might break your lint build)
-    - A bug fix in a rule that results in ESLint reporting more linting errors.
+    - A bug fix in a rule that results in Bahlint reporting more linting errors.
     - A new rule is created.
-    - A new option to an existing rule that does not result in ESLint reporting more linting errors by default.
-    - A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in ESLint reporting more linting errors by default.
+    - A new option to an existing rule that does not result in Bahlint reporting more linting errors by default.
+    - A new addition to an existing rule to support a newly-added language feature (within the last 12 months) that will result in Bahlint reporting more linting errors by default.
     - An existing rule is deprecated.
     - A new CLI capability is created.
     - New capabilities to the public API are added (new classes, new methods, new arguments to existing methods, etc.).
     - A new formatter is created.
-    - `eslint:recommended` is updated and will result in strictly fewer linting errors (e.g., rule removals).
+    - `bahlint:recommended` is updated and will result in strictly fewer linting errors (e.g., rule removals).
 - Major release (likely to break your lint build)
-    - `eslint:recommended` is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
-    - A new option to an existing rule that results in ESLint reporting more linting errors by default.
+    - `bahlint:recommended` is updated and may result in new linting errors (e.g., rule additions, most rule option updates).
+    - A new option to an existing rule that results in Bahlint reporting more linting errors by default.
     - An existing formatter is removed.
     - Part of the public API is removed or changed in an incompatible way. The public API includes:
         - Rule schemas
@@ -217,7 +217,7 @@ ESLint follows [semantic versioning](https://semver.org). However, due to the na
         - Node.js API
         - Rule, formatter, parser, plugin APIs
 
-According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (`~`) in `package.json` e.g. `"eslint": "~3.1.0"` to guarantee the results of your builds.
+According to our policy, any minor update may report more linting errors than the previous release (ex: from a bug fix). As such, we recommend using the tilde (`~`) in `package.json` e.g. `"bahlint": "~3.1.0"` to guarantee the results of your builds.
 
 ## License
 
@@ -253,7 +253,7 @@ These folks keep the project moving and are resources for help.
 
 ### Technical Steering Committee (TSC)
 
-The people who manage releases, review feature requests, and meet regularly to ensure ESLint is properly maintained.
+The people who manage releases, review feature requests, and meet regularly to ensure Bahlint is properly maintained.
 
 <table><tbody><tr><td align="center" valign="top" width="11%">
 <a href="https://github.com/nzakas">
@@ -352,7 +352,7 @@ Percy Ma
 
 ## Sponsors
 
-The following companies, organizations, and individuals support ESLint's ongoing maintenance and development. [Become a Sponsor](https://eslint.org/donate)
+The following companies, organizations, and individuals support Bahlint's ongoing maintenance and development. [Become a Sponsor](https://eslint.org/donate)
 to get your logo on our READMEs and [website](https://eslint.org/sponsors).
 
 <h3>Platinum Sponsors</h3>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "bahlint",
-  "version": "28.58.6934",
+  "version": "28.58.693401",
   "author": "Nicholas C. Zakas <nicholas+npm@nczconsulting.com>",
   "description": "An AST-based pattern checker for JavaScript.",
   "type": "commonjs",