chore(deps): update dependency prettier-plugin-tailwindcss to ^0.6.14

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
prettier-plugin-tailwindcss	^0.6.11 -> ^0.6.14

---

Release Notes

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

v0.6.14

Compare Source

• Add support for OXC + Hermes Prettier plugins (#​376, #​380)
• Sort template literals in Angular expressions (#​377)
• Don't repeatedly add backslashes to escape sequences when formatting (#​381)

v0.6.13

Compare Source

• Prevent Svelte files from breaking when there are duplicate classes (#​359)
• Ensure prettier-plugin-multiline-arrays and prettier-plugin-jsdoc work when used together with this plugin (#​372)

v0.6.12

Compare Source

• Add internal (unsupported) option to load Tailwind CSS using a different package name (#​366)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
dev-astral	Ready	Preview	Comment	Sep 1, 2025 6:10pm
explorer	Ready	Preview	Comment	Sep 1, 2025 6:10pm

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​nx/​nx-darwin-arm64@​20.5.0
	@​nx/​nx-darwin-x64@​20.5.0
	@​nx/​nx-freebsd-x64@​20.5.0
	@​nx/​nx-linux-arm-gnueabihf@​20.5.0
	@​nx/​nx-linux-arm64-gnu@​20.5.0
	@​nx/​nx-linux-arm64-musl@​20.5.0
	@​nx/​nx-linux-x64-gnu@​20.5.0
	@​nx/​nx-linux-x64-musl@​20.5.0
	@​nx/​nx-win32-arm64-msvc@​20.5.0
	@​nx/​nx-win32-x64-msvc@​20.5.0
	@​types/​ioredis@​5.0.0
	aggregate-error@​3.1.0
	@​npmcli/​name-from-folder@​2.0.0
	@​npmcli/​node-gyp@​3.0.0
	@​pkgr/​core@​0.2.0
	@​jest/​schemas@​29.6.3
	common-ancestor-path@​1.0.1
	chownr@​2.0.0
	@​subql/​types@​3.14.1
	@​subql/​common-substrate@​4.5.2
	@​types/​minimist@​1.2.5
	abbrev@​2.0.0
	@​typescript-eslint/​visitor-keys@​8.27.0
	@​types/​express@​5.0.3
	@​typescript-eslint/​parser@​8.27.0
	array-ify@​1.0.0
	@​isaacs/​string-locale-compare@​1.1.0
	@​types/​minimatch@​5.1.2 ⏵ 3.0.5			-1
	eslint-config-prettier@​9.1.0
	@​npmcli/​query@​3.1.0
	@​yarnpkg/​parsers@​3.0.2
	@​tufjs/​models@​2.0.1
	@​types/​pg@​8.15.5
See 161 more rows in the dashboard

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		[email protected] has a Critical CVE. CVE: GHSA-cchq-frgv-rjh5 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: <= 3.9.19 Patched version: No patched versions From: ? → npm/@subql/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] has a Critical CVE. CVE: GHSA-g644-9gfx-q4q4 vm2 Sandbox Escape vulnerability (CRITICAL) Affected versions: <= 3.9.19 Patched version: No patched versions From: ? → npm/@subql/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		@webbuf/[email protected] has Obfuscated code. Confidence: 0.90 Location: Package overview From: ? → npm/@autonomys/[email protected] → npm/@webbuf/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@webbuf/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] is Protestware or potentially unwanted behavior. Note: This package prints a protestware console message on install regarding Ukraine for users with Russian language locale From: ? → npm/@subql/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is protestware? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Consider that consuming this package may come along with functionality unrelated to its primary purpose. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] is Protestware or potentially unwanted behavior. Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts. From: ? → npm/@subql/[email protected] → npm/[email protected] ℹ Read more on: This package | This alert | What is protestware? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Consider that consuming this package may come along with functionality unrelated to its primary purpose. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report