-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update emotion monorepo #65
Open
renovate
wants to merge
1
commit into
master
Choose a base branch
from
renovate/emotion-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/emotion-monorepo
branch
from
May 9, 2019 03:20
36d897b
to
cbf0b6f
Compare
renovate
bot
changed the title
Update emotion monorepo to v10.0.10
Update emotion monorepo
May 9, 2019
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
June 9, 2019 09:19
cbf0b6f
to
35d88bd
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
July 13, 2019 05:59
35d88bd
to
a3c4163
Compare
renovate
bot
changed the title
Update emotion monorepo
Update emotion monorepo to v10.0.14
Jul 13, 2019
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
August 10, 2019 13:56
a3c4163
to
2a176dd
Compare
renovate
bot
changed the title
Update emotion monorepo to v10.0.14
Update emotion monorepo
Aug 10, 2019
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
August 20, 2019 05:56
2a176dd
to
711d644
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
September 5, 2019 00:00
711d644
to
ab7e969
Compare
renovate
bot
changed the title
Update emotion monorepo
Update emotion monorepo to v10.0.17
Sep 5, 2019
renovate
bot
changed the title
Update emotion monorepo to v10.0.17
Update emotion monorepo
Oct 3, 2019
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
October 3, 2019 05:59
ab7e969
to
590d5d7
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
November 11, 2019 15:02
590d5d7
to
8c831a0
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
December 30, 2019 13:56
8c831a0
to
fb11eb3
Compare
renovate
bot
changed the title
Update emotion monorepo
Update emotion monorepo to v10.0.27
Dec 30, 2019
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
March 15, 2020 10:58
fb11eb3
to
b1796e2
Compare
renovate
bot
changed the title
Update emotion monorepo to v10.0.27
Update emotion monorepo
Mar 15, 2020
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
April 28, 2020 18:01
b1796e2
to
c27f7dd
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
August 25, 2020 02:59
c27f7dd
to
d48a5cf
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
November 27, 2020 05:55
d48a5cf
to
d9064b1
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
February 10, 2021 11:01
d9064b1
to
efa351f
Compare
renovate
bot
force-pushed
the
renovate/emotion-monorepo
branch
from
March 7, 2022 15:40
efa351f
to
cc0dfed
Compare
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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:
10.0.9
->10.3.1
10.0.9
->10.3.0
10.0.9
->10.2.2
10.0.9
->10.0.27
Release Notes
emotion-js/emotion
v10.3.1
Compare Source
Patch Changes
33c01578
Thanks @Methuselah96! - ExportKeyframes
type to avoid TypeScript insertingimport("@​emotion/serialize").Keyframes
references into declaration files emitted based on a source files exportingkeyframes
result. This avoids issues with strict package managers that don't allow accessing undeclared dependencies.v10.3.0
Compare Source
Minor Changes
#2566
122e9f11
Thanks @eps1lon, @Andarist! - Fixed hydration mismatches ifReact.useId
(an upcoming API in React 18) is used within a tree below our components.#2560
b5a26619
Thanks @eps1lon! - Dropped usage of a deprecatedSFC
React type in favor ofFC
. TheFC
type has been introduced in@types/[email protected]
so this version of this package is now a minimum requirement for TypeScript users.v10.1.1
Compare Source
Patch Changes
fe30cbd6
#2066 Thanks @Andarist! - Fixed an issue with React giving warning about static children not having unique keys when using the classicjsx
factory. This example illustrates the situation in which this has been incorrectly happening:v10.1.0
Compare Source
Minor Changes
71514b06
#1970 Thanks @FLGMwt! - Support for the new JSX runtimes has been added. They require compatible React versions and shouldn't be manually used.To use them you can use the new
@jsxImportSource @​emotion/core
pragma instead of the old@jsx jsx
or you can use@emotion/babel-preset-css-prop
with{ runtime: 'automatic' }
option to have it handled automatically for you for the whole project.v10.0.35
Compare Source
Patch Changes
2cf3b16b
#1973 Thanks @santialbo! - Fixed label extraction from the stack traces in node for components wrapped inReact.forwardRef
. This has affected only development builds.v10.0.34
Compare Source
Patch Changes
4979ebb2
#1966 Thanks @chnakamura! - Fixed label extraction from the stack traces in Chrome in certain scenarios. This has affected only development builds.v10.0.28
Compare Source
Patch Changes
d0b2a94
#1714 Thanks @Andarist! - Fixed label extraction from the stack traces in FireFox and Safari. We have failed to match a label in Emotion wrappers like Theme UI which caused SSR mismatches in mentioned browsers. This has affected only development builds.v10.0.27
Compare Source
Patch Changes
4c62ae9
#1698 Thanks @Andarist! - Add LICENSE file4c62ae9
]:v10.0.22
Compare Source
Patch Changes
4fc5657a
#1219 Thanks @Andarist! - Add dev hint about css object being stringified by accident2fc75f26
#1548 Thanks @Andarist! - Accept objects asclassName
in jsx-created components (they are stringified) to match React behavior10211951
#1553 Thanks @Andarist! - Add dev warning about keyframes being interpolated into plain strings.57a767ea
#1560 Thanks @Andarist! - Fix composition of styles without a final semicolon in a declaration blockUpdated dependencies [
4fc5657a
,10211951
,57a767ea
,c3f0bc10
,11bea3a8
]:v10.0.21
Compare Source
Patch Changes
/* #__PURE__ */
annotation to creation of EmotionCssPropInternalv10.0.20
Compare Source
Patch Changes
v10.0.17
Compare Source
v10.0.16
Compare Source
v10.0.15
Compare Source
v10.0.14
Compare Source
v10.0.10
Compare Source
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 has been generated by Mend Renovate. View repository job log here.