eslint-plugin-operability 3.0.6 → 3.0.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +26 -0
- package/package.json +1 -1
- package/src/index.js +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,31 @@
|
|
|
1
1
|
## [3.0.5] - 2026-02-08
|
|
2
2
|
|
|
3
|
+
## 3.0.7
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- [#200](https://github.com/ofri-peretz/eslint/pull/200) [`02e0baf`](https://github.com/ofri-peretz/eslint/commit/02e0baf7a4e8ba83e8b2ec2b82169f733e4f4d87) Thanks [@ofri-peretz](https://github.com/ofri-peretz)! - fix: republish `recommended` preset with the correct plugin namespace
|
|
8
|
+
|
|
9
|
+
The published builds of `eslint-plugin-maintainability` and
|
|
10
|
+
`eslint-plugin-operability` shipped a `recommended` config whose plugin KEY
|
|
11
|
+
(`@interlace/maintainability`) did not match its rule PREFIX
|
|
12
|
+
(`@interlace/maintainability/maintainability/…` — doubled). ESLint cannot
|
|
13
|
+
resolve that, so spreading `...configs.recommended` throws
|
|
14
|
+
"could not find plugin" the moment a consumer lints a file — under both
|
|
15
|
+
ESLint 9 and 10.
|
|
16
|
+
|
|
17
|
+
The source was corrected in the 2026-05-16 namespace cleanup (alongside
|
|
18
|
+
`react-features`, which has since been republished via other changesets), but
|
|
19
|
+
these two plugins were never bumped — so npm still serves the broken builds and
|
|
20
|
+
they are the only two doubled-namespace plugins still unfixed downstream. This
|
|
21
|
+
republishes them from the corrected source.
|
|
22
|
+
|
|
23
|
+
Regression lock: `packages/eslint-config-interlace/src/ecosystem-integrity.test.ts`
|
|
24
|
+
loads every plugin's every config preset into a real ESLint instance and fails
|
|
25
|
+
if any rule→plugin reference cannot be resolved. Run it against the built
|
|
26
|
+
`dist/` in the release pipeline (pre-publish) to also catch a stale-artifact
|
|
27
|
+
publish — the failure mode that let these two ship broken.
|
|
28
|
+
|
|
3
29
|
## 3.0.6
|
|
4
30
|
|
|
5
31
|
### Patch Changes
|
package/package.json
CHANGED