@blumintinc/eslint-plugin-blumint 1.20.143 → 1.20.145

package/lib/index.js

@@ -223,7 +223,7 @@ function noFrontendImportsFromFunctionsPatterns(pattern) {
 module.exports = {
     meta: {
         name: '@blumintinc/eslint-plugin-blumint',
-        version: '1.20.143',
+        version: '1.20.145',
     },
     parseOptions: {
         ecmaVersion: 2020,

package/lib/rules/enforce-centralized-mock-firestore.js

@@ -338,27 +338,6 @@ exports.enforceCentralizedMockFirestore = (0, createRule_1.createRule)({
                     }
                 }
             },
-            // Handle dynamic imports
-            'AwaitExpression > CallExpression[callee.type="ImportExpression"]'(node) {
-                const parent = node.parent;
-                if (parent?.type === utils_1.AST_NODE_TYPES.AwaitExpression &&
-                    parent.parent?.type === utils_1.AST_NODE_TYPES.VariableDeclarator &&
-                    parent.parent.id.type === utils_1.AST_NODE_TYPES.ObjectPattern) {
-                    for (const prop of parent.parent.id.properties) {
-                        if (prop.type === utils_1.AST_NODE_TYPES.Property &&
-                            prop.key.type === utils_1.AST_NODE_TYPES.Identifier &&
-                            prop.key.name === 'mockFirestore') {
-                            mockFirestoreNodes.add(parent.parent);
-                            // Track renamed destructured imports
-                            if (prop.value.type === utils_1.AST_NODE_TYPES.Identifier &&
-                                prop.value.name !== 'mockFirestore') {
-                                customMockFirestoreNames.add(prop.value.name);
-                            }
-                            break;
-                        }
-                    }
-                }
-            },
             // Handle complex object destructuring
             'ObjectPattern > Property > ObjectPattern > Property > ObjectPattern > Property[key.name="mockFirestore"]'(node) {
                 let current = node;

package/lib/rules/no-always-true-false-conditions.js

@@ -3,6 +3,81 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.noAlwaysTrueFalseConditions = void 0;
 const createRule_1 = require("../utils/createRule");
 const utils_1 = require("@typescript-eslint/utils");
+const ASTHelpers_1 = require("../utils/ASTHelpers");
+const BREAKABLE = new Set([
+    utils_1.AST_NODE_TYPES.WhileStatement,
+    utils_1.AST_NODE_TYPES.DoWhileStatement,
+    utils_1.AST_NODE_TYPES.ForStatement,
+    utils_1.AST_NODE_TYPES.ForInStatement,
+    utils_1.AST_NODE_TYPES.ForOfStatement,
+    utils_1.AST_NODE_TYPES.SwitchStatement,
+]);
+/**
+ * Whether `body` can leave the loop that owns it.
+ *
+ * An unlabeled `break` binds to the nearest enclosing loop or switch, so a
+ * nested breakable is still walked but its own unlabeled breaks do not count; a
+ * labeled one counts when it names this loop. `return` and `throw` leave the
+ * loop as well, unless they sit inside a nested function, which has its own.
+ */
+function canExitLoop(body, label) {
+    let escapes = false;
+    const visit = (node, insideNestedBreakable) => {
+        if (escapes)
+            return;
+        switch (node.type) {
+            case utils_1.AST_NODE_TYPES.FunctionDeclaration:
+            case utils_1.AST_NODE_TYPES.FunctionExpression:
+            case utils_1.AST_NODE_TYPES.ArrowFunctionExpression:
+                return;
+            case utils_1.AST_NODE_TYPES.BreakStatement:
+                if (node.label ? node.label.name === label : !insideNestedBreakable) {
+                    escapes = true;
+                }
+                return;
+            case utils_1.AST_NODE_TYPES.ReturnStatement:
+            case utils_1.AST_NODE_TYPES.ThrowStatement:
+                escapes = true;
+                return;
+            default:
+                break;
+        }
+        const nested = insideNestedBreakable || BREAKABLE.has(node.type);
+        for (const [key, value] of Object.entries(node)) {
+            if (key === 'parent')
+                continue;
+            if (Array.isArray(value)) {
+                for (const child of value) {
+                    if (ASTHelpers_1.ASTHelpers.isNode(child))
+                        visit(child, nested);
+                }
+            }
+            else if (ASTHelpers_1.ASTHelpers.isNode(value)) {
+                visit(value, nested);
+            }
+        }
+    };
+    visit(body, false);
+    return escapes;
+}
+/**
+ * `while (true)` and `do … while (true)` around a `break` are how a loop whose
+ * exit is only known mid-body is written — cursor pagination being the usual
+ * case. The condition is the point, and unlike an `if` it cannot be removed:
+ * the only way to satisfy the report is to rewrite the loop as `for (;;)`,
+ * which this rule already accepts because it has no test node to check. A
+ * literal `true` over a body with no way out is still reported, since that loop
+ * really does run forever (#1973).
+ */
+function isDeliberateInfiniteLoop(loop) {
+    if (loop.test?.type !== utils_1.AST_NODE_TYPES.Literal || loop.test.value !== true) {
+        return false;
+    }
+    const label = loop.parent?.type === utils_1.AST_NODE_TYPES.LabeledStatement
+        ? loop.parent.label.name
+        : null;
+    return canExitLoop(loop.body, label);
+}
 exports.noAlwaysTrueFalseConditions = (0, createRule_1.createRule)({
     name: 'no-always-true-false-conditions',
     meta: {
@@ -1498,15 +1573,19 @@ exports.noAlwaysTrueFalseConditions = (0, createRule_1.createRule)({
             },
             // Check while loops
             WhileStatement(node) {
+                if (isDeliberateInfiniteLoop(node))
+                    return;
                 checkCondition(node.test);
             },
             // Check do-while loops
             DoWhileStatement(node) {
+                if (isDeliberateInfiniteLoop(node))
+                    return;
                 checkCondition(node.test);
             },
             // Check for loop conditions
             ForStatement(node) {
-                if (node.test) {
+                if (node.test && !isDeliberateInfiniteLoop(node)) {
                     checkCondition(node.test);
                 }
             },

package/lib/rules/no-explicit-return-type.js

@@ -8,6 +8,7 @@ const importRemoval_1 = require("../utils/importRemoval");
 const typeDeclarationRemoval_1 = require("../utils/typeDeclarationRemoval");
 const replacementSegments_1 = require("../utils/replacementSegments");
 const lexicalScope_1 = require("../utils/lexicalScope");
+const arrowAnnotationGap_1 = require("../utils/arrowAnnotationGap");
 const defaultOptions = {
     allowRecursiveFunctions: true,
     allowOverloadedFunctions: true,
@@ -780,25 +781,6 @@ function batchAnnotations(source, candidates) {
     });
     return [...batches.values()];
 }
-/**
- * A comment whose meaning is tied to where it sits. Re-emitting one somewhere
- * else retargets it — a disable directive lands on an unrelated line and a
- * `@ts-expect-error` becomes an error of its own — so a removal that would move
- * one is withheld instead.
- */
-function isPositionalDirective(comment) {
-    if ((0, disableDirectives_1.parseDisableDirectives)([comment]).length > 0) {
-        return true;
-    }
-    const value = comment.value.trim();
-    return value.startsWith('@ts-expect-error') || value.startsWith('@ts-ignore');
-}
-/** The indentation of the line `offset` sits on, for a carried line break. */
-function indentAt(source, offset) {
-    const lineStart = source.text.lastIndexOf('\n', offset - 1) + 1;
-    const [indent] = /^[ \t]*/.exec(source.text.slice(lineStart, offset)) ?? [''];
-    return indent;
-}
 /**
  * Whether the span deletes a whole declaration of the program.
  *
@@ -827,9 +809,9 @@ function carriedText(source, range) {
         .filter((comment) => comment.range[0] >= range[0] && comment.range[1] <= range[1]);
     if (comments.length === 0)
         return '';
-    if (comments.some(isPositionalDirective))
+    if (comments.some(arrowAnnotationGap_1.isPositionalDirective))
         return null;
-    const indent = indentAt(source, range[0]);
+    const indent = (0, arrowAnnotationGap_1.indentAt)(source, range[0]);
     const segments = comments.map((comment) => ({
         text: source.text.slice(comment.range[0], comment.range[1]),
         breakAfter: (0, replacementSegments_1.requiresLineBreakAfter)(comment),
@@ -846,70 +828,20 @@ function carriedText(source, range) {
             : ' ';
     return `${lead}${body}${trail}`;
 }
-/** Every character the syntactic grammar counts as a LineTerminator. */
-const LINE_TERMINATOR = /[\n\r\u2028\u2029]/;
-const textOf = (source, range) => source.text.slice(range[0], range[1]);
-/**
- * The span an arrow's return annotation occupies between the parameter list and
- * the `=>`, together with that arrow token.
- *
- * The span holds the annotation, whitespace and comments and nothing else,
- * which is what makes it safe to rewrite wholesale: no binding reference can
- * hide in it beyond the ones the annotation itself names.
- */
-function arrowAnnotationGap(source, returnType) {
-    const parametersEnd = source.getTokenBefore(returnType);
-    const arrow = source.getTokenAfter(returnType, {
-        filter: (token) => token.value === '=>',
-    });
-    if (!parametersEnd || !arrow)
-        return null;
-    const gap = [parametersEnd.range[1], arrow.range[0]];
-    return containsRange(gap, returnType.range) ? { gap, arrow } : null;
-}
-/**
- * Re-emits `comments` on the far side of the arrow, where a line terminator is
- * inert, consuming the horizontal whitespace the arrow already had after it so
- * the body keeps a single separator.
- */
-function hoistPastArrow(source, arrow, comments) {
-    const indent = indentAt(source, arrow.range[0]);
-    const trailingText = source.text.slice(arrow.range[1]);
-    const [spacing] = /^[ \t]*/.exec(trailingText) ?? [''];
-    const body = (0, replacementSegments_1.joinSegmentBody)(comments.map((comment) => ({
-        text: textOf(source, comment.range),
-        breakAfter: true,
-    })), indent);
-    const rest = trailingText.slice(spacing.length);
-    const separator = LINE_TERMINATOR.test(rest.charAt(0))
-        ? ''
-        : (0, replacementSegments_1.requiresLineBreakAfter)(comments[comments.length - 1])
-            ? `\n${indent}`
-            : ' ';
-    return {
-        range: [arrow.range[1], arrow.range[1] + spacing.length],
-        text: ` ${body}${separator}`,
-    };
-}
 /**
  * The edits that strip one annotation, carrying every comment the strip
  * strands rather than deleting it (#1877). `null` withholds the fix, for a
  * comment whose meaning is its position and which cannot stay where it is.
  *
  * An arrow is the one subject whose annotation sits inside a restricted
- * production: `ArrowParameters [no LineTerminator here] =>` forbids a line
- * terminator between the parameter list and the arrow, and a block comment
- * carrying a line terminator IS one to the grammar. A comment left there — or
- * carried there from inside the annotation — therefore turns the output into a
- * hard SyntaxError that only V8 reports, since `@typescript-eslint/parser`
- * accepts it (#1964). Such a comment is re-emitted past the `=>` instead, the
- * nearest position outside the restricted gap that cannot itself begin one;
- * hoisting it above the enclosing line would anchor an insertion at a column
- * zero that may sit inside a template literal or JSX text, where the comment
- * would become content rather than code.
+ * production, so its edits come from the shared planner that answers for that
+ * grammar (#1964). The removal span handed to it is the annotation's own
+ * range: unlike the planner's other caller, nothing here reaches back over the
+ * whitespace ahead of the `:`.
  *
  * Every other subject ends its parameter list at a body or a semicolon, so its
- * stranded comments stay where they were written.
+ * stranded comments stay where they were written and a deletion that carries
+ * them in place is correct.
  */
 function planAnnotationEdits(source, entry) {
     const range = entry.returnType.range;
@@ -917,53 +849,7 @@ function planAnnotationEdits(source, entry) {
         const carried = carriedText(source, range);
         return carried === null ? null : [{ range, text: carried }];
     }
-    const gapInfo = arrowAnnotationGap(source, entry.returnType);
-    if (!gapInfo)
-        return null;
-    const { gap, arrow } = gapInfo;
-    const comments = source
-        .getAllComments()
-        .filter((comment) => containsRange(gap, comment.range));
-    const stranded = comments.filter((comment) => containsRange(range, comment.range));
-    // What the plain deletion would leave between the parameters and the arrow.
-    // A comment left there contributes its own text, so a line comment or a
-    // multi-line block comment shows up here as the line terminator it is.
-    const residue = `${textOf(source, [gap[0], range[0]])}${textOf(source, [
-        range[1],
-        gap[1],
-    ])}`;
-    // The plain deletion is kept wherever it already lands a legal gap and
-    // strands nothing, so no output that survives today moves by a byte.
-    if (stranded.length === 0 && !LINE_TERMINATOR.test(residue)) {
-        return [{ range, text: '' }];
-    }
-    // Rewriting the gap collapses the lines it spanned, which moves the line a
-    // directive inside it points at, so the whole fix is withheld rather than
-    // retargeting one. The gap a directive can share with nothing else is left
-    // untouched by the branch above.
-    if (comments.some(isPositionalDirective))
-        return null;
-    const hoisted = comments.filter(replacementSegments_1.requiresOwnLine);
-    const inline = comments
-        .filter((comment) => !(0, replacementSegments_1.requiresOwnLine)(comment))
-        .map((comment) => textOf(source, comment.range));
-    const edits = [
-        { range: gap, text: inline.length === 0 ? ' ' : ` ${inline.join(' ')} ` },
-    ];
-    if (hoisted.length > 0) {
-        edits.push(hoistPastArrow(source, arrow, hoisted));
-    }
-    return edits;
-}
-/**
- * ESLint applies a fix whole or not at all, and rejects one whose edits
- * overlap. Two spans planned independently — an annotation and the declaration
- * that strands it — can only overlap if a premise here is wrong, so an overlap
- * withdraws the fix rather than throwing at apply time.
- */
-function isDisjoint(edits) {
-    const sorted = [...edits].sort((left, right) => left.range[0] - right.range[0]);
-    return sorted.every((edit, index) => index === 0 || sorted[index - 1].range[1] <= edit.range[0]);
+    return (0, arrowAnnotationGap_1.planArrowAnnotationEdits)(source, entry.returnType, range);
 }
 /**
  * The edits a single fix makes for `batch`: the annotations themselves plus the
@@ -1002,7 +888,7 @@ function planRemoval(source, removalSource, batch) {
             return null;
         edits.push({ range, text: carried });
     }
-    return isDisjoint(edits) ? edits : null;
+    return (0, arrowAnnotationGap_1.isDisjoint)(edits) ? edits : null;
 }
 exports.noExplicitReturnType = (0, createRule_1.createRule)({
     name: 'no-explicit-return-type',

package/lib/rules/no-redundant-annotation-assertion.js

@@ -28,6 +28,7 @@ const utils_1 = require("@typescript-eslint/utils");
 const visitor_keys_1 = require("@typescript-eslint/visitor-keys");
 const ts = __importStar(require("typescript"));
 const ASTHelpers_1 = require("../utils/ASTHelpers");
+const arrowAnnotationGap_1 = require("../utils/arrowAnnotationGap");
 const createRule_1 = require("../utils/createRule");
 const disableDirectives_1 = require("../utils/disableDirectives");
 const importRemoval_1 = require("../utils/importRemoval");
@@ -174,6 +175,49 @@ function annotationRemovalRange(typeAnnotation, sourceCode) {
 function typeText(type, checker) {
     return checker.typeToString(type, undefined, typeFormatFlags());
 }
+/**
+ * Whether the checker failed to resolve `type` to a real one.
+ *
+ * `@typescript-eslint/parser` hands back parser services even with no
+ * `parserOptions.project`, but the program it builds then has no lib, so every
+ * type naming a global degrades: array types collapse to one shared anonymous
+ * `{}` (no symbol), and generic references such as `Map<K, V>` become the error
+ * type. Both are assignable to everything and stringify alike, so two unrelated
+ * types compare equal — `string[]` and `number[]` are literally the same object.
+ * Answering "no type information" with a report is what made this rule delete
+ * annotations and silently change a binding's type (#1972).
+ *
+ * A genuine `{}`, `{ a: number }` or `() => void` carries a `__type` symbol, so
+ * only the degraded forms match here. Under a real `tsconfig` nothing does.
+ */
+function isUnresolvedType(type) {
+    const candidate = type;
+    if ((type.flags & ts.TypeFlags.Any) !== 0 &&
+        candidate.intrinsicName === 'error') {
+        return true;
+    }
+    return (candidate.objectFlags !== undefined &&
+        (candidate.objectFlags & ts.ObjectFlags.Anonymous) !== 0 &&
+        !type.symbol);
+}
+/**
+ * Whitespace inside a type is not part of it, so `Map<string, A>` and
+ * `Map<string,A>` must compare equal. Spaces between two word characters are
+ * kept so `keyof A` cannot collapse onto a type named `keyofA`.
+ */
+function normalizeTypeSpelling(text) {
+    return text
+        .replace(/\s+/g, ' ')
+        .replace(/\s*([<>,[\]()|&{}:;?])\s*/g, '$1')
+        .trim();
+}
+/**
+ * The comparison form drops spacing the developer chose, so a type spanning
+ * several lines is flattened for the message but otherwise quoted as written.
+ */
+function displayTypeSpelling(text) {
+    return text.replace(/\s+/g, ' ').trim();
+}
 function unwrapAlias(type, checker) {
     const aliasSymbol = type
         .aliasSymbol;
@@ -334,8 +378,13 @@ function doTypeTextsMatch(representations) {
         annotationCanonical === assertionCanonical ||
         annotationStructural === assertionStructural);
 }
-function selectMatchingTypeRepresentation(representations) {
-    return representations.annotationText;
+/**
+ * The message names the type the developer is looking at, so it is the
+ * annotation's own spelling rather than `typeToString`, which renders
+ * `ValidResult[]` as `Array<ValidResult>` and an unresolved type as `{}`.
+ */
+function selectMatchingTypeRepresentation(annotationSpelling) {
+    return annotationSpelling;
 }
 /**
  * Checks if two types are effectively equal for the purpose of identifying redundant assertions.
@@ -362,16 +411,32 @@ function areTypesEffectivelyEqual(annotationType, assertionType, representations
  * @param services The parser services.
  * @returns The matching type string if the types are effectively equal, null otherwise.
  */
-function haveMatchingTypes(annotation, assertion, checker, services) {
+function haveMatchingTypes(annotation, assertion, checker, services, sourceCode) {
     const annotationType = getComparableType(annotation, checker, services);
     const assertionType = getComparableType(assertion, checker, services);
     if (!annotationType || !assertionType)
         return null;
+    const annotationText = sourceCode.getText(annotation);
+    const annotationSpelling = normalizeTypeSpelling(annotationText);
+    const reportedType = displayTypeSpelling(annotationText);
+    /**
+     * With either side unresolved the checker cannot separate "same type" from
+     * "no type information", so fall back to how the two are written. Identical
+     * spellings in one scope denote one type, which keeps every genuinely
+     * redundant pair reportable while the mismatched pairs that motivated this
+     * fallback — `string[]` against `number[]` — no longer match.
+     */
+    if (isUnresolvedType(annotationType) || isUnresolvedType(assertionType)) {
+        const assertionSpelling = normalizeTypeSpelling(sourceCode.getText(assertion));
+        return annotationSpelling === assertionSpelling
+            ? selectMatchingTypeRepresentation(reportedType)
+            : null;
+    }
     const representations = getTypeRepresentations(annotationType, assertionType, checker);
     if (!areTypesEffectivelyEqual(annotationType, assertionType, representations, checker)) {
         return null;
     }
-    return selectMatchingTypeRepresentation(representations);
+    return selectMatchingTypeRepresentation(reportedType);
 }
 function getReturnAssertionSite(node) {
     const value = node.type === utils_1.AST_NODE_TYPES.MethodDefinition ? node.value : node;
@@ -864,14 +929,15 @@ exports.noRedundantAnnotationAssertion = (0, createRule_1.createRule)({
          * trading an unused import for a dangling type.
          */
         const isReportSuppressed = (0, disableDirectives_1.createSuppressionChecker)(context);
-        function collectIfRedundant(annotation, assertion, reportNode, fixerTarget) {
-            const matchingType = haveMatchingTypes(annotation.typeAnnotation, assertion, checker, parserServices);
+        function collectIfRedundant(annotation, assertion, reportNode, fixerTarget, arrowReturnType) {
+            const matchingType = haveMatchingTypes(annotation.typeAnnotation, assertion, checker, parserServices, sourceCode);
             if (!matchingType)
                 return null;
             const site = {
                 reportNode,
                 removal: annotationRemovalRange(fixerTarget, sourceCode),
                 matchingType,
+                arrowReturnType,
             };
             sites.push(site);
             return site;
@@ -890,25 +956,54 @@ exports.noRedundantAnnotationAssertion = (0, createRule_1.createRule)({
             // Whether the annotation is load-bearing is decided at `Program:exit`:
             // the cycle can run through a function elsewhere in the file, and every
             // annotation in it goes in the same batched fix.
-            const site = collectIfRedundant(annotation, assertionSite.assertion, reportNode, annotation);
+            const site = collectIfRedundant(annotation, assertionSite.assertion, reportNode, annotation, node.type === utils_1.AST_NODE_TYPES.ArrowFunctionExpression
+                ? annotation
+                : undefined);
             if (site)
                 returnCandidates.push({ site, owners, references });
         }
+        /**
+         * The text a site's removal writes in place of the annotation.
+         *
+         * An arrow's annotation is the one that cannot simply be deleted: its slice
+         * sits inside a restricted production, so a comment left in the gap — or
+         * stranded there by the deletion — turns the output into a SyntaxError that
+         * only a compiler reports (#1969). Every other subject ends its signature at
+         * a body or a separator, so its slice is deleted exactly as before.
+         */
+        function planEdits(site) {
+            if (!site.arrowReturnType) {
+                return [{ range: site.removal, text: '' }];
+            }
+            return (0, arrowAnnotationGap_1.planArrowAnnotationEdits)(sourceCode, site.arrowReturnType, site.removal);
+        }
         /**
          * The sites whose fixes actually ship. A site is excluded when its report
-         * will be suppressed, or when its own removal orphans something the helper
-         * cannot rewrite — a local alias, an interface, a type parameter. Deleting a
-         * declaration is a materially riskier edit than dropping an import
-         * specifier, and the author is better placed to decide whether the type
-         * should go or be used elsewhere.
+         * will be suppressed, when its own removal orphans something the helper
+         * cannot rewrite — a local alias, an interface, a type parameter — or when
+         * its edits cannot be planned without moving a comment whose meaning is its
+         * position. Deleting a declaration is a materially riskier edit than
+         * dropping an import specifier, and the author is better placed to decide
+         * whether the type should go or be used elsewhere.
          *
          * Screening individually before batching keeps one unfixable site from
          * vetoing the rest: orphanhood grows monotonically with the removed set, so
          * a site that cannot be planned alone can only ever poison the batch.
          */
         function selectFixableSites(candidates) {
-            return candidates.filter((site) => !isReportSuppressed(site.reportNode) &&
-                (0, importRemoval_1.planOrphanedImportRemoval)(sourceCode, [site.removal]) !== null);
+            const fixable = [];
+            for (const site of candidates) {
+                if (isReportSuppressed(site.reportNode))
+                    continue;
+                if ((0, importRemoval_1.planOrphanedImportRemoval)(sourceCode, [site.removal]) === null) {
+                    continue;
+                }
+                const edits = planEdits(site);
+                if (edits === null)
+                    continue;
+                fixable.push({ site, edits });
+            }
+            return fixable;
         }
         /**
          * The file's inference graph, built only where a return annotation is at
@@ -936,27 +1031,33 @@ exports.noRedundantAnnotationAssertion = (0, createRule_1.createRule)({
                 if (reportable.length === 0)
                     return;
                 const fixable = selectFixableSites(reportable);
-                const removals = fixable.map((site) => site.removal);
+                const removals = fixable.map((entry) => entry.site.removal);
                 // One plan over every surviving removal: an import referenced solely by
                 // annotations that all go in this pass is orphaned by their union, even
                 // though no single one of them orphans it.
                 const importRanges = removals.length > 0
                     ? (0, importRemoval_1.planOrphanedImportRemoval)(sourceCode, removals)
                     : null;
+                // The batch rewrites some spans rather than deleting them, and ships as
+                // one fix: ESLint rejects a fix whose edits overlap, so an overlap
+                // withdraws the fix instead of throwing at apply time. Only a wrong
+                // premise can produce one — an annotation's gap and an import
+                // declaration are disjoint regions of the file.
+                const edits = [
+                    ...fixable.flatMap((entry) => entry.edits),
+                    ...(importRanges ?? []).map((range) => ({ range, text: '' })),
+                ];
                 // The whole batch ships as one fix, so no removal can land without the
                 // others that the import's orphanhood was judged against. The rest
                 // report without a fixer; the carrier's pass already resolves them.
-                const carrier = importRanges ? fixable[0] : undefined;
+                const carrier = importRanges && (0, arrowAnnotationGap_1.isDisjoint)(edits) ? fixable[0]?.site : undefined;
                 for (const site of reportable) {
                     context.report({
                         node: site.reportNode,
                         messageId: 'redundantAnnotationAndAssertion',
                         data: { type: site.matchingType },
-                        fix: site === carrier && importRanges
-                            ? (fixer) => [
-                                ...removals.map((range) => fixer.removeRange([range[0], range[1]])),
-                                ...importRanges.map((range) => fixer.removeRange([range[0], range[1]])),
-                            ]
+                        fix: site === carrier
+                            ? (fixer) => edits.map((edit) => fixer.replaceTextRange([edit.range[0], edit.range[1]], edit.text))
                             : null,
                     });
                 }

package/lib/rules/no-undefined-null-passthrough.js

@@ -265,6 +265,21 @@ function checkImplicitReturn(node, context) {
     }
     if (!paramName)
         return;
+    /**
+     * A body that is the parameter itself — `(value) => value` — is not reported.
+     * What this rule looks for is a function that ANSWERS a nullish argument by
+     * handing the absence back: a guard, an `&&`, a ternary whose alternate is
+     * nullish. The identity function has no nullish-specific behaviour at all, so
+     * the prescribed remedy (validate up front, or return a concrete fallback)
+     * does not apply to it — least of all to `items.filter((x) => x)`, the
+     * standard truthiness filter, or to a generic `identity` helper.
+     *
+     * Every other spelling of that same function — a block-bodied arrow, a
+     * declaration, a function expression — was already accepted, so reporting
+     * only the implicit-return form made the verdict turn on body spelling. The
+     * test suite recorded that asymmetry as a deferred question and asked that a
+     * carve-out settle both spellings at once; this is that carve-out (#1974).
+     */
     if (isNullishPassthroughExpression(node.body, paramName)) {
         context.report({
             node,
@@ -272,14 +287,6 @@ function checkImplicitReturn(node, context) {
             data: { paramName },
         });
     }
-    else if (node.body.type === 'Identifier' && node.body.name === paramName) {
-        // Check for (param) => param
-        context.report({
-            node,
-            messageId: 'unexpected',
-            data: { paramName },
-        });
-    }
 }
 /**
  * Check if an expression is testing if a parameter is null or undefined

package/lib/utils/arrowAnnotationGap.d.ts

@@ -0,0 +1,72 @@
+import { TSESLint, TSESTree } from '@typescript-eslint/utils';
+import { TextRange } from './importRemoval';
+/**
+ * The span between an arrow function's parameter list and its `=>` is the one
+ * place a return-type annotation sits inside a restricted production:
+ * `ArrowParameters [no LineTerminator here] =>` forbids a line terminator
+ * there, and the syntactic grammar counts a block comment carrying a line
+ * terminator AS one. Stripping the annotation and leaving such a comment behind
+ * therefore emits a hard SyntaxError (TS1200 / V8 `Unexpected token '=>'`) —
+ * which `@typescript-eslint/parser` accepts, so no reparse-based guard sees it
+ * (#1964, #1969).
+ *
+ * Every other subject an annotation can hang off — a function declaration, a
+ * method, a class property with a body, a plain binding — ends its signature at
+ * a body or a separator, so nothing about the comments around it is restricted
+ * and a plain deletion stays correct.
+ */
+/** One span of a fix, and the text that replaces it. */
+export type Edit = {
+    range: TextRange;
+    text: string;
+};
+/**
+ * A comment whose meaning is tied to where it sits. Re-emitting one somewhere
+ * else retargets it — a disable directive lands on an unrelated line and a
+ * `@ts-expect-error` becomes an error of its own — so a rewrite that would move
+ * one is withheld instead.
+ */
+export declare function isPositionalDirective(comment: TSESTree.Comment): boolean;
+/** The indentation of the line `offset` sits on, for a carried line break. */
+export declare function indentAt(source: TSESLint.SourceCode, offset: number): string;
+/**
+ * The span an arrow's return annotation occupies between the parameter list and
+ * the `=>`, together with that arrow token.
+ *
+ * The span holds the annotation, whitespace and comments and nothing else,
+ * which is what makes it safe to rewrite wholesale: no binding reference can
+ * hide in it beyond the ones the annotation itself names.
+ */
+export declare function arrowAnnotationGap(source: TSESLint.SourceCode, returnType: TSESTree.TSTypeAnnotation): {
+    gap: TextRange;
+    arrow: TSESTree.Token;
+} | null;
+/**
+ * The edits that strip an arrow function's return annotation without leaving a
+ * line terminator in the restricted gap, carrying every comment the strip
+ * strands rather than deleting it (#1877).
+ *
+ * `removal` is the span the calling rule would otherwise delete: it covers the
+ * annotation and may reach further back over the horizontal whitespace ahead of
+ * the `:`. It must lie inside the gap, which it does for any annotation the
+ * caller located on the arrow itself.
+ *
+ * A comment that must own a line is re-emitted past the `=>`, the nearest
+ * position outside the restricted gap that cannot itself begin one; hoisting it
+ * above the enclosing line would anchor an insertion at a column zero that may
+ * sit inside a template literal or JSX text, where the comment would become
+ * content rather than code. A comment that trips no restricted production stays
+ * exactly where it was written, since moving comments gratuitously is its own
+ * regression.
+ *
+ * `null` withholds the fix, for a comment whose meaning is its position and
+ * which cannot stay where it is.
+ */
+export declare function planArrowAnnotationEdits(source: TSESLint.SourceCode, returnType: TSESTree.TSTypeAnnotation, removal: TextRange): Edit[] | null;
+/**
+ * ESLint applies a fix whole or not at all, and rejects one whose edits
+ * overlap. Spans planned independently — several annotations, and the bindings
+ * their removal orphans — can only overlap if a premise behind them is wrong,
+ * so an overlap withdraws the fix rather than throwing at apply time.
+ */
+export declare function isDisjoint(edits: readonly Edit[]): boolean;

package/lib/utils/arrowAnnotationGap.js

@@ -0,0 +1,150 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.isDisjoint = exports.planArrowAnnotationEdits = exports.arrowAnnotationGap = exports.indentAt = exports.isPositionalDirective = void 0;
+const disableDirectives_1 = require("./disableDirectives");
+const replacementSegments_1 = require("./replacementSegments");
+/** Every character the syntactic grammar counts as a LineTerminator. */
+const LINE_TERMINATOR = /[\n\r\u2028\u2029]/;
+function containsRange(outer, inner) {
+    return inner[0] >= outer[0] && inner[1] <= outer[1];
+}
+const textOf = (source, range) => source.text.slice(range[0], range[1]);
+/**
+ * A comment whose meaning is tied to where it sits. Re-emitting one somewhere
+ * else retargets it — a disable directive lands on an unrelated line and a
+ * `@ts-expect-error` becomes an error of its own — so a rewrite that would move
+ * one is withheld instead.
+ */
+function isPositionalDirective(comment) {
+    if ((0, disableDirectives_1.parseDisableDirectives)([comment]).length > 0) {
+        return true;
+    }
+    const value = comment.value.trim();
+    return value.startsWith('@ts-expect-error') || value.startsWith('@ts-ignore');
+}
+exports.isPositionalDirective = isPositionalDirective;
+/** The indentation of the line `offset` sits on, for a carried line break. */
+function indentAt(source, offset) {
+    const lineStart = source.text.lastIndexOf('\n', offset - 1) + 1;
+    const [indent] = /^[ \t]*/.exec(source.text.slice(lineStart, offset)) ?? [''];
+    return indent;
+}
+exports.indentAt = indentAt;
+/**
+ * The span an arrow's return annotation occupies between the parameter list and
+ * the `=>`, together with that arrow token.
+ *
+ * The span holds the annotation, whitespace and comments and nothing else,
+ * which is what makes it safe to rewrite wholesale: no binding reference can
+ * hide in it beyond the ones the annotation itself names.
+ */
+function arrowAnnotationGap(source, returnType) {
+    const parametersEnd = source.getTokenBefore(returnType);
+    const arrow = source.getTokenAfter(returnType, {
+        filter: (token) => token.value === '=>',
+    });
+    if (!parametersEnd || !arrow)
+        return null;
+    const gap = [parametersEnd.range[1], arrow.range[0]];
+    return containsRange(gap, returnType.range) ? { gap, arrow } : null;
+}
+exports.arrowAnnotationGap = arrowAnnotationGap;
+/**
+ * Re-emits `comments` on the far side of the arrow, where a line terminator is
+ * inert, consuming the horizontal whitespace the arrow already had after it so
+ * the body keeps a single separator.
+ */
+function hoistPastArrow(source, arrow, comments) {
+    const indent = indentAt(source, arrow.range[0]);
+    const trailingText = source.text.slice(arrow.range[1]);
+    const [spacing] = /^[ \t]*/.exec(trailingText) ?? [''];
+    const body = (0, replacementSegments_1.joinSegmentBody)(comments.map((comment) => ({
+        text: textOf(source, comment.range),
+        breakAfter: true,
+    })), indent);
+    const rest = trailingText.slice(spacing.length);
+    const separator = LINE_TERMINATOR.test(rest.charAt(0))
+        ? ''
+        : (0, replacementSegments_1.requiresLineBreakAfter)(comments[comments.length - 1])
+            ? `\n${indent}`
+            : ' ';
+    return {
+        range: [arrow.range[1], arrow.range[1] + spacing.length],
+        text: ` ${body}${separator}`,
+    };
+}
+/**
+ * The edits that strip an arrow function's return annotation without leaving a
+ * line terminator in the restricted gap, carrying every comment the strip
+ * strands rather than deleting it (#1877).
+ *
+ * `removal` is the span the calling rule would otherwise delete: it covers the
+ * annotation and may reach further back over the horizontal whitespace ahead of
+ * the `:`. It must lie inside the gap, which it does for any annotation the
+ * caller located on the arrow itself.
+ *
+ * A comment that must own a line is re-emitted past the `=>`, the nearest
+ * position outside the restricted gap that cannot itself begin one; hoisting it
+ * above the enclosing line would anchor an insertion at a column zero that may
+ * sit inside a template literal or JSX text, where the comment would become
+ * content rather than code. A comment that trips no restricted production stays
+ * exactly where it was written, since moving comments gratuitously is its own
+ * regression.
+ *
+ * `null` withholds the fix, for a comment whose meaning is its position and
+ * which cannot stay where it is.
+ */
+function planArrowAnnotationEdits(source, returnType, removal) {
+    const gapInfo = arrowAnnotationGap(source, returnType);
+    if (!gapInfo)
+        return null;
+    const { gap, arrow } = gapInfo;
+    if (!containsRange(gap, removal))
+        return null;
+    const comments = source
+        .getAllComments()
+        .filter((comment) => containsRange(gap, comment.range));
+    const stranded = comments.filter((comment) => containsRange(removal, comment.range));
+    // What the plain deletion would leave between the parameters and the arrow.
+    // A comment left there contributes its own text, so a line comment or a
+    // multi-line block comment shows up here as the line terminator it is.
+    const residue = `${textOf(source, [gap[0], removal[0]])}${textOf(source, [
+        removal[1],
+        gap[1],
+    ])}`;
+    // The plain deletion is kept wherever it already lands a legal gap and
+    // strands nothing, so no output that survives today moves by a byte.
+    if (stranded.length === 0 && !LINE_TERMINATOR.test(residue)) {
+        return [{ range: removal, text: '' }];
+    }
+    // Rewriting the gap collapses the lines it spanned, which moves the line a
+    // directive inside it points at, so the whole fix is withheld rather than
+    // retargeting one. The gap a directive can share with nothing else is left
+    // untouched by the branch above.
+    if (comments.some(isPositionalDirective))
+        return null;
+    const hoisted = comments.filter(replacementSegments_1.requiresOwnLine);
+    const inline = comments
+        .filter((comment) => !(0, replacementSegments_1.requiresOwnLine)(comment))
+        .map((comment) => textOf(source, comment.range));
+    const edits = [
+        { range: gap, text: inline.length === 0 ? ' ' : ` ${inline.join(' ')} ` },
+    ];
+    if (hoisted.length > 0) {
+        edits.push(hoistPastArrow(source, arrow, hoisted));
+    }
+    return edits;
+}
+exports.planArrowAnnotationEdits = planArrowAnnotationEdits;
+/**
+ * ESLint applies a fix whole or not at all, and rejects one whose edits
+ * overlap. Spans planned independently — several annotations, and the bindings
+ * their removal orphans — can only overlap if a premise behind them is wrong,
+ * so an overlap withdraws the fix rather than throwing at apply time.
+ */
+function isDisjoint(edits) {
+    const sorted = [...edits].sort((left, right) => left.range[0] - right.range[0]);
+    return sorted.every((edit, index) => index === 0 || sorted[index - 1].range[1] <= edit.range[0]);
+}
+exports.isDisjoint = isDisjoint;
+//# sourceMappingURL=arrowAnnotationGap.js.map

package/lib/utils/restrictedProductions.d.ts

@@ -0,0 +1,45 @@
+export type RestrictedProduction = 'arrow' | 'throw';
+export type RestrictedBreach = {
+    production: RestrictedProduction;
+    /** 1-indexed line of the token that closes the gap. */
+    line: number;
+    /** The offending text between the two tokens, comments included. */
+    gap: string;
+};
+type Token = {
+    type: string;
+    value: string;
+    range: [number, number];
+};
+type Node = {
+    type: string;
+    range: [number, number];
+} & Record<string, unknown>;
+type ParsedSource = {
+    ast: Node;
+    tokens: Token[];
+} | null;
+/**
+ * `.ts` and `.tsx` are not ordered by permissiveness — only `.ts` accepts
+ * `<T>expr` and only `.tsx` accepts JSX — so a snippet is tried both ways rather
+ * than parsed under a guessed extension. A snippet that parses under neither is
+ * `null`: unparsable text is `fixture-corpus-parsability`'s axis, and reporting
+ * it here would double-count it.
+ */
+export declare function parseForRestrictedProductions(code: string): ParsedSource;
+/**
+ * Every restricted-production breach in `code`, or `null` when it does not parse
+ * at all.
+ *
+ * The gap is measured between TOKENS, so the text it spans is whitespace and
+ * comments and nothing else. That is what makes a block comment carrying a line
+ * terminator indistinguishable from a raw newline here — which is the whole
+ * point, since it is indistinguishable to the grammar too.
+ */
+export declare function restrictedProductionBreaches(code: string): RestrictedBreach[] | null;
+/**
+ * The non-comment token stream, used to prove a planted comment changed nothing
+ * but comments. `null` when the text does not parse.
+ */
+export declare function tokenSignatureOf(code: string): string | null;
+export {};

package/lib/utils/restrictedProductions.js

@@ -0,0 +1,233 @@
+"use strict";
+var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    var desc = Object.getOwnPropertyDescriptor(m, k);
+    if (!desc || ("get" in desc ? !m.__esModule : desc.writable || desc.configurable)) {
+      desc = { enumerable: true, get: function() { return m[k]; } };
+    }
+    Object.defineProperty(o, k2, desc);
+}) : (function(o, m, k, k2) {
+    if (k2 === undefined) k2 = k;
+    o[k2] = m[k];
+}));
+var __setModuleDefault = (this && this.__setModuleDefault) || (Object.create ? (function(o, v) {
+    Object.defineProperty(o, "default", { enumerable: true, value: v });
+}) : function(o, v) {
+    o["default"] = v;
+});
+var __importStar = (this && this.__importStar) || function (mod) {
+    if (mod && mod.__esModule) return mod;
+    var result = {};
+    if (mod != null) for (var k in mod) if (k !== "default" && Object.prototype.hasOwnProperty.call(mod, k)) __createBinding(result, mod, k);
+    __setModuleDefault(result, mod);
+    return result;
+};
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.tokenSignatureOf = exports.restrictedProductionBreaches = exports.parseForRestrictedProductions = void 0;
+const tsParser = __importStar(require("@typescript-eslint/parser"));
+/**
+ * Restricted productions: the places the ECMAScript grammar forbids a
+ * LineTerminator, and where `@typescript-eslint/parser` accepts one anyway.
+ *
+ * A fixer that leaves — or carries — a line break into one of these gaps emits
+ * text no engine will run, and NOTHING else in this repo's pipeline says so.
+ * Every parse-based guard (`fixture-corpus-parsability`, `fix-fixpoint-closure`'s
+ * fatal check, `fix-orphan-binding-closure`'s `message.fatal` gate, the agora
+ * `fix: true` sweep) reads the broken text as clean, because the parser they all
+ * share is the one that accepts it. #1964 shipped through every one of them.
+ *
+ * WHICH productions belong here is MEASURED, not copied from the spec. The
+ * grammar lists seven; only two are detectable here, because for the rest
+ * `@typescript-eslint/parser` already agrees with V8:
+ *
+ *   | production                 | parser  | V8      | detectable here     |
+ *   | -------------------------- | ------- | ------- | ------------------- |
+ *   | `ArrowParameters [] =>`    | accepts | rejects | YES                 |
+ *   | `throw []`                 | accepts | rejects | YES                 |
+ *   | `async [] (params) =>`     | rejects | rejects | no — parser sees it |
+ *   | `async [] method()`        | rejects | rejects | no — parser sees it |
+ *   | `yield [] *`               | rejects | rejects | no — parser sees it |
+ *   | postfix `++` / `--`        | rejects | rejects | no — parser sees it |
+ *   | `return` / `yield` / label | ASI     | ASI     | no — both insert `;` |
+ *
+ * The last row is the one worth stating plainly: for `return`, `yield`,
+ * `break`/`continue` with a label and `async function`, the parser applies
+ * automatic semicolon insertion exactly as V8 does, so the two never disagree
+ * and there is no divergence to detect. The rows the parser rejects are already
+ * fatal to every parse-based guard, so they need no help from this module.
+ *
+ * `src/tests/restricted-production-closure.test.ts` re-measures that table on
+ * every run: an arm that stops being redundant (a parser upgrade turning a
+ * "rejects" into an "accepts") fails there rather than silently going unchecked.
+ */
+/**
+ * Every character the syntactic grammar counts as a LineTerminator, by code
+ * point rather than as a regular expression: U+2028 and U+2029 terminate a line
+ * in JavaScript SOURCE too, so a literal holding them cannot be written here
+ * without breaking this file.
+ */
+const LINE_TERMINATOR_CODES = new Set([0x0a, 0x0d, 0x2028, 0x2029]);
+const hasLineTerminator = (text) => {
+    for (let index = 0; index < text.length; index++) {
+        if (LINE_TERMINATOR_CODES.has(text.charCodeAt(index)))
+            return true;
+    }
+    return false;
+};
+const PARSE_OPTIONS = {
+    ecmaVersion: 2022,
+    sourceType: 'module',
+    range: true,
+    loc: true,
+    comment: true,
+    tokens: true,
+};
+/**
+ * `.ts` and `.tsx` are not ordered by permissiveness — only `.ts` accepts
+ * `<T>expr` and only `.tsx` accepts JSX — so a snippet is tried both ways rather
+ * than parsed under a guessed extension. A snippet that parses under neither is
+ * `null`: unparsable text is `fixture-corpus-parsability`'s axis, and reporting
+ * it here would double-count it.
+ */
+function parseForRestrictedProductions(code) {
+    for (const jsx of [true, false]) {
+        try {
+            const ast = tsParser.parse(code, {
+                ...PARSE_OPTIONS,
+                ecmaFeatures: { jsx },
+            });
+            if (ast.tokens)
+                return { ast, tokens: ast.tokens };
+        }
+        catch {
+            continue;
+        }
+    }
+    return null;
+}
+exports.parseForRestrictedProductions = parseForRestrictedProductions;
+function visit(node, callback) {
+    if (!node || typeof node !== 'object')
+        return;
+    const record = node;
+    if (typeof record.type === 'string' && Array.isArray(record.range)) {
+        callback(record);
+    }
+    for (const [key, value] of Object.entries(record)) {
+        // `parent` is a back-edge on some node shapes and would loop forever.
+        if (key === 'parent')
+            continue;
+        if (Array.isArray(value)) {
+            for (const item of value)
+                visit(item, callback);
+        }
+        else if (value && typeof value === 'object') {
+            visit(value, callback);
+        }
+    }
+}
+/** Index of the last token ending at or before `position`. */
+function lastTokenIndexBefore(tokens, position) {
+    let low = 0;
+    let high = tokens.length - 1;
+    let found = -1;
+    while (low <= high) {
+        const middle = (low + high) >> 1;
+        if (tokens[middle].range[1] <= position) {
+            found = middle;
+            low = middle + 1;
+        }
+        else {
+            high = middle - 1;
+        }
+    }
+    return found;
+}
+const lineAt = (code, position) => code.slice(0, position).split('\n').length;
+/**
+ * Every restricted-production breach in `code`, or `null` when it does not parse
+ * at all.
+ *
+ * The gap is measured between TOKENS, so the text it spans is whitespace and
+ * comments and nothing else. That is what makes a block comment carrying a line
+ * terminator indistinguishable from a raw newline here — which is the whole
+ * point, since it is indistinguishable to the grammar too.
+ */
+function restrictedProductionBreaches(code) {
+    const parsed = parseForRestrictedProductions(code);
+    if (!parsed)
+        return null;
+    const { ast, tokens } = parsed;
+    const breaches = [];
+    const record = (production, from, to) => {
+        const gap = code.slice(from, to);
+        if (!hasLineTerminator(gap))
+            return;
+        breaches.push({ production, line: lineAt(code, to), gap });
+    };
+    visit(ast, (node) => {
+        if (node.type === 'ArrowFunctionExpression') {
+            const body = node.body;
+            if (!body)
+                return;
+            /**
+             * The arrow token is the LAST `=>` before the body, never the first: a
+             * default parameter may itself be an arrow, and its `=>` sits inside this
+             * node's range.
+             *
+             * Taking the token immediately before it is also what makes a TypeScript
+             * return annotation fall out correctly. The grammar forbids the break
+             * between the SIGNATURE and `=>`, and the annotation is part of the
+             * signature — `() \n : T => 1` is legal and `(): T \n => 1` is not, which
+             * is exactly the pair this comparison distinguishes.
+             */
+            const end = lastTokenIndexBefore(tokens, body.range[0]);
+            for (let index = end; index >= 0; index--) {
+                if (tokens[index].range[1] <= node.range[0])
+                    break;
+                if (tokens[index].value !== '=>')
+                    continue;
+                if (index > 0) {
+                    record('arrow', tokens[index - 1].range[1], tokens[index].range[0]);
+                }
+                break;
+            }
+            return;
+        }
+        if (node.type === 'ThrowStatement' && node.argument) {
+            // The keyword opens the statement, so it is the token after the last one
+            // that ends at or before the statement's start.
+            const index = lastTokenIndexBefore(tokens, node.range[0]) + 1;
+            const keyword = tokens[index];
+            if (!keyword || keyword.value !== 'throw')
+                return;
+            /**
+             * The parser does not reject the breach, but it does RECOVER from it: it
+             * emits a zero-width token where the argument should have been and hands
+             * back a `ThrowStatement` whose argument is an empty node. Measuring the
+             * gap to that phantom would measure nothing at all, so the width filter
+             * is what makes this arm detect anything.
+             */
+            const next = tokens
+                .slice(index + 1)
+                .find((token) => token.range[1] > token.range[0]);
+            if (!next)
+                return;
+            record('throw', keyword.range[1], next.range[0]);
+        }
+    });
+    return breaches;
+}
+exports.restrictedProductionBreaches = restrictedProductionBreaches;
+/**
+ * The non-comment token stream, used to prove a planted comment changed nothing
+ * but comments. `null` when the text does not parse.
+ */
+function tokenSignatureOf(code) {
+    const parsed = parseForRestrictedProductions(code);
+    if (!parsed)
+        return null;
+    return parsed.tokens.map((token) => `${token.type} ${token.value}`).join(' ');
+}
+exports.tokenSignatureOf = tokenSignatureOf;
+//# sourceMappingURL=restrictedProductions.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@blumintinc/eslint-plugin-blumint",
-  "version": "1.20.143",
+  "version": "1.20.145",
   "description": "Custom eslint rules for use within BluMint",
   "author": {
     "name": "Brodie McGuire",

package/release-manifest.json

@@ -1,4 +1,48 @@
 [
+  {
+    "version": "1.20.145",
+    "date": "2026-08-12T16:05:12.174Z",
+    "rules": [
+      {
+        "name": "no-always-true-false-conditions",
+        "changeType": "fix",
+        "issues": [
+          1973
+        ],
+        "summary": "accept a literal loop test the body can exit (closes #1973)"
+      },
+      {
+        "name": "no-redundant-annotation-assertion",
+        "changeType": "fix",
+        "issues": [
+          1972
+        ],
+        "summary": "do not treat unresolved types as identical (closes #1972)"
+      },
+      {
+        "name": "no-undefined-null-passthrough",
+        "changeType": "fix",
+        "issues": [
+          1974
+        ],
+        "summary": "stop reporting the identity function (closes #1974)"
+      }
+    ]
+  },
+  {
+    "version": "1.20.144",
+    "date": "2026-08-12T12:16:01.495Z",
+    "rules": [
+      {
+        "name": "no-redundant-annotation-assertion",
+        "changeType": "fix",
+        "issues": [
+          1969
+        ],
+        "summary": "carry a stranded comment past the arrow (closes #1969)"
+      }
+    ]
+  },
   {
     "version": "1.20.143",
     "date": "2026-08-12T07:48:25.970Z",