Skip to content

Change usage of 'next' version of @react-native-community/template and react-native packages to specific react-native version #13446

@Yajur-Grover

Description

@Yajur-Grover

Summary

Due to Meta moving the template package outside the react-native repo and into the @react-native-community/template package, there is no matching nightly version for the new template package for [email protected], which is breaking the current 6/18 integration. In order to unblock the integration, the scripts that run the react-native init command have been modified to use the next version of the @react-native-community/template package, as that is the only one with a matching react-native version.

This PR adds a job that will publish a nightly build to the @react-native-community/template package every time a new react-native package is published. Once the react-native-windows repo is integrated up to a date that has a matching react-native and @react-native-community/template nightly build, we will revert the usage of 'next' to the current react-native version being used in the repo.

Additionally, a similar change had to be made in the react-native-windows-init.yml file to use the next version of the react-native package instead of the 6/18 nightly build when running the create-react-native-library init script. Once we have integrated to the point that the nightly build works with the new template package, we should revert this change.

Forks made:
5e9e7e3
e534281

Motivation

Unblock CI to allow jobs with react-native init to run successfully.

Basic Example

No response

Open Questions

No response

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions