Skip to content
This repository has been archived by the owner on Jun 17, 2022. It is now read-only.

Road to v0.65.0 - RC4 phase #242

Closed
5 of 8 tasks
kelset opened this issue Aug 11, 2021 · 7 comments
Closed
5 of 8 tasks

Road to v0.65.0 - RC4 phase #242

kelset opened this issue Aug 11, 2021 · 7 comments
Labels
pre-release rc Release candidate release status Information about an upcoming or ongoing release

Comments

@kelset
Copy link
Member

kelset commented Aug 11, 2021

This issue serves to track the status of work to reach 0.65.0.

Current latest: 0.65.0-rc.4

Read this comment for more info on why we decided to do one more RC. We really hope that we can have a shorter lifespan on this RC4 and get to 0.65.0 soon 🤞

Left to do for 0.65.0

non code related

code related

  • add me

Known issues

  • add me

Commits (and PRs) to cherry pick

  • add me

Non-blocking

Local commits to backport to main


Please limit your comments to reports of issues encountered with the RC and cherry pick suggestions. No ETA currently for when 0.65.0 will be released.

@kelset kelset added stable Stable version backport request Cherry picking a change into an existing release pre-release rc Release candidate release status Information about an upcoming or ongoing release and removed stable Stable version backport request Cherry picking a change into an existing release labels Aug 11, 2021
@kelset kelset mentioned this issue Aug 11, 2021
9 tasks
@hramos
Copy link
Collaborator

hramos commented Aug 11, 2021

Thanks @kelset and @Titozzz for digging into the react-native-codegen issues. I think that applying facebook/react-native@5f7deb5 to 0.65, without upstreaming to main, is reasonable.

For context, we would not want this change in main because the code-gen files (FBReactNativeSpec.h and its Obj-C++ counterpart) can be derived from the JavaScript source files in Libraries/ by react-native-codegen, and we would not want to have conflicts in what react-native-codegen outputs at build time versus what is checked into the repository.

@kelset
Copy link
Member Author

kelset commented Aug 12, 2021

For context, we would not want this change in main because the code-gen files (FBReactNativeSpec.h and its Obj-C++ counterpart) can be derived from the JavaScript source files in Libraries/ by react-native-codegen, and we would not want to have conflicts in what react-native-codegen outputs at build time versus what is checked into the repository.

Thanks for clarifying - this is very close to our assumption for why the two files were ignored in the first place 👍 I think that one consideration to do at a later point (when talking about RN OSS releases >= 0.66) is if we should bring this mechanism back more "formally"; meaning, when a release branch is out, we should revert the gitignore line about the two files so that at the local E2E test phase they will get generated and so they will be bundled with the "released" RN node module (which will, as it was done for 0.64 and 0.65) that ios builds will not fail.

@tido64
Copy link
Collaborator

tido64 commented Aug 12, 2021

@hramos Is making react-native-codegen work more seamlessly and moving the dependency from the template into main package.json on FB's backlog? It would be great if we didn't have to spend so much effort on this next release.

@mhammerc
Copy link

mhammerc commented Aug 17, 2021

I tried 0.65.0-rc.4 on my app.

  • On iOS, I had set flipper to a specific version inferior to 0.93. It failed to build. But setting back the default value (use_flipper!()) fixed the compilation issue.

  • I had to patch packages react-native-keyboard-aware-scroll-view and react-native-blurhash because of api changes. (patch files/pr available on both repositories)

  • Works fine on iOS on debug and release! I had to disable react-native-codepush for release, otherwise the bundle could not be found 🤔

  • On Android, I get loads of warning new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.. I could not test my app further because react-native-reanimated crash (both debug & release).

Compilation on both Android and iOS on both debug and release works fine!

@kelset
Copy link
Member Author

kelset commented Aug 17, 2021

great report, thanks @mhammerc! We'll release 0.65.0 later today, hopefully the third party packages you listed will catch up quickly to the new release :)

@nelsonprsousa
Copy link

I tried 0.65.0-rc.4 on my app.

  • On iOS, I had set flipper to a specific version inferior to 0.93. It failed to build. But setting back the default value (use_flipper!()) fixed the compilation issue.
  • I had to patch the package react-native-keyboard-aware-scroll-view and react-native-blurhash because of api changes. (patch files/pr available on both repositories)
  • Works fine on iOS on debug and release! I had to disable react-native-codepush for release, otherwise the bundle could not be found 🤔
  • On Android, I get loads of warning new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.. I could not test my app further because react-native-reanimated crash (both debug & release).

Compilation on both Android and iOS on both debug and release works fine!

cc @mrousavy @piaskowyk

@kelset
Copy link
Member Author

kelset commented Aug 17, 2021

allright folks, 0.65.0 is out!

Thank you all for your support in getting to this point 🙏 See you on the other side: #244

@kelset kelset closed this as completed Aug 17, 2021
@react-native-community react-native-community locked as resolved and limited conversation to collaborators Aug 17, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
pre-release rc Release candidate release status Information about an upcoming or ongoing release
Projects
None yet
Development

No branches or pull requests

5 participants