Update dependency styled-components to v6.1.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
styled-components (source)	6.1.10 -> 6.1.11

---

Release Notes

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

v6.1.11

Compare Source

v6.1.10

Compare Source

v6.1.9

Compare Source

What's Changed

• fix: improve types for .attrs() by @​uhyo in https://github.com/styled-components/styled-components/pull/4288
• fix(types): allow using a styled component as a key inside object styles in the web runtime by @​iiroj in https://github.com/styled-components/styled-components/pull/4249
• Upgrading babel dependencies to latest to fix CVE-2023-45133 by @​JesseObrien in https://github.com/styled-components/styled-components/pull/4214

New Contributors

• @​uhyo made their first contribution in https://github.com/styled-components/styled-components/pull/4288
• @​iiroj made their first contribution in https://github.com/styled-components/styled-components/pull/4249
• @​JesseObrien made their first contribution in https://github.com/styled-components/styled-components/pull/4214

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

---

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]

⚠️ 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: pnpm-lock.yaml

Scope: all 21 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
bench/vercel                             |  WARN  deprecated term-size@4.0.0
/tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/@turbo%2Fpack-test-harness: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/X-oss-byte/Nextjs/packages/next-swc/crates/next-dev-tests/tests

@turbo/pack-test-harness is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[changeset-bot]

⚠️ No Changeset found

Latest commit: f0bf5da

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR