build(deps-dev): bump prettier from 2.8.8 to 3.2.4

[dependabot]

Bumps prettier from 2.8.8 to 3.2.4.

Release notes

Sourced from prettier's releases.

3.2.4

• Fix .eslintrc.json format #15947

🔗 Changelog

3.2.3

• Format tsconfig.json file with jsonc parser #15927

🔗 Changelog

3.2.2

🔗 Changelog

3.2.1

🔗 Changelog

3.2.0

diff

🔗 Release note

3.1.1

🔗 Changelog

3.1.0

diff

🔗 Release note

3.0.3

🔗 Changelog

3.0.2

🔗 Changelog

3.0.1

🔗 Changelog

3.0.0

diff

🔗 Release note

3.0.0-alpha.6

What's Changed

• Update .d.ts files of plugins to use export default ... by @​fisker in prettier/prettier#14435

Other changes since v2, see 3.0.0-alpha.1 release notes

Full Changelog: prettier/prettier@3.0.0-alpha.5...3.0.0-alpha.6

... (truncated)

Changelog

Sourced from prettier's changelog.

3.2.4

diff

Fix incorrect parser inference (#15947 by @​fisker)

Files like .eslintrc.json were incorrectly formatted as JSONC files.

// Input
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "jsonc" }
// Prettier 3.2.4
prettier --file-info .eslintrc.json
{ "ignored": false, "inferredParser": "json" }

3.2.3

diff

Throw errors for invalid code (#15881 by @​fisker, @​Josh-Cena, @​auvred)

// Input
1++;
// Prettier 3.2.2
1++;
// Prettier 3.2.3
SyntaxError: Invalid left-hand side expression in unary operation (1:1)
> 1 | 1++;
| ^

// Input
try {} catch (error = 1){}
// Prettier 3.2.2
try {
} catch (error) {}
// Prettier 3.2.3
SyntaxError: Catch clause variable cannot have an initializer. (1:23)
</tr></table>

... (truncated)

Commits

• 03822f5 Release 3.2.4
• 1cd4d9c Fix JSONC filenames list (#15947)
• 6c6a332 Spellcheck
• 75ec1f7 Fix lock file
• dda00cd Clean changelog_unreleased
• c12e3c6 Git blame ignore 3.2.3
• 4985be5 Bump Prettier dependency to 3.2.3
• 38c0d21 Update dependents count
• 42ba437 Release 3.2.3
• 99c873d chore(deps): update typescript-eslint to v6.19.0 (#15939)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[vercel]

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

Name	Status	Preview	Updated (UTC)
fern-cloudflare	✅ Ready (Inspect)	Visit Preview	Jan 31, 2024 11:03pm
fern-dev	✅ Ready (Inspect)	Visit Preview	Jan 31, 2024 11:03pm

4 Ignored Deployments

Name	Status	Preview	Updated (UTC)
fern-cohere	⬜️ Ignored (Inspect)		Jan 31, 2024 11:03pm
fern-finch	⬜️ Ignored (Inspect)		Jan 31, 2024 11:03pm
fern-prod	⬜️ Ignored (Inspect)	Visit Preview	Jan 31, 2024 11:03pm
private-docs	⬜️ Ignored (Inspect)	Visit Preview	Jan 31, 2024 11:03pm

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
5099597	Triggered	Generic High Entropy Secret	b746ac0	packages/ui/public-docs-bundle/.env-cmdrc.cjs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>