Skip to content

Conversation

@frankieyan
Copy link
Member

@frankieyan frankieyan commented Nov 1, 2025

Short description

This PR updates Ariakit to the latest available version.

Changelogs: https://ariakit.org/changelog

Test plan

  • Exploratory testing in Storybook
  • Use yalc to pull this into Todoist's frankie/ariakit-0.4.19 branch and verify that the app builds

@frankieyan frankieyan added the 👀 Show PR Used for PRs that need a review, but can be merged when CI is green. label Nov 1, 2025
@frankieyan frankieyan changed the title chore: Update Ariakit to 0.4.19 chore!: Update Ariakit to 0.4.19 Nov 1, 2025
@frankieyan frankieyan requested review from a team and rmartins90 and removed request for a team November 1, 2025 07:43
@frankieyan frankieyan force-pushed the frankie/update-typescript branch from 5da4cb8 to 6b53e57 Compare November 2, 2025 03:11
@frankieyan frankieyan force-pushed the frankie/update-ariakit-0.4.19 branch from 718e0f3 to c858bec Compare November 2, 2025 04:14
userEvent.click(screen.getByRole('tab', { name: 'Tab 2' }))
expect(screen.getByText('Content of tab 1')).not.toBeVisible()

await waitFor(() => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just curious, why these changes in tests?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These were failing without this, possibly due to Ariakit queueing these behind additional microtasks compared to the previous version. The same thing happens in Todoist - similar changes needed to be added there after pulling this in.

@rmartins90
Copy link
Contributor

@frankieyan why are we marking this RP as containing breaking change in the PR title?

@frankieyan
Copy link
Member Author

@rmartins90 while Ariakit's changelog doesn't mention any breaking changes in the range we're upgrading to, I marked this as breaking as it requires updates to our tests. I'm also moving it to a peer dependency so that consumers will need to explicitly list it as a dependency (as we already do), so for us, I don't think it makes sense for Renovate to pick this up automatically.

With the loosened restrictions (with the tilde symbol), consumers can technically use any patch updates beyond 0.4.19 so we are no longer blocking Ariakit updates with Reactist in the future.

Do you think it should be a patch/minor update instead?

@frankieyan frankieyan changed the title chore!: Update Ariakit to 0.4.19 build: Update Ariakit to 0.4.19 Nov 4, 2025
@frankieyan frankieyan force-pushed the frankie/update-typescript branch from 6b53e57 to 28eb8f2 Compare November 4, 2025 22:28
Base automatically changed from frankie/update-typescript to main November 4, 2025 22:30
@frankieyan frankieyan force-pushed the frankie/update-ariakit-0.4.19 branch from e1cbd09 to b17ce4a Compare November 4, 2025 22:40
@frankieyan frankieyan changed the title build: Update Ariakit to 0.4.19 feat!: Update Ariakit to 0.4.19 Nov 4, 2025
@frankieyan frankieyan merged commit 0a521a9 into main Nov 4, 2025
7 checks passed
@frankieyan frankieyan deleted the frankie/update-ariakit-0.4.19 branch November 4, 2025 22:45
@rmartins90
Copy link
Contributor

it requires updates to our tests

you mean on consumer side, right?

@frankieyan
Copy link
Member Author

you mean on consumer side, right?

Yup 👍 Also turns out, there was a small breaking change in Ariakit 0.4.9 as well: https://ariakit.org/changelog#aria-selected-on-composite-items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

👀 Show PR Used for PRs that need a review, but can be merged when CI is green.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants