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

Update dependency @emotion/core to v10.3.1 #16

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Nov 1, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@emotion/core 10.0.35 -> 10.3.1 age adoption passing confidence

Release Notes

emotion-js/emotion

v10.3.1

Compare Source

Patch Changes
  • #​2576 33c01578 Thanks @​Methuselah96! - Export Keyframes type to avoid TypeScript inserting import("@​emotion/serialize").Keyframes references into declaration files emitted based on a source files exporting keyframes result. This avoids issues with strict package managers that don't allow accessing undeclared dependencies.

v10.3.0

Compare Source

Minor Changes

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 classic jsx factory. This example illustrates the situation in which this has been incorrectly happening:

    <div css={{ color: 'hotpink' }}>
      <div />
      <div />
    </div>

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 @&#8203;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.


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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from 2ac7083 to b405888 Compare November 2, 2020 10:14
@renovate renovate bot changed the title Update dependency @emotion/core to v10.1.0 Update dependency @emotion/core to v10.1.1 Nov 2, 2020
@renovate renovate bot force-pushed the renovate/emotion-monorepo branch from b405888 to 5239cad Compare March 7, 2022 14:15
@renovate renovate bot changed the title Update dependency @emotion/core to v10.1.1 Update dependency @emotion/core to v10.3.1 Mar 7, 2022
@renovate
Copy link
Author

renovate bot commented Mar 24, 2023

Edited/Blocked Notification

Renovate 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.

⚠️ Warning: custom changes will be lost.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant