Update dependency tailwindcss to v3.4.11

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tailwindcss (source)	3.4.10 -> 3.4.11

---

Release Notes

tailwindlabs/tailwindcss (tailwindcss)

v3.4.11

Compare Source

v3.4.10

Compare Source

v3.4.9

Compare Source

Fixed

• No longer warns when broad glob patterns are detecting vendor folders

v3.4.8

Compare Source

v3.4.7

Compare Source

v3.4.6

Compare Source

Fixed

• Fix detection of some utilities in Slim/Pug templates (#​14006)

Changed

• Loosen :is() wrapping rules when using an important selector (#​13900)

v3.4.5

Compare Source

v3.4.4

Compare Source

Fixed

• Make it possible to use multiple <alpha-value> placeholders in a single color definition (#​13740)
• Don't prefix classes in arbitrary values of has-*, group-has-*, and peer-has-* variants (#​13770)
• Support negative values for {col,row}-{start,end} utilities (#​13781)
• Update embedded browserslist database (#​13792)

---

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 was generated by Mend Renovate. View the repository job log.

[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
.                                        |  WARN  deprecated @babel/plugin-proposal-object-rest-spread@7.20.7
.                                        |  WARN  deprecated @types/sharp@0.32.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: 119256e

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