v1.9.3

This release updates bes-relevance-lint to bigfix-relevance-analyzer 1.19.0. That version adds five rules, and this release maps each of them to a code.

⚠️ Upgrade notes

• Requires bigfix-relevance-analyzer >= 1.19.0 on Python 3.11 or newer (was >= 1.16.3). The published hook installs it. If you define bes-relevance-lint as repo: local with language: python, raise the version in additional_dependencies.
• bes-relevance-lint can now fail where it used to pass, through the new E612 and E613 errors. Disable either with --disable if needed.
• Some E603 findings are now E611. A plural operand where the engine requires a single value used to be reported as a general type error. If your config passes --disable E603, these findings will now fail the hook as E611 until you also disable E611.

Added (bes-relevance-lint)

• E611, a new error: a plural operand where the engine requires a single value, which it refuses before evaluating anything. Where it is safe, a unique value of (or singular-aggregate) rewrite is printed as a suggested fix.
• E612, a new error: an ActionScript { with anything after it on its line and no } to close it there, which fails the action.
• E613, a new error: a <?Relevance with no closing ?>, so its relevance was never linted.
• E614, a new error, off by default: a BES file that is not well-formed XML. bes-schema-validate still owns file validity, so unparsable XML stays skipped here unless you pass --enable E614.
• W607, a new warning: a relevance code fence in markdown that is never closed. Only seen when you run the hook by hand on markdown.

Full Changelog: v1.9.2...v1.9.3