eslint-plugin-test-governance 0.13.2 → 0.14.0

package/CHANGELOG.md

@@ -6,6 +6,93 @@ All notable changes to this project are documented here. The format follows
 
 ## [Unreleased]
 
+## [0.14.0] - 2026-11-10
+
+### Fixed
+
+- Treat arguments passed to Mocha, Cypress and WebdriverIO `this.skip()` as ignored, so a false
+  argument cannot hide an unconditional skip or explain a conditional one.
+- Accept OpenProject short links under installation base paths and semantic work-package IDs,
+  while rejecting their zero-number placeholders.
+- Read ticket IDs from URLs matched by custom patterns, rejecting zero IDs without mistaking
+  unrelated title suffixes or query values for placeholders.
+- Recognize Vitest function titles without analyzing the name function as an executed body,
+  and preserve options, runtime contexts and ticket-to-metadata suggestions.
+- Find commented-out tests through namespace aliases and recognize CommonJS-only test files,
+  while retaining protection against reassigned helpers and suite-hook aliases.
+
+### Added
+
+- Add the opt-in `limit-retries` rule for Playwright, Jest, Vitest, Mocha, Cypress and WebdriverIO.
+  It checks readable native retry counts against the shared `maxRetries` setting (default `2`),
+  independently of retry ticket requirements. Framework configs leave the rule off.
+- Recognize chained Mocha retry setters such as `it('example', fn).retries(3)` for retry ticketing
+  as well as retry limits.
+
+### Removed
+
+- **Breaking:** remove `lifecycleTags`, `states.new`, `states.quarantined` and their tag overrides.
+  Use explicit `customStates` mappings for any tag that should require a ticket. Removed settings
+  fail with migration instructions; native runner states keep their existing defaults.
+- Remove the built-in checks for `@new` on a skipped test and for `@new` combined with `@quarantined`.
+  Custom tags have no prescribed lifecycle or conflicts.
+
+### Changed
+
+- **Breaking:** rename `no-conflicting-states` to `consistent-tag-names`. It retains case fixes and
+  spelling checks for `customStates` and `knownTags`; the old rule name fails with migration guidance.
+  See the [upgrade guide](docs/upgrading.md#upgrading-to-014-custom-tag-states).
+
+- Reorganize documentation around a complete first lint run, with separate configuration, framework
+  and troubleshooting references. Clarify supported version combinations, optional states, example
+  settings and recent upgrade actions; retain existing README section links.
+
+## [0.13.3] - 2026-11-09
+
+### Fixed
+
+- Vitest conditional factories can clear an earlier skip in a modifier chain. Runtime context methods
+  retain their state through TypeScript wrappers on the receiver or method.
+- Mutation detection follows wrapped references and aliases, and recognizes writes through the global
+  `Object` and `Reflect` mutation methods without treating shadowed helpers as those built-ins.
+- Retry counts are read through local constants and object members, with effective properties after
+  spreads and overrides. Unread spreads remain possible retries unless every relevant count is known.
+- Commented-out tests no longer hide a broken marker or a disallowed note behind another valid marker.
+- Negative numeric and bigint template interpolations, `void`, and unshadowed `undefined`, `NaN` and
+  `Infinity` retain their rendered text when checking tag boundaries.
+- Mutable constant objects and arrays no longer supply stale tag or annotation values after detected
+  property writes, deletion, array mutation or writes through a local alias.
+- Runtime context methods keep their original test owner inside nested subtests. Vitest skip notes
+  supplied through constants remain unconditional skips.
+- Test callees retain their meaning through TypeScript assertions and type instantiations, sequence
+  expressions and defaulted local destructuring. Repeated conditional factories use the final condition.
+- Nested conditional returns and throws, and conditional loop breaks and continues, guard later runtime
+  skips. Jest retry calls are recognized through CommonJS object bindings and method aliases, including
+  bound arguments.
+- Primitive template interpolations retain their rendered text when checking tag boundaries. Object
+  prototype setters do not count as own tag or metadata properties, and suggestions use computed keys
+  for metadata named `__proto__`.
+- Test functions are read through aliases of whole modules, local destructuring, bound functions and
+  nested conditional selections. Reassigning an alias to a helper no longer leaves it treated as a test.
+- Runtime test contexts and their methods keep their meaning through chains of aliases, `bind()` and
+  default parameter values. Arguments supplied by `bind()` retain their condition and reason, and a
+  bound title no longer gives a diagnostic whose end is before its start.
+- A runtime skip in a conditional loop, or after a conditional early exit inside a nested block, is
+  read as conditional. A TypeScript assertion around a literal boolean keeps that boolean's meaning.
+- With the retry state on, Jest's retry calls are read through renamed and namespace imports, and a
+  Mocha describe chosen by a condition still supplies its suite context for `this.retries()`.
+- Chains of constants retain their tags, details and annotation tickets. An unread computed property
+  no longer leaves an earlier member of a tag object treated as certain.
+- Tags from literal and nested template interpolations are checked using the rendered text's boundaries,
+  so joining text around an `@` doesn't invent a state tag. Plain Vitest tags written as templates count
+  like quoted strings. Cyclic constant and template definitions remain unread instead of recursing.
+- `annotations.only` checks every supplied issue ticket, including an invalid one next to a valid one.
+- The commented-out-test rule recognizes renamed test imports.
+- Removing an orphaned marker removes its complete line with CR or Unicode line endings too.
+- A suggestion to add another state's marker no longer copies a ticket that state's format rejects.
+- Suggestions that move a ticket into annotations escape line breaks in the annotation type or key,
+  keeping the suggested JavaScript valid.
+
 ## [0.13.2] - 2026-11-08
 
 ### Fixed
@@ -598,7 +685,9 @@ First release.
 - Support for ESLint 9 and 10 flat config, JavaScript and TypeScript test files, `.extend()`
   fixtures, describe blocks, runtime skips and tags in titles or the `tag` option.
 
-[Unreleased]: https://github.com/Huldoser/eslint-plugin-test-governance/compare/v0.13.2...HEAD
+[Unreleased]: https://github.com/Huldoser/eslint-plugin-test-governance/compare/v0.14.0...HEAD
+[0.14.0]: https://github.com/Huldoser/eslint-plugin-test-governance/compare/v0.13.3...v0.14.0
+[0.13.3]: https://github.com/Huldoser/eslint-plugin-test-governance/compare/v0.13.2...v0.13.3
 [0.13.2]: https://github.com/Huldoser/eslint-plugin-test-governance/compare/v0.13.1...v0.13.2
 [0.13.1]: https://github.com/Huldoser/eslint-plugin-test-governance/compare/v0.13.0...v0.13.1
 [0.13.0]: https://github.com/Huldoser/eslint-plugin-test-governance/compare/v0.12.1...v0.13.0