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

fix(deps): update dependency styled-components to v6 #939

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 30, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
styled-components (source) 5.3.11 -> 6.1.13 age adoption passing confidence

Release Notes

styled-components/styled-components (styled-components)

v6.1.13

Compare Source

v6.1.12

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.11...v6.1.12

v6.1.11

Compare Source

v6.1.10

Compare Source

v6.1.9

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.8...v6.1.9

v6.1.8

Compare Source

Revert adding peerDependencies from v6.1.7; apparently some build tools do not respect peerDependenciesMeta[package].optional which is causing issues. Will revisit at a later date if possible.

Full Changelog: styled-components/styled-components@v6.1.7...v6.1.8

v6.1.7

Compare Source

What's Changed
  • chore: add all missing peer dependency statements by @​quantizor in https://github.com/styled-components/styled-components/pull/4243

    NOTE: this change may cause some installed dependency duplication until this NPM bug is addressed but yarn and pnpm have correct behavior. Bun also has a similar bug.

    Overall these changes ensure that styled-components is specifying a known working version of all utilized libraries, while instructing the client package manager that higher semver-compliant versions are permissible and should work, assuming the relevant libraries are compliant in practice.

Full Changelog: styled-components/styled-components@v6.1.6...v6.1.7

v6.1.6

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v6.1.5...v6.1.6

v6.1.5

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v6.1.4...v6.1.5

v6.1.4

Compare Source

What's Changed

Full Changelog: styled-components/styled-components@v6.1.3...v6.1.4

v6.1.3

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.2...v6.1.3

v6.1.2

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.1...v6.1.2

v6.1.1

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.1.0...v6.1.1

v6.1.0

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.9...v6.1.0

v6.0.9

Compare Source

fix bundling to not hardcode window (should fix some testing use cases that were incorrectly assuming a server environment when JSDOM and similar are in use)

Full Changelog: styled-components/styled-components@v6.0.8...v6.0.9

v6.0.8

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.7...v6.0.8

v6.0.7

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.6...v6.0.7

v6.0.6

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.5...v6.0.6

v6.0.5

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.4...v6.0.5

v6.0.4

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.3...v6.0.4

v6.0.3

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.2...v6.0.3

v6.0.2

Compare Source

What's Changed

New Contributors

Full Changelog: styled-components/styled-components@v6.0.1...v6.0.2

v6.0.1

Compare Source

Fixed an issue where a dev-time warning was being triggered too eagerly.

Full Changelog: styled-components/styled-components@v6.0.0...v6.0.1

v6.0.0

Compare Source

yarn add styled-components

Changed in this version

  • fix(types): prevent prop bleed on styling properties (fixes #​4053, c0f8015)
  • feat(types): ship csstype via "CSS" namespace (e6c4f0a)
  • chore: bump stylis to 4.3 (fixes #​4007, fa58875)
  • reduced some sources of unnecessary branching logic

Breaking changes in v6

Migration guide → https://styled-components.com/docs/faqs#what-do-i-need-to-do-to-migrate-to-v6

  • now using stylis v4 (if using stylis-plugin-rtl you'll need to upgrade to the newer version)
  • styled-components now provides its own types; if you installed @types/styled-components in the past, you'll want to remove it
  • dropped $as and $forwardedAs props (use as or forwardedAs)
  • dropped automatic prop filtering; use transient props ($ prefix) for stuff you don't want to be passed to child component / HTML
  • StyleSheetManager
    • replaced disableVendorPrefixes with enableVendorPrefixes prop
    • dropped automatic vendor prefixing; if you need to support older browsers, you can re-enable it easily with the above prop
      <StyleSheetManager enableVendorPrefixes>
        {/* your React tree and ThemeProvider goes here */}
      </StyleSheetManager>
  • dropped deprecated withComponent API (87f511a); use "as" prop instead
  • node >= 14 needed

Full Changelog: styled-components/styled-components@v5.3.7...v6.0.0


Configuration

📅 Schedule: Branch creation - "every weekday after 2:00 am before 6:00 am,every weekend" (UTC), 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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Jun 30, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @opencollective/[email protected]
npm error Found: [email protected]
npm error node_modules/styled-components
npm error   styled-components@"6.1.10" from the root project
npm error   peer styled-components@"*" from @styled-icons/[email protected]
npm error   node_modules/@styled-icons/boxicons-regular
npm error     @styled-icons/boxicons-regular@"10.47.0" from @opencollective/[email protected]
npm error     node_modules/@opencollective/frontend-components
npm error       @opencollective/frontend-components@"0.5.0" from the root project
npm error   5 more (@styled-icons/fa-solid, @styled-icons/feather, ...)
npm error
npm error Could not resolve dependency:
npm error peer styled-components@"5.3.11" from @opencollective/[email protected]
npm error node_modules/@opencollective/frontend-components
npm error   @opencollective/frontend-components@"0.5.0" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/styled-components
npm error   peer styled-components@"5.3.11" from @opencollective/[email protected]
npm error   node_modules/@opencollective/frontend-components
npm error     @opencollective/frontend-components@"0.5.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-07T22_31_13_735Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-07T22_31_13_735Z-debug-0.log

@vercel
Copy link

vercel bot commented Jun 30, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
opencollective-pdf ❌ Failed (Inspect) Oct 23, 2024 7:34am

@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 6ae8fbc to 0cdc682 Compare July 3, 2023 03:40
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 0cdc682 to d9c0fcf Compare July 6, 2023 06:34
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from d9c0fcf to fa1ad20 Compare July 7, 2023 22:23
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from fa1ad20 to ef6d057 Compare July 13, 2023 04:35
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from ef6d057 to 1a5e9eb Compare July 21, 2023 18:43
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 1a5e9eb to 90a55e4 Compare August 2, 2023 09:14
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 90a55e4 to f82067a Compare August 3, 2023 13:26
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from f82067a to 16a3777 Compare September 13, 2023 16:21
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 16a3777 to c18b70d Compare October 12, 2023 18:30
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from c18b70d to bc1b4ef Compare October 14, 2023 03:48
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from bc1b4ef to 07dd1fc Compare November 8, 2023 07:58
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 07dd1fc to 1f9bf53 Compare November 23, 2023 13:59
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 1f9bf53 to 522c736 Compare December 20, 2023 07:22
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 522c736 to 27664c0 Compare December 22, 2023 16:23
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 0047eb6 to 38f0a44 Compare March 1, 2024 10:43
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 38f0a44 to 970063f Compare March 11, 2024 07:54
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 970063f to 2d6ac89 Compare April 15, 2024 07:22
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 2d6ac89 to 48fa963 Compare May 1, 2024 02:13
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 48fa963 to c28f01d Compare May 7, 2024 22:31
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from c28f01d to ffbd675 Compare May 9, 2024 19:34
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from ffbd675 to 78a4a5d Compare July 17, 2024 16:00
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 78a4a5d to 8199332 Compare August 13, 2024 12:23
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 8199332 to dc3c32a Compare August 30, 2024 03:49
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from dc3c32a to 8a0350f Compare October 4, 2024 08:08
@renovate renovate bot force-pushed the renovate/styled-components-6.x branch from 8a0350f to 7d31e98 Compare October 16, 2024 07:09
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.

0 participants