chore: version packages#646
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
9e833d7 to
8281dc0
Compare
8281dc0 to
02b83e5
Compare
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.19
Patch Changes
react-doctor@0.2.19
Patch Changes
#655
d594f69Thanks @rayhanadev! - react-doctor no longer crashes when the--changed-files-fromfile can't be read.--changed-files-from <file>is user input, so an unreadable file — missing, a directory, permission-denied, or a stale pipe/process-substitution descriptor (EBADF, REACT-DOCTOR-V) — is an invocation mistake, not a bug. It now exits non-zero with a clean, single-line message telling you to pass a readable text file, instead of printing the generic "Something went wrong" block and reporting the read failure to Sentry.#654
eab6dc2Thanks @rayhanadev! - react-doctor no longer crashes when a directory can't be enumerated during project discovery.The recursive subproject crawl reads directories best-effort and already skipped ones it couldn't open for permission or missing-path reasons (
EACCES/EPERM/ENOENT/ENOTDIR). It now also skips directories the underlying filesystem rejects outright —EINVALonscandir(REACT-DOCTOR-N, seen on special/virtual mounts), plus symlink loops (ELOOP) and over-long paths (ENAMETOOLONG) — instead of throwing and reporting the environment issue to Sentry. The crawl continues past the unreadable directory.#645
4aadaabThanks @aidenybai! - Two React Native rules no longer false-positive on Expo Universal UI (@expo/ui).@expo/uiis a native UI layer (it delegates to SwiftUI / Jetpack Compose), not React Native's core primitives, so several RN-core assumptions don't hold for its components:rn-no-raw-text: Universal UI's<ListItem>renders its raw string children inside the native headline text area, and its compound slot markers (<ListItem.Leading>,<ListItem.Supporting>,<ListItem.Trailing>) forward strings into native text too — so raw text inside them is safe, unlike React Native's core<View>. The rule now recognizes them as text-handling.rn-no-scrollview-mapped-list: Universal UI's<ScrollView>is a native scroll container; React Native's virtualized lists (FlashList/FlatList) can't compose inside its<Host>tree, and@expo/uiships its own virtualized<List>. The rule no longer flags mapped children inside an@expo/uiScrollView.Both checks are gated on the
@expo/uiimport (root,@expo/ui/swift-ui, or@expo/ui/jetpack-compose, including renamed and namespace imports), so same-named components from other libraries — or with no import — still report.#650
3cc9971Thanks @rayhanadev! - A terminal hangup during an interactive prompt no longer crashes the CLI. When the terminal/PTY backing a prompt goes away mid-read (closing the tab, a dropped SSH/tmux session, sleep/wake), Node raisesread EIOon the raw-mode stdin handle; the CLI now exits cleanly (code 129) instead of surfacing it as a fatal uncaught exception and reporting it to crash telemetry. Genuine stdin errors still funnel to the error reporter unchanged.Updated dependencies []:
oxlint-plugin-react-doctor@0.2.19
@react-doctor/api@0.2.19
Patch Changes
@react-doctor/core@0.2.19
Patch Changes
Note
Low Risk
Diff is version/changelog/changeset housekeeping only; behavioral changes are already merged patch releases documented for npm publish.
Overview
This is a Changesets release PR: it bumps the monorepo from 0.2.18 → 0.2.19, rolls release notes into each package
CHANGELOG, updatespackage.jsonversions, and removes the four consumed.changeset/*.mdentries (no source changes in this diff).react-doctor@0.2.19(documented in its changelog) ships the fixes that were in those changesets: graceful handling when--changed-files-frompoints at an unreadable path; skipping problematic directories during subproject discovery (EINVAL/ELOOP/ENAMETOOLONGonscandir);@expo/ui-aware exemptions forrn-no-raw-textandrn-no-scrollview-mapped-list; and clean exit (129) on terminal hangup during interactive prompts instead of an uncaught crash.eslint-plugin-react-doctor,oxlint-plugin-react-doctor,@react-doctor/core, and@react-doctor/apionly record the version bump and dependency sync.Reviewed by Cursor Bugbot for commit 02b83e5. Bugbot is set up for automated code reviews on this repo. Configure here.