chore: upgrade react-aria-components to 1.19.0#1938
Open
apucacao wants to merge 1 commit into
Open
Conversation
Bumps react-aria-components 1.18.0 -> 1.19.0 with the aligned react-aria (3.50.0), react-stately (3.48.0), and @react-types/shared (3.36.0) packages from the same release. The @react-aria/*, @react-stately/*, and @internationalized/* sub-packages were already at the matching versions and are unchanged. Ran `pnpm dedupe` so react-aria, react-stately, and @react-types/shared each resolve to a single instance (3.50.0 / 3.48.0 / 3.36.0). Without it the @react-aria/* shims' floating `^3.48.0` range keeps the prior 3.49.0 copy in the tree, producing duplicate PressResponderContext / FocusableContext instances that break aria-disabled propagation (Perceivable.spec.tsx) — the same regression seen in the 1.18.0 bump. All 268 unit tests pass; typecheck and build are clean.
🦋 Changeset detectedLatest commit: 14d56ea The changes in this PR will be included in the next version bump. This PR includes changesets to release 9 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
commit: |
nhironaka
approved these changes
Jun 24, 2026
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
2 participants
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.
Note
Do not merge until we've met the repo's 7-day minimum-release age policy, on June 25, 2026.
Summary
Upgrades
react-aria-componentsfrom 1.18.0 → 1.19.0, along with the aligned packages from the same upstream release:react-aria: 3.49.0 → 3.50.0react-stately: 3.47.0 → 3.48.0@react-types/shared: 3.35.0 → 3.36.0The
@react-aria/*,@react-stately/utils, and@internationalized/datesub-packages were already pinned at the versions that ship with this release, so they're unchanged. Bumps are applied to bothdependencies/devDependenciesandpeerDependenciesacross all nine affected packages (components,drawer,dropdown,filter,focus-trap,form,menu,modal,navigation).pnpm dedupewas run soreact-aria,react-stately, and@react-types/sharedeach resolve to a single instance (3.50.0 / 3.48.0 / 3.36.0). Without it, the@react-aria/*shims' floating^3.48.0range keeps the prior 3.49.0 copy in the tree, yielding duplicatePressResponderContext/FocusableContextinstances that breakaria-disabledpropagation (Perceivable.spec.tsx) — the same regression encountered in the 1.18.0 bump (#1914).This is a purely additive upstream release — no breaking changes — so no component code changes were required. Notable upstream additions (not yet surfaced by LaunchPad):
keyboardNavigationBehaviorforGridList/Tree, inline-completion support +getTargetRectonPopover/Autocomplete,MenuonActionnow passing the item value, andDragTypes.has()wildcard matching.Screenshots (if appropriate)
N/A — dependency-only upgrade with no intended visual change. Chromatic will confirm no visual regressions.
Testing approaches
pnpm typecheck— clean (0 diagnostics)pnpm test— 268/268 unit tests pass, coverage above thresholds;Perceivable.spec.tsx(the duplicate-context canary) passespnpm build— all 21 projects build successfullybiome check— clean on all changed filesreact-aria@3.50.0/react-stately@3.48.0/@react-types/shared@3.36.0🤖 Generated with Claude Code
Note
Medium Risk
Wide dependency bump across accessibility-focused UI packages can change focus, keyboard, and disabled-state behavior at runtime even without local code edits; lockfile dedupe is important to avoid duplicate react-aria context instances.
Overview
This PR aligns the monorepo on React Aria 1.19.0 by bumping
react-aria-components(1.18.0 → 1.19.0),react-aria(3.49.0 → 3.50.0),react-stately(3.47.0 → 3.48.0), and@react-types/shared(3.35.0 → 3.36.0) in devDependencies, peerDependencies, and where applicable dependencies for@launchpad-ui/components,drawer,dropdown,filter,focus-trap,form,menu,modal, andnavigation.A changeset records patch releases for those packages and notes upstream additive features (e.g.
keyboardNavigationBehavior, PopovergetTargetRect, MenuonActionvalue).pnpm-lock.yamlis refreshed so the tree resolves to a single copy of the upgraded packages (and drops an unusedaxios@1.16.1entry in favor of 1.17.0 via nx). No LaunchPad component or test source files are modified in this diff.Reviewed by Cursor Bugbot for commit 14d56ea. Bugbot is set up for automated code reviews on this repo. Configure here.