Skip to content

fix(component-library): upgrade react-aria and react-aria-components #2942

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Aug 11, 2025

Conversation

cprussin
Copy link
Collaborator

Summary

Our prior version of react-aria was susceptible to the bug at adobe/react-spectrum#6399, which is a race condition that causes the table to sometimes fail to render items when rerendering. I didn't think our version was susceptible to this bug as I haven't personally encountered it, but Tejas mentioned he saw it in the entropy explorer. I expect that upgrading should resolve the bug for good.

Rationale

Fixes bugs

How has this been tested?

  • Current tests cover my changes
  • Added new tests
  • Manually tested the code

@cprussin cprussin requested a review from a team as a code owner August 11, 2025 22:04
Copy link

vercel bot commented Aug 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Project Deployment Preview Comments Updated (UTC)
api-reference Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm
component-library Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm
developer-hub Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm
entropy-debugger Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm
entropy-explorer Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm
insights Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm
proposals Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm
staking Ready Preview 💬 Add feedback Aug 11, 2025 10:29pm

Our prior version of react-aria was susceptible to the bug at
adobe/react-spectrum#6399, which is a race condition
that causes the table to sometimes fail to render items when rerendering.  I
didn't think our version was susceptible to this bug as I haven't personally
encountered it, but Tejas mentioned he saw it in the entropy explorer.  I expect
that upgrading should resolve the bug for good.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants