@timmo001/oxlint-rules 0.6.3 → 0.6.5

package/README.md

@@ -7,19 +7,19 @@ locally owned generic rules under `timmo` and Effect rules under
 
 This package targets the latest stable Oxlint toolchain. Oxlint's
 [JavaScript plugin API is alpha](https://oxc.rs/docs/guide/usage/linter/config.html)
-and is outside its semver guarantees, so each rules release declares the exact
-`oxlint` and `@oxlint/plugins` versions it has validated. Older toolchains and
-untested future versions are not part of the support contract.
+and is outside its semver guarantees. Each rules release is validated against
+the Oxlint version pinned in its development dependencies, and declares a caret
+peer range from that version so consumers can take newer Oxlint releases
+without waiting for a rules release. Older toolchains are not supported.
 
 ## Install
 
-Check the published rules package's `peerDependencies` against the official npm
-`latest` versions of `oxlint` and `@oxlint/plugins`. If they differ, a validated
-rules release is needed before upgrading. Do not bypass peer checks or override
-Vite Plus's bundled dependencies to make an unsupported version fit.
+Check that the official npm `latest` versions of `oxlint` and `@oxlint/plugins`
+satisfy the published rules package's `peerDependencies`. Do not bypass peer
+checks or override Vite Plus's bundled dependencies to make an unsupported
+version fit.
 
-Once the versions match, install from npm with the package manager already used
-by the repository:
+Install from npm with the package manager already used by the repository:
 
 ```sh
 bun add --dev --exact @timmo001/oxlint-rules oxlint @oxlint/plugins
@@ -182,24 +182,25 @@ the surrounding test code is linted with the full rule set.
 isolated consumer using the exact toolchain pins from `package.json` and strict
 peer checks. It verifies both recommended configs, diagnostics from all four
 shared namespaces, and valid and invalid type-aware examples. CI runs this
-through the existing package workflow's build step. It also requires matching,
-exact Oxlint development and peer versions.
+through the existing package workflow's build step. It also requires exact
+Oxlint development versions that satisfy the caret peer ranges.
 
 ### Toolchain updates and releases
 
-Renovate's shared preset groups Oxlint, `@oxlint/plugins` and `oxlint-tsgolint`.
-The local rule keeps both development and peer dependencies pinned instead of
-widening peer ranges. For each update:
+Renovate's shared preset groups Oxlint, `@oxlint/plugins` and `oxlint-tsgolint`
+and widens peer ranges. The local rule keeps the development dependencies
+pinned. For each update:
 
 1. Verify the official npm `latest` versions and Oxlint's tsgolint peer
    requirement. Keep Oxlint and plugins on the same latest version and regenerate
    the lockfile with the selected tsgolint version.
 2. Run the checks and package dry-runs above. Fix any API incompatibility before
    accepting the new pins; do not disable rules or bypass peer failures.
-3. Review and merge the validated update. Consumers need a separately approved
-   version bump and release to receive the new peer contract. Publishing a
-   GitHub release triggers the existing npm and JSR workflows; both must succeed
-   before the update is available to consumers.
+3. Review and merge the validated update. Consumers already in the peer range
+   don't need a rules release; raise the peer floor and release only when the
+   rules need a newer Oxlint. Publishing a GitHub release triggers the existing
+   npm and JSR workflows; both must succeed before the update is available to
+   consumers.
 
 Advance `vendor/anti-slop` only by updating its Git submodule commit. Keep its
 source and MIT licence unchanged, then run the full package checks so both

package/dist/configs/recommended-effect.d.ts

@@ -0,0 +1,5 @@
+import type { OxlintConfig } from "oxlint";
+
+declare const config: OxlintConfig;
+
+export default config;

package/dist/configs/recommended.d.ts

@@ -0,0 +1,5 @@
+import type { OxlintConfig } from "oxlint";
+
+declare const config: OxlintConfig;
+
+export default config;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@timmo001/oxlint-rules",
-  "version": "0.6.3",
+  "version": "0.6.5",
   "description": "Shared Oxlint plugins and configs with optional Effect rules.",
   "type": "module",
   "license": "Apache-2.0",
@@ -16,8 +16,14 @@
     "./upstream/effect": "./dist/upstream/effect.js",
     "./generic": "./dist/generic/index.js",
     "./effect": "./dist/effect/index.js",
-    "./configs/recommended": "./dist/configs/recommended.js",
-    "./configs/recommended-effect": "./dist/configs/recommended-effect.js"
+    "./configs/recommended": {
+      "types": "./dist/configs/recommended.d.ts",
+      "default": "./dist/configs/recommended.js"
+    },
+    "./configs/recommended-effect": {
+      "types": "./dist/configs/recommended-effect.d.ts",
+      "default": "./dist/configs/recommended-effect.js"
+    }
   },
   "files": [
     "dist",
@@ -49,14 +55,14 @@
     "typecheck": "tsc --noEmit"
   },
   "peerDependencies": {
-    "@oxlint/plugins": "1.88.0",
-    "oxlint": "1.88.0"
+    "@oxlint/plugins": "^1.91.0",
+    "oxlint": "^1.91.0"
   },
   "devDependencies": {
-    "@oxlint/plugins": "1.88.0",
+    "@oxlint/plugins": "1.93.0",
     "@types/bun": "^1.3.14",
-    "oxlint": "1.88.0",
-    "oxlint-tsgolint": "7.0.2004",
+    "oxlint": "1.93.0",
+    "oxlint-tsgolint": "7.0.2006",
     "prettier": "^3.9.5",
     "skills-ref": "0.1.5",
     "typescript": "^7.0.0"

package/skills/install-timmo-oxlint-rules/SKILL.md

@@ -15,11 +15,11 @@ description: >-
    the user names another target.
 3. Preserve existing ignores, overrides, plugins, and repository-owned rules.
    Verify the official npm `latest` versions of `oxlint` and `@oxlint/plugins`.
-   They must match each other and the exact peers of the selected rules release.
-   Support is latest-only: if the published peer contract has not caught up,
-   report the pending rules release instead of widening peers or bypassing
-   package-manager failures. Do not force upgrades of Vite Plus's transitive
-   dependencies or assume its bundled plugins satisfy this contract.
+   They must match each other and satisfy the peer ranges of the selected rules
+   release. If they fall outside those ranges, report the pending rules release
+   instead of bypassing package-manager failures. Do not force upgrades of Vite
+   Plus's transitive dependencies or assume its bundled plugins satisfy this
+   contract.
 
 ## Package
 

package/skills/release-oxlint-rules/SKILL.md

@@ -18,12 +18,15 @@ description: >-
    minor, patch, or exact version. Ask only when the release level is missing.
    Do not add a `v` prefix when the repository's existing tags omit it.
 3. Verify official npm `latest` metadata for `oxlint`, `@oxlint/plugins` and
-   `oxlint-tsgolint`. Support is latest-only: keep Oxlint and plugins on the same
-   latest version, pin their development and peer dependencies exactly, and
-   select the latest tsgolint satisfying Oxlint's peer requirement. Regenerate
-   `bun.lock`. The shared Renovate preset groups this toolchain; the local rule
-   keeps peers pinned. Resolve compatibility failures before releasing, without
-   widening peers, disabling rules or forcing transitive dependency upgrades.
+   `oxlint-tsgolint`. Keep Oxlint and plugins on the same latest version, pinned
+   exactly in development dependencies, and select the latest tsgolint
+   satisfying Oxlint's peer requirement. Declare the peers as a caret range
+   (`^1.91.0`) so consumers can move to newer Oxlint releases without waiting
+   for a release here; raise its floor only when the rules need a newer Oxlint.
+   Regenerate `bun.lock`. The shared Renovate preset groups this toolchain and
+   widens peer ranges; the local rule pins only the development dependencies.
+   Resolve compatibility failures before releasing, without disabling rules or
+   forcing transitive dependency upgrades.
 4. Update the version in `package.json` and `jsr.json` only when a version bump
    is requested. Before committing, run `mise run check`, `mise run build`,
    `mise run test:package`, `npm pack --dry-run`, and
@@ -45,6 +48,4 @@ description: >-
    succeed.
 8. Report the release URL, version commit, validation results, and npm and JSR
    publication conclusions. Do not report the release as complete while either
-   publication job is pending or failed. A merged toolchain update alone does
-   not deliver its peer contract to consumers; preparation ends with publication
-   pending until a version bump and release are approved.
+   publication job is pending or failed.