This repository has been archived by the owner on May 7, 2021. It is now read-only.
[Snyk] Upgrade react from 16.11.0 to 16.12.0 #959
Merged
Conversation
This file contains 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
Snyk has created this PR to upgrade react from 16.11.0 to 16.12.0. See this package in NPM: https://www.npmjs.com/package/react See this project in Snyk: https://app.snyk.io/org/cds-snc/project/762c54e6-bad5-4b75-b4e7-c2ac53716139?utm_source=github&utm_medium=upgrade-pr
DianeLiu2019
approved these changes
Nov 25, 2019
DianeLiu2019
deleted the
snyk-upgrade-d574a3e567395b4253f2c83ba286aaa0
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Snyk has created this PR to upgrade react from 16.11.0 to 16.12.0.
ℹ️ 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
React DOM
useEffect) not being fired in a multi-root app. (@acdlite in #17347)React Is
lazyandmemotypes considered elements instead of components (@bvaughn in #17278)Artifacts
• react: https://unpkg.com/react@16.12.0/umd/
• react-art: https://unpkg.com/react-art@16.12.0/umd/
• react-dom: https://unpkg.com/react-dom@16.12.0/umd/
• react-is: https://unpkg.com/react-is@16.12.0/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.12.0/umd/
• scheduler: https://unpkg.com/scheduler@0.18.0/umd/
React DOM
mouseenterhandlers from firing twice inside nested React containers. @yuanoook in #16928unstable_createRootandunstable_createSyncRootexperimental APIs. (These are available in the Experimental channel ascreateRootandcreateSyncRoot.) (@acdlite in #17088)Artifacts
• react: https://unpkg.com/react@16.11.0/umd/
• react-art: https://unpkg.com/react-art@16.11.0/umd/
• react-dom: https://unpkg.com/react-dom@16.11.0/umd/
• react-is: https://unpkg.com/react-is@16.11.0/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.11.0/umd/
• scheduler: https://unpkg.com/scheduler@0.17.0/umd/
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