Skip to content
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

Changelog for 18.3 is missing #28924

Closed
renchap opened this issue Apr 26, 2024 · 3 comments · Fixed by #28929
Closed

Changelog for 18.3 is missing #28924

renchap opened this issue Apr 26, 2024 · 3 comments · Fixed by #28929
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug

Comments

@renchap
Copy link

renchap commented Apr 26, 2024

React version: 18.3

Steps To Reproduce

  1. Check the Releases section on this repo, the CHANGELOG.md file, or click on "Release notes" at the end of the second note on this blog post: https://react.dev/blog/2024/04/25/react-19-upgrade-guide

The current behavior

There is no changelog for the 18.3 release

The expected behavior

There should be a changelog

@renchap renchap added the Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug label Apr 26, 2024
@joaopedrodcf
Copy link

Was also looking to understand the impact of this minor update :D

@nathanforce
Copy link

Sorry to pile on to a closed issue but did not want to add a documentation related issue.

@rickhanlonii does the 18.3 release include a fix for the hydration mismatch errors mentioned in React and Remix issues (
#24430 (comment)
remix-run/remix#4822 (comment))

I'm seeing some comments around issues/Twitter that indicate it might, but the changelog does not mention it.
https://twitter.com/kiliman/status/1769730243772780825

Thanks!

@rickhanlonii
Copy link
Member

No, that's the canary, not 18.3 stable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Unconfirmed A potential issue that we haven't yet confirmed as a bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants