Closed
Conversation
- Upgrade react/react-dom from ^18.2.0 to ^19.0.0 - Upgrade @types/react/@types/react-dom to ^19.0.0 - Replace react-test-renderer with @testing-library/react (17 test files) - Remove forwardRef wrappers (Input, TextArea, Modal, react-map-gl mock) - Remove propTypes assignments (Collapsible, Toggle, Dropdown, Input) - Remove Deprecated validator from utils/prop-types - Fix useRef() calls to pass explicit initial values (5 files) - Migrate emotion v10 to @emotion/css v11 in CSS pipeline - Replace Context.Provider with Context (React 19 syntax) - Replace useContext with use() hook (React 19 API) - Fix ReactElement<any> type casts for React 19 stricter typing - Fix styleguide webpack chunk filename conflict and router aliases - Remove deprecated TabNavigation page from styleguide - Regenerate all 64 test snapshots - Update peer dependency ranges to support React 19 (<21) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Move console.warn calls out of render into useEffect (Dropdown, Table, FilterGroup, Filter, TabNavigation, Grid) - Remove trivial dev warnings that don't aid debugging (Title, Pagination, NumberInput) - Fix hooks-after-early-return in Dropdown (Rules of Hooks violation) - Move ref.current sync assignments into useEffect (Modal, Popover, InlineEdit) Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
React 19 is now the minimum supported version. The React 18 test job swapped in React 18 at runtime but @testing-library/react@16 requires React 19 internals, causing recentlyCreatedOwnerStacks errors. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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.
PR Template
You can delete this markup if it doesn't apply to this PR
How to choose a release version?
From semver
Given a version number MAJOR.MINOR.PATCH:
If this PR is not for a major version change / does not introduce breaking changes, you can discard this template.
You can remove any unapplicable section if it doesn't apply to your introduced changes.
Breaking changes 💥
Migration guide from [previous version] 📋
Enums
In this version, all deprecated enums from [previous version] have been removed. The following table shows the equivalent new field for all removed fields:
When upgrading to [new version], simply import and use the new enums instead of the old ones (the props of the components is still named the same).
Deprecated Enums
The following emums have been deprecated, and will be removed in the next major version.
Props
In this version, all deprecated props from [previous version] have been removed. The following table shows the equivalent new field for all removed fields:
The following props have been deprecated, and will be removed in the next major version.