Skip to content

chore: version packages - #1

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: version packages#1
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

Copy link
Copy Markdown

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

eslint-plugin-react-doctor@0.2.15

Patch Changes

  • Updated dependencies []:
    • oxlint-plugin-react-doctor@0.2.15

react-doctor@0.2.15

Patch Changes

  • #605 4861f37 Thanks @rayhanadev! - Update the dead-code analysis engine (deslop-js) to 0.0.14 so the published CLI's unused-file / dead-code detection runs on the latest release. The CLI previously pinned ^0.0.13 while the internal core engine was already on 0.0.14; this aligns both on a single version and drops the duplicate from the lockfile.

  • #607 5dff3b5 Thanks @rayhanadev! - Fix react-doctor --staged (and other scans) hanging after the diagnostics summary is already printed. When an adopted lint config crashed oxlint on the first attempt, the oxlint runner's per-batch progress timer was left running while the scan silently retried with extends stripped — so the run finished and printed results, but the orphaned setInterval kept the Node event loop alive and the process never returned control to the shell. The batch loop now clears the timer in a finally, so it's always cleaned up even when a batch throws. See #599.

  • #601 5f7cc7c Thanks @rayhanadev! - Publish a JSON Schema for react-doctor.config.json at https://react.doctor/schema/config.json.

    Pointing $schema at the URL enables editor autocomplete, hover docs from the interface JSDoc, and typo warnings in any editor that understands JSON Schema. Closes #497.

    {
      "$schema": "https://react.doctor/schema/config.json",
      "lint": true
    }

    The schema is generated from packages/core/src/types/config.ts via pnpm build:schema and checked into packages/website/public/schema/config.json.

  • #606 fe01e57 Thanks @rayhanadev! - Redact secrets and PII from diagnostic output. Every diagnostic's message/help is now scrubbed for API keys, tokens, private keys, JWTs, credentialed URLs, and email addresses before it reaches the terminal, the JSON report, or the score API — so react-doctor never echoes or transmits a secret embedded in your source. Provider tokens keep their non-secret, type-identifying prefix (e.g. sk_live_<redacted>, ghp_<redacted>) so you can tell which credential leaked while the secret itself stays masked.

  • Updated dependencies []:

    • oxlint-plugin-react-doctor@0.2.15

oxlint-plugin-react-doctor@0.2.15

@react-doctor/api@0.2.15

Patch Changes

  • Updated dependencies []:
    • @react-doctor/core@0.2.15

@react-doctor/core@0.2.15

Patch Changes

  • Updated dependencies []:
    • oxlint-plugin-react-doctor@0.2.15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Publish a JSON schema for react-doctor.config.json

0 participants