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

fix: declare support for react-native 0.69 #891

Merged
merged 1 commit into from
Jun 13, 2022
Merged

Conversation

tido64
Copy link
Member

@tido64 tido64 commented May 3, 2022

Description

Declare support for react-native 0.69.

Discussion: reactwg/react-native-releases#21

Platforms affected

  • Android
  • iOS
  • macOS
  • Windows

Test plan

  • Android
    • Fabric off
    • Fabric ON
  • iOS
    • Fabric off / Hermes off
    • Fabric off / Hermes ON
    • Fabric ON / Hermes off
    • Fabric ON / Hermes ON
  • Windows
    • NuGet off
    • NuGet ON

@github-actions github-actions bot added the platform: Android This affects Android label May 3, 2022
@tido64 tido64 linked an issue May 3, 2022 that may be closed by this pull request
13 tasks
@tido64 tido64 marked this pull request as ready for review June 13, 2022 12:52
@tido64 tido64 requested a review from kelset June 13, 2022 12:52
Copy link
Member

@kelset kelset left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, added a nit suggestion but feel free to proceed if you want 👍

@@ -17,10 +17,10 @@
"windows": "react-native run-windows --no-packager"
},
"peerDependencies": {
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2",
"react-native": "^0.0.0-0 || 0.62 - 0.68 || 1000.0.0",
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2 || ~18.0.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2 || ~18.0.0",
"react": "~16.11.0 || ~16.13.0 || ~17.0.0 || ~18.0.0",

nit: since we use ~ we should just be able to use the .0 for the patch version, it will account for them all

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In general, we shouldn't deviate from what react-native requires. By allowing the version number to go higher, we're basically allowing some leeway in case of emergencies. I don't think we should allow users to downgrade.

Copy link
Member

@kelset kelset Jun 13, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah that makes sense, in that case we can go

Suggested change
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2 || ~18.0.0",
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~18.0.0",

@@ -79,10 +79,10 @@
"@react-native-community/cli-platform-android": ">=4.10.0",
"@react-native-community/cli-platform-ios": ">=4.10.0",
"mustache": "^4.0.0",
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2",
"react-native": "^0.0.0-0 || 0.62 - 0.68 || 1000.0.0",
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2 || ~18.0.0",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
"react": "~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2 || ~18.0.0",
"react": "~16.11.0 || ~16.13.0 || ~17.0.0 || ~18.0.0",

(same as above)

@@ -5364,10 +5364,10 @@ __metadata:
react-native-test-app: "workspace:."
react-native-windows: ^0.66.11
peerDependencies:
react: ~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2
react-native: ^0.0.0-0 || 0.62 - 0.68 || 1000.0.0
react: ~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2 || ~18.0.0
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
react: ~16.11.0 || ~16.13.1 || ~17.0.1 || ~17.0.2 || ~18.0.0
react: ~16.11.0 || ~16.13.0 || ~17.0.0 || ~18.0.0

@tido64 tido64 merged commit 9145b17 into trunk Jun 13, 2022
@tido64 tido64 deleted the tido/bump-react-native branch June 13, 2022 14:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform: Android This affects Android
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add support for react-native 0.69
2 participants