chore: update dependency prettier-plugin-tailwindcss to ^0.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
prettier-plugin-tailwindcss	^0.7.4 → ^0.8.0

---

Release Notes

tailwindlabs/prettier-plugin-tailwindcss (prettier-plugin-tailwindcss)

v0.8.0

Compare Source

Changed

• Require at least Prettier 3.7.x (#​420)

Added

• Export public sorting APIs to /sorter (#​438)

Fixed

• Remove top-level await (#​420)
• Improve load-time performance (#​420)
• Improve config resolution caching with directory-based cache (#​432)
• Load compatible plugins on demand and tighten plugin detection (#​437)
• Load v3/v4 modules only when needed (#​439)
• Remove recast/ast-types deps and optimize dynamic JS attribute handling (#​440)
• Remove unused deps (#​441)
• Use the plugin that has already been imported rather than dynamically importing it again (#​442)
• Skip visiting non-node children (#​443)
• Optimize whitespace-only class detection (#​429)
• Fix v3 config loading with Jiti re-exports (#​448)
• Collapse whitespace in template literals with adjacent quasis (#​427)
• Improve canCollapseWhitespaceIn handling for "tailwindPreserveWhitespace": true (#​428)

---

Configuration

📅 Schedule: (in timezone Asia/Tokyo)

• Branch creation
  • "after 8am and before 5pm every weekday"
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Never, 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 4 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 9, reused 0, downloaded 0, added 0
Progress: resolved 18, reused 0, downloaded 0, added 0
Progress: resolved 25, reused 0, downloaded 0, added 0
Progress: resolved 34, reused 0, downloaded 0, added 0
Progress: resolved 55, reused 0, downloaded 0, added 0
Progress: resolved 76, reused 0, downloaded 0, added 0
Progress: resolved 87, reused 0, downloaded 0, added 0
Progress: resolved 93, reused 0, downloaded 0, added 0
Progress: resolved 95, reused 0, downloaded 0, added 0
Progress: resolved 96, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/kufu/smarthr-ui/sandbox/next:
 ERR_PNPM_NO_MATURE_MATCHING_VERSION  Version 16.2.6 (released 6 days ago) of next does not meet the minimumReleaseAge constraint

This error happened while installing a direct dependency of /tmp/renovate/repos/github/kufu/smarthr-ui/sandbox/next

The latest release of next is "16.2.6". Published at 5/7/2026

Other releases are:
  * next-11: 11.1.4 published at 1/27/2022
  * next-12-2-6: 12.2.6 published at 9/29/2022
  * next-14-1: 14.1.1 published at 2/29/2024
  * rc: 15.0.0-rc.1 published at 10/15/2024
  * next-13: 13.5.11 published at 3/27/2025
  * next-12-3-2: 12.3.7 published at 3/28/2025
  * beta: 16.0.0-beta.0 published at 10/10/2025
  * next-14: 14.2.35 published at 12/11/2025
  * next-15-3: 15.3.9 published at 1/26/2026
  * next-15-2: 15.2.9 published at 1/26/2026
  * next-15-0: 15.1.12 published at 1/26/2026
  * next-15-0-0: 15.0.8 published at 1/26/2026
  * backport: 15.5.18 published at 5/7/2026
  * canary: 16.3.0-canary.19 published at 5/10/2026

If you need the full list of all 3766 published versions run "pnpm view next versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude