chore: version packages - #1
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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
react-doctor@0.2.15
Patch Changes
#605
4861f37Thanks @rayhanadev! - Update the dead-code analysis engine (deslop-js) to0.0.14so the published CLI's unused-file / dead-code detection runs on the latest release. The CLI previously pinned^0.0.13while the internal core engine was already on0.0.14; this aligns both on a single version and drops the duplicate from the lockfile.#607
5dff3b5Thanks @rayhanadev! - Fixreact-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 withextendsstripped — so the run finished and printed results, but the orphanedsetIntervalkept the Node event loop alive and the process never returned control to the shell. The batch loop now clears the timer in afinally, so it's always cleaned up even when a batch throws. See #599.#601
5f7cc7cThanks @rayhanadev! - Publish a JSON Schema forreact-doctor.config.jsonathttps://react.doctor/schema/config.json.Pointing
$schemaat 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.tsviapnpm build:schemaand checked intopackages/website/public/schema/config.json.#606
fe01e57Thanks @rayhanadev! - Redact secrets and PII from diagnostic output. Every diagnostic'smessage/helpis 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
@react-doctor/api@0.2.15
Patch Changes
@react-doctor/core@0.2.15
Patch Changes