eslint-plugin-sequelize-security@0.3.2

0.3.2

Patch Changes

• #407 5ecf4d1 Thanks @ofri-peretz! - Correct the declared ESLint floor: ^8.0.0 → ^8.40.0.

  context.sourceCode landed in ESLint 8.40. The shared devkit reads it without a
  fallback and 20 plugins read it directly, so on ESLint 8.0–8.39 the install
  resolved cleanly and then every rule threw
  Cannot read properties of undefined (reading 'ast') at lint time — npm reported
  nothing, because the manifest claimed the version was supported.

  Measured on 8.0.0 / 8.39.0 (throw on load) versus 8.40.0 / 8.57.1 / 9.0.0 /
  9.39.2 / 10.8.0 (all produce the expected finding). No runtime behaviour
  changes; this only makes the manifest match what the code can actually run.

• #423 4794017 Thanks @ofri-peretz! - Correct the ESLint peer range shown in the README Compatibility table.

  The manifest floor moved to 8.40.0, but every package README still advertised
  ^8.0.0 || ^9.0.0 || ^10.0.0. The README is what npm renders on the package
  page, so the requirement consumers actually read disagreed with the one npm
  enforced: an install on 8.39.x warns about a peer conflict while the README
  says that version is supported.

  The range was missed by the original sweep because a markdown table escapes
  the union as \|\|, so a grep for the plain shape matched none of the 29
  files.

  Also updates .agent/rules/readme-structure.md and
  .agent/compatibility-matrix.md, which template this table for new packages,
  and adds a README-vs-manifest assertion to
  scripts/__tests__/eslint-peer-floor.test.ts so the two cannot drift again.

• Updated dependencies [b59e984, 5ecf4d1, 4794017]:

  • @interlace/eslint-devkit@1.11.0