[3.1.3] - 2026-05-03

3.1.4

Patch Changes

• #141 38ab670 Thanks @ofri-peretz! - fix: remove false meta.fixable: 'code' declarations from 21 rules that had no fix() function

  Rules that declared fixable: 'code' in their ESLint meta without an actual fix() implementation would show the ⚡ auto-fix icon in editors and CI formatters but apply no change when --fix was run. This patch removes the misleading declaration from:

  • browser-security/no-clickjacking
  • import-next/first, named, no-barrel-import, no-import-module-exports, no-namespace
  • node-security/no-buffer-overread, no-unsafe-dynamic-require, no-zip-slip
  • react-features/react-no-inline-functions
  • reliability/no-jsdoc-terminator-in-example (uses suggest, not auto-fix; corrected to hasSuggestions: true only)
  • secure-coding/no-directive-injection, no-electron-security-issues, no-graphql-injection, no-improper-sanitization, no-improper-type-validation, no-ldap-injection, no-unchecked-loop-condition, no-unlimited-resource-allocation, no-weak-password-recovery, no-xpath-injection

• #143 213cde1 Thanks @ofri-peretz! - fix(no-missing-null-checks): eliminate 53 false positives via three new narrowing patterns

  Rules that were recognized as null guards are now correctly identified as safe:

  1. Truthy if guard — if (obj) { obj.prop } — direct truthy check proves non-null. Also covers chains: if (response) protects response.data.items.
  2. Short-circuit AND — obj && obj.prop — right side of && only runs when left is truthy.
  3. Ternary consequent — obj ? obj.prop : fallback — truthy test guards the consequent.

  Also: bumped beforeAll timeout to 30 seconds in 7 compatibility test files (__compatibility__/*.spec.ts). Native-addon packages routinely exceed the previous 10-second default on a cold ESM load.

• Updated dependencies [736a5fe]:

  • @interlace/eslint-devkit@1.4.1

Bug Fixes

• no-missing-null-checks: exempt provably-non-null identifiers (built-in singletons like Math, JSON, console, error classes; catch-clause params; constructor results; top-level imports) from the null-check requirement. Eliminates a large class of false positives without weakening real coverage.
• no-unhandled-promise: refined detection (see source diff).

3.1.2 (2026-02-09)

This was a version bump only for eslint-plugin-reliability to align it with other projects, there were no code changes.

[3.1.0] - 2026-02-08

This was a version bump only for eslint-plugin-reliability to align it with other projects, there were no code changes.

[3.0.4] - 2026-02-08

Bug Fixes

• align codecov component IDs with full package names (2831b968)

Documentation

• fix changelog header format across all packages (c3a15082)

❤️ Thank You

• Ofri Peretz

[3.0.3] - 2026-02-06

Bug Fixes

• align codecov component names and update docs components (0a59a86c)

❤️ Thank You

• Ofri Peretz

[3.0.2] - 2026-02-02

This was a version bump only for eslint-plugin-reliability to align it with other projects, there were no code changes.

Changelog

All notable changes to eslint-plugin-reliability will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

Documentation

• 📘 Launched new documentation site: eslint.interlace.tools
• 📝 Achieved 100% documentation parity (both .md and .mdx files)

[3.0.1] - 2026-02-02

This was a version bump only for eslint-plugin-reliability to align it with other projects, there were no code changes.

[3.0.0] - 2026-02-02

This was a version bump only for eslint-plugin-reliability to align it with other projects, there were no code changes.

[1.0.0] - 2026-01-26

Added

• Initial stable release with 8 reliability rules
• LLM-optimized error messages for AI-assisted development
• 100% test coverage across all rules
• ESLint 9 flat config support
• TypeScript type definitions for all rule options

Rules

Error Handling (4 rules)

Runtime Safety (4 rules)

Presets

• recommended - Balanced reliability checks (4 rules as warnings)

Known Limitations

Documented in docs/KNOWN-LIMITATIONS.md:

• no-unhandled-promises: Promises in callbacks or async iterators may be missed
• no-silent-errors: Intentional suppression vs. actual swallowing is hard to distinguish
• no-missing-null-checks: Business-logic guarantees not in types can trigger false positives