chore: version packages

[github-actions]

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.12

Patch Changes

• #570 d917f62 Thanks @aidenybai! - Add the no-prop-types architecture rule. React 19 removed runtime propTypes validation entirely — React no longer reads Component.propTypes, so invalid props that used to log a console warning now pass silently. The rule flags Component.propTypes = { ... } assignments and static propTypes class fields on component-cased identifiers, and is version-gated to React 19+ (requires: ["react:19"]) so projects where propTypes still runs stay quiet. It steers users toward TypeScript prop types plus explicit runtime validation. See #460.

• #582 b2934f9 Thanks @rayhanadev! - Fix a rn-no-raw-text false positive on fbtee translation tags. fbtee's <fbt> / <fbs> (and namespaced children like <fbt:param>) are compile-time translation tags that disappear at build time, so text inside <Text><fbt>…</fbt></Text> is really rendered inside <Text> and is safe on React Native. The rule now treats fbt / fbs as transparent wrappers when every ancestor up to a text-handling component is also transparent, while still reporting raw text when an <fbt> is used outside a <Text> boundary. See #581.

• Updated dependencies [d917f62, d0f5206, b2934f9]:

  • oxlint-plugin-react-doctor@0.2.12

oxlint-plugin-react-doctor@0.2.12

Patch Changes

• #570 d917f62 Thanks @aidenybai! - Add the no-prop-types architecture rule. React 19 removed runtime propTypes validation entirely — React no longer reads Component.propTypes, so invalid props that used to log a console warning now pass silently. The rule flags Component.propTypes = { ... } assignments and static propTypes class fields on component-cased identifiers, and is version-gated to React 19+ (requires: ["react:19"]) so projects where propTypes still runs stay quiet. It steers users toward TypeScript prop types plus explicit runtime validation. See #460.

• #572 d0f5206 Thanks @aidenybai! - Add the react-doctor/no-self-updating-effect rule. It warns when a useEffect / useLayoutEffect lists a state value in its dependency array and the effect body unconditionally calls that state's own useState setter with a value that never settles — a functional updater (setCount((value) => value + 1)), a freshly-constructed reference (setItems([]), setUser({ ...user })), or a value derived from the same state (setCount(count + 1)). Every commit re-runs the effect and re-sets the state, causing a render loop that exhaustive-deps does not catch because the dependency array is already complete. The rule stays quiet on mount-only [] effects, setters deferred inside timer/subscription/promise callbacks, guarded updates, and plausibly-stable scalar writes that settle via Object.is (setOpen(true), setTab(props.tab)). See #346.

• #582 b2934f9 Thanks @rayhanadev! - Fix a rn-no-raw-text false positive on fbtee translation tags. fbtee's <fbt> / <fbs> (and namespaced children like <fbt:param>) are compile-time translation tags that disappear at build time, so text inside <Text><fbt>…</fbt></Text> is really rendered inside <Text> and is safe on React Native. The rule now treats fbt / fbs as transparent wrappers when every ancestor up to a text-handling component is also transparent, while still reporting raw text when an <fbt> is used outside a <Text> boundary. See #581.

react-doctor@0.2.12

Patch Changes

• #570 d917f62 Thanks @aidenybai! - Add the no-prop-types architecture rule. React 19 removed runtime propTypes validation entirely — React no longer reads Component.propTypes, so invalid props that used to log a console warning now pass silently. The rule flags Component.propTypes = { ... } assignments and static propTypes class fields on component-cased identifiers, and is version-gated to React 19+ (requires: ["react:19"]) so projects where propTypes still runs stay quiet. It steers users toward TypeScript prop types plus explicit runtime validation. See #460.

• #582 b2934f9 Thanks @rayhanadev! - Fix a rn-no-raw-text false positive on fbtee translation tags. fbtee's <fbt> / <fbs> (and namespaced children like <fbt:param>) are compile-time translation tags that disappear at build time, so text inside <Text><fbt>…</fbt></Text> is really rendered inside <Text> and is safe on React Native. The rule now treats fbt / fbs as transparent wrappers when every ancestor up to a text-handling component is also transparent, while still reporting raw text when an <fbt> is used outside a <Text> boundary. See #581.

• #557 67848ae Thanks @aidenybai! - Scope React subproject discovery so running react-doctor from a home directory no longer reports unrelated, vendored projects as ambiguous candidates. When the scan root has no package.json or workspace manifest, the filesystem crawl now skips OS/editor app-data directories (AppData, Library, …) and stops descending past a fixed depth. Previously a home-directory scan could surface React packages bundled inside editor installs (e.g. a VS Code extension under AppData) alongside real projects, aborting with Multiple React projects found. See #545.

• #576 e7a998a Thanks @aidenybai! - Unref process.stdin at CLI startup so an inherited stdin pipe/socket can no longer keep the event loop alive after a scan completes. Previously react-doctor --json (and other one-shot runs) could finish the scan and flush the full report yet never exit when launched by a parent that holds the stdin write-end open (eval runners, CI harnesses, editor integrations) — Node kept the loop alive on the idle Socket fd=0. Interactive prompts are unaffected because prompts' readline interface re-refs stdin on demand.

• Updated dependencies [d917f62, d0f5206, b2934f9]:

  • oxlint-plugin-react-doctor@0.2.12

@react-doctor/api@0.2.12

Patch Changes

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

@react-doctor/core@0.2.12

Patch Changes

• Updated dependencies [d917f62, d0f5206, b2934f9]:
  • oxlint-plugin-react-doctor@0.2.12

---

Note

Low Risk
Release-metadata-only diff (versions, changelogs, deleted changesets); behavioral changes were reviewed in the feature PRs this aggregates.

Overview
This is a Changesets release PR: it bumps the monorepo from 0.2.11 → 0.2.12, folds pending changeset notes into package CHANGELOGs, and removes the consumed .changeset/*.md files. There is no application source in the diff—only version and release metadata.

What 0.2.12 documents for consumers (already landed on main):

Lint plugins (oxlint-plugin-react-doctor, mirrored in eslint-plugin-react-doctor): new no-prop-types (React 19+ only) and no-self-updating-effect; rn-no-raw-text no longer false-positives on fbtee <fbt> / <fbs> wrappers.

CLI (react-doctor): tighter subproject discovery when scanning from a home directory without a root manifest (skip app-data dirs, depth cap); process.stdin unref at startup so one-shot runs (e.g. --json) exit when a parent keeps stdin open.

Internal (@react-doctor/api, @react-doctor/core): version alignment and dependency bumps on oxlint-plugin-react-doctor@0.2.12 only.

^{Reviewed by Cursor Bugbot for commit d505d22. Bugbot is set up for automated code reviews on this repo. Configure here.}