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
[core] Fix react next patch and prevent regression #21482
Conversation
await exec(`git apply ${path.resolve(__dirname, `./react-${distTag}.diff`)}`); | ||
} catch (error) { | ||
// ignore if the patch doesn't exist | ||
if (error.code !== 128) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This code is not necessarily tied to non-existing patches. It hid the error message that the patch was corrupted.
I don't remember why I added it. In the end we could always leave the patch empty on certain branches.
Details of bundle changes.Comparing: ff6bde2...d153ed0 Details of page changes
|
@eps1lon I recall using git diff to generate the diff, using git apply to test it. But it was the first time doing such. It's not unlikely I did one step wrong. |
When I say "test", I mean testing that the diff is applied, I didn't try to run the tests with the next version of React (I used the failing CI report instead). I haven't look into how to do such in my env yet. |
Weird. Because usually the compare range should be updated as well to reflect the compared commits. Anyway, in the future the CI failures should be more descriptive. Make sure to use |
Pinning the command, for later: REACT_DIST_TAG=next node scripts/use-react-dist-tag.js && yarn |
The patch probably broken in #21249. @oliviertassinari Did you create the new patch with
git diff
or manually edit the diff?Will be forward ported to
next
once merged.