chore: version packages - #805
Merged
Merged
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.5.3
Patch Changes
react-doctor@0.5.3
Patch Changes
#804
022790bThanks @NisargIO! - Clearer Socket supply-chain diagnostics (socket/low-supply-chain-score). When Socket returns a concrete alert, the message now names it — e.g. a critical "known malware" alert, the offending file, and a one-line description — instead of only a bare score; when it doesn't (metric-driven dips like CVE-only scores), the message explains what the failing axis means. The help is now axis-aware: remove a package flagged as compromised, upgrade past known vulnerabilities (npm audit), or vet-and-raise the threshold — rather than a generic "update or replace". The headline leads with the exact failing axis and collapses the redundant "declared as X, scored at X" phrasing (a range now readspkg@floor (lowest version "^x.y.z" allows)). JSON report shape is unchanged (schemaVersion: 1).Updated dependencies []:
oxlint-plugin-react-doctor@0.5.3
@react-doctor/api@0.5.3
Patch Changes
@react-doctor/core@0.5.3
Patch Changes
@react-doctor/language-server@0.5.3
Patch Changes
Note
Low Risk
Release metadata and version bumps only; behavioral change is limited to CLI diagnostic copy for supply-chain findings, not scoring gates or report schema.
Overview
Automated 0.5.3 release: workspace packages move from
0.5.2to0.5.3(react-doctor,eslint-plugin-react-doctor,oxlint-plugin-react-doctor, and internal@react-doctor/*), with matching CHANGELOG entries and consumption of the pending changeset (.changeset/socket-supply-chain-messaging.mdremoved).The only user-facing note in this bump is on
react-doctor@0.5.3(#804):socket/low-supply-chain-scoremessages and help are clearer—concrete Socket alerts when present, axis-specific guidance when scores dip on metrics alone, tighter headlines (including semver floor wording), while JSON report shape staysschemaVersion: 1. Other packages in the PR only record dependency alignment tooxlint-plugin-react-doctor@0.5.3/@react-doctor/core@0.5.3with no additional changelog bullets.Reviewed by Cursor Bugbot for commit c4c5c32. Bugbot is set up for automated code reviews on this repo. Configure here.