kvalita 1.24.1 → 1.24.2

package/README.md

@@ -45,7 +45,7 @@ The rest apply to all code:
 - `as unknown as`, which skips the type check entirely.
 - An object literal cast with `as Type`, where an annotation checks every field. `as const` is fine.
 - `.catch()` chained on a promise, where try/catch around an `await` is the house style. A fire-and-forget call behind `void` keeps its `.catch()`.
-- Two or more `===` comparisons against literals in one condition, which read better as a named array and `.includes()`.
+- Two or more `===` comparisons of one variable against literals, which read better as a named array and `.includes()`. A property such as `parsed.kind` is left alone, since a chain on it can narrow a union that `.includes()` cannot.
 - A regex constant whose name doesn't end with `Regex`.
 
 The plugins load from `node_modules/kvalita`, so the config expects kvalita installed at the project root.
@@ -131,7 +131,7 @@ jobs:
     secrets: inherit
 ```
 
-`shared-release` takes `branch`, `build`, `config` and `bun-version`; `shared-test` takes `bun-version` and `ref`. Every one has a default, so a repo on the common setup passes nothing. Start every release from `main` and pick the branch with `branch`: `shared-release` checks it out and tells semantic-release to release it. Pass the same branch as `ref` when a release job waits on `shared-test`, or the tests check `main` instead of the branch being released.
+`shared-release` takes `branch`, `build`, `config` and `bun-version`; `shared-test` takes `bun-version` and `ref`. Every one has a default, so a repo on the common setup passes nothing. Start the release from the branch it releases, and pass that branch as `branch`. npm's provenance names the branch the run started on, so a run started on `main` can't publish another branch. Pass the same branch as `ref` to any gate job, such as `shared-test`, so the gates check the code being released.
 
 `shared-package` checks the package the way a consumer gets it. It builds the package, installs it into an empty project with `npm install --install-links`, so only the published files land there, and loads every entry point in `exports`: through `import`, and through `require()` where a `require` condition exists. It does that on every even Node.js major from the floor in `engines.node`, or 18 when it isn't set, up to the latest release. On the latest one, it also turns off syntax detection and `require()` of ESM files, which older versions don't have. Optional peers get installed too, since an entry point built on one needs it.
 

package/configs/biome/no-literal-equality-chain.grit

@@ -1,6 +1,7 @@
 language js
 
 `$left === $first || $left === $second` where {
+  $left <: JsIdentifierExpression(),
   $first <: or {
     string(),
     number()

package/package.json

@@ -42,5 +42,5 @@
     "semantic-release": "^25.0.9",
     "typescript": "^7.0.2"
   },
-  "version": "1.24.1"
+  "version": "1.24.2"
 }