-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
[Snyk] Upgrade react-native-web from 0.14.10 to 0.16.1 #2939
Conversation
Snyk has created this PR to upgrade react-native-web from 0.14.10 to 0.16.1. See this package in npm: https://www.npmjs.com/package/react-native-web See this project in Snyk: https://app.snyk.io/org/luke9389/project/8e767e27-47b3-4730-99bf-20145f1d4e73?utm_source=github&utm_medium=upgrade-pr
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
Definitely we should make sure this doesn't screw anything up too badly 🙃 |
👋 Hey, I'm making a pr that should hopefully allow snyk-bot to pass the CLA check after it gets rerun. Once my PR is merged I'll try rerunning this to see if it passes. |
will wait for that then @Luke9389 |
Hey @sketchydroide, looks like re-running it doesn't work. It seems to be referencing the commit hash of whatever the most recent master branch had when it was created. You'll likely have to just merge with the failing CLA and then leave a message explaining that (as long as you know this is actually safe to merge in the first place 😄). The PR I made will prevent this from happening in the future. |
@roryabraham and @marcaaron do you think this is safe to merge, what @Luke9389 says makes some sense, but wanted to get a third opinion. |
@sketchydroide I think it might be worth doing, but we should definitely be careful and do extensive testing. We could always merge it and see if it causes regressions during QA? We could also ask Applause to do some extra exploratory testing for the release including this PR too? |
I think asking Applause to do some exploratory testing sounds great. |
I think the merge it and track regressions approach makes sense for a minor version bumps. In this case, we are jumping 2 major versions forward so I think we can afford to be a bit cautious and...
15.0 - https://github.com/necolas/react-native-web/releases/tag/0.15.0
Thoughts? |
Oh, this is a big one that I glossed over the first time:
That means we also would have to bump React up a major version too? |
Just gonna start dropping things here that I'm finding so we can make an action list...
from v 15.0 notes |
This could probably be a follow up but maybe this can simplify our use of the custom |
Found one usage of this. |
Everything else looks pretty much OK and testing well. |
I looked into this a bit, and I'm not sure it will. Some context for why I created the |
Does just seem like the subscription will be removed anyway but the method is deprecated... but the error will show in the console 🙃 |
Ok I traced this back to here -> https://github.com/react-navigation/react-navigation/blob/a184ce24b3d7a8a37667d3f43ac043fef0231db4/packages/stack/src/views/Stack/CardContainer.tsx#L183 And I think there are maybe two options...
|
Gonna close this in favor of #3215 I don't think we should upgrade to 0.16.1 yet, but migrating to the previous major version was relatively painless. |
Snyk has created this PR to upgrade react-native-web from 0.14.10 to 0.16.1.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: react-native-web
0.16.1
0.16 preview release
This release includes Flow type exports, updates vendored modules, and miscellaneous bug fixes.
Breaking changes
Animated
&VirtualizedList
have been updated from React Native.Dimensions
has changed the source ofwindow
dimensions and works more reliably in Safari.NativeEventEmitter
no longer inherits fromEventEmitter
and does not include theremoveSubscription
method.New features
0.15.7
0.15.6
0.15.5
0.15.4
0.15.3
0.15.2
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs