-
Notifications
You must be signed in to change notification settings - Fork 5
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
chore: update react monorepo #74
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/react-monorepo
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
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
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
February 26, 2020 20:30
3ccb6f1
to
e086a36
Compare
renovate
bot
changed the title
chore: update react monorepo to v16.12.0
chore: update react monorepo to v16.13.0
Feb 26, 2020
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
April 14, 2020 17:01
e086a36
to
6f79af5
Compare
renovate
bot
changed the title
chore: update react monorepo to v16.13.0
chore: update react monorepo to v16.13.1
Apr 14, 2020
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
October 27, 2020 10:55
6f79af5
to
b9f259f
Compare
renovate
bot
changed the title
chore: update react monorepo to v16.13.1
chore: update react monorepo to v16.14.0
Oct 27, 2020
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
March 16, 2023 11:11
b9f259f
to
b04dd2a
Compare
renovate
bot
changed the title
chore: update react monorepo to v16.14.0
chore: update react monorepo
Mar 16, 2023
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
March 30, 2023 19:19
b04dd2a
to
ecacb8a
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
May 30, 2023 03:54
ecacb8a
to
7158140
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
June 13, 2023 11:39
7158140
to
b189378
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
August 12, 2023 22:41
ed90726
to
3f466b5
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
August 25, 2023 19:53
3f466b5
to
90e36ff
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
October 4, 2023 10:54
a934710
to
75c13a9
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
October 13, 2023 22:39
75c13a9
to
dd40698
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
October 21, 2023 13:56
dd40698
to
36c6803
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
November 10, 2023 21:06
36c6803
to
d578559
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
November 24, 2023 04:32
d578559
to
117ba34
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
December 16, 2023 02:31
117ba34
to
f70f92a
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
December 31, 2023 17:03
f70f92a
to
1a26bb2
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
January 18, 2024 10:40
1a26bb2
to
5d6d7c4
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
February 29, 2024 23:35
5d6d7c4
to
63617bb
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
2 times, most recently
from
March 21, 2024 14:24
f97f570
to
c0bb1c7
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
March 29, 2024 09:28
c0bb1c7
to
181b052
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
September 19, 2024 11:33
181b052
to
58068db
Compare
renovate
bot
force-pushed
the
renovate/react-monorepo
branch
from
September 30, 2024 16:28
58068db
to
ce1b549
Compare
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.
This PR contains the following updates:
16.9.9
->16.14.62
16.11.0
->16.14.0
16.11.0
->16.14.0
Release Notes
facebook/react (react)
v16.14.0
Compare Source
React
v16.13.1
Compare Source
React DOM
componentWillReceiveProps
,shouldComponentUpdate
, and so on). (@gaearon in #18330)v16.13.0
Compare Source
React
React.createFactory()
(@trueadm in #17878)React DOM
style
may cause an unexpected collision (@sophiebits in #14181, #18002)unstable_createPortal
(@trueadm in #17880)onMouseEnter
being fired on disabled buttons (@AlfredoGJ in #17675)shouldComponentUpdate
twice when developing inStrictMode
(@bvaughn in #17942)version
property to ReactDOM (@ealush in #15780)toString()
ofdangerouslySetInnerHTML
(@sebmarkbage in #17773)Concurrent Mode (Experimental)
ReactDOM.createRoot()
(@trueadm in #17937)ReactDOM.createRoot()
callback params and added warnings on usage (@bvaughn in #17916)SuspenseList
CPU bound heuristic (@sebmarkbage in #17455)isPending
only being true when transitioning from inside an input event (@acdlite in #17382)React.memo
components dropping updates when interrupted by a higher priority update (@acdlite in #18091)v16.12.0
Compare Source
React DOM
useEffect
) not being fired in a multi-root app. (@acdlite in #17347)React Is
lazy
andmemo
types considered elements instead of components (@bvaughn in #17278)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.