chore(api): regenerate stale API report snapshots#844
Merged
Conversation
The committed React + agents API reports drifted from what API Extractor produces under the lockfile-pinned toolchain (@types/react 19.2.17), breaking the `build` job's api:check on main since #840. The drift is representational only — JSX return-type alias naming (react_jsx_runtime.JSX.Element → react.JSX.Element) and @public tag normalization. No public symbols, signatures, or shapes changed.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
All contributors have signed the CLA ✍️ ✅ Posted by the CLA bot. |
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
1 participant
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.
The
buildjob'sapi:checkhas failed onmainsince #840. The committed React and agents API reports drifted from what API Extractor produces under the lockfile-pinned toolchain (@types/react@19.2.17), because #840's snapshots were regenerated with a different local toolchain.The drift is representational only:
react_jsx_runtime.JSX.Element→react.JSX.Element/React_2.JSX.Element)@public (undocumented)→@publictag normalization on a few interfacesNo public symbols, signatures, or shapes changed.
api:checkwas short-circuiting at the React package, which is why CI only reportedindex+ui; the agentsreactentry was stale too and is included here.bun run api:checkpasses clean (exit 0) after this regen.Need help on this PR? Tag
/codesmithwith what you need. Autofix is disabled.