Bump react-native-is-edge-to-edge to 1.1.7 #7346
Merged
Conversation
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
tomekzaw
reviewed
Apr 5, 2025
tomekzaw
approved these changes
Apr 5, 2025
daniellmartins
approved these changes
Apr 6, 2025
bartlomiejbloniarz
approved these changes
Apr 6, 2025
tomekzaw
changed the title
bartlomiejbloniarz
approved these changes
Apr 7, 2025
patrycjakalinska
pushed a commit
that referenced
this pull request
Apr 7, 2025
<!-- Thanks for submitting a pull request! We appreciate you spending the time to work on these changes. Please follow the template so that the reviewers can easily understand what the code changes affect. --> This PR unfixes the current `react-native-is-edge-to-edge` version. The current version has `peerDependencies` that prevents the Expo team from creating a canary release: ``` Conflicting peer dependency: [email protected] ``` npm installs this version to respect the `>=0.73.0` requirement, even if `[email protected]` is already a project dependency. PS: I'm on my phone and without a computer access, if someone can run yarn and fix the pipeline before merging, it would help 🙏 --------- Co-authored-by: Tomek Zawadzki <[email protected]>
patrycjakalinska
added a commit
that referenced
this pull request
Apr 7, 2025
This PR unfixes the current `react-native-is-edge-to-edge` version. The current version has `peerDependencies` that prevents the Expo team from creating a canary release: ``` Conflicting peer dependency: [email protected] ``` npm installs this version to respect the `>=0.73.0` requirement, even if `[email protected]` is already a project dependency. PS: I'm on my phone and without a computer access, if someone can run yarn and fix the pipeline before merging, it would help 🙏 Co-authored-by: Mathieu Acthernoene <[email protected]> Co-authored-by: Tomek Zawadzki <[email protected]>
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This PR unfixes the current
react-native-is-edge-to-edgeversion.The current version has
peerDependenciesthat prevents the Expo team from creating a canary release:npm installs this version to respect the
>=0.73.0requirement, even if[email protected]is already a project dependency.PS: I'm on my phone and without a computer access, if someone can run yarn and fix the pipeline before merging, it would help 🙏