chore(deps): bump prettier from 3.3.0 to 3.3.2

[dependabot[bot]]

Bumps prettier from 3.3.0 to 3.3.2.

Release notes

Sourced from prettier's releases.

3.3.2

🔗 Changelog

3.3.1

🔗 Changelog

Changelog

Sourced from prettier's changelog.

3.3.2

diff

Fix handlebars path expressions starts with @ (#16358 by @​Princeyadav05)

{{! Input }}
<div>{{@x.y.z}}</div>
{{! Prettier 3.3.1 }}
<div>{{@​x}}</div>
{{! Prettier 3.3.2 }}
<div>{{@​x.y.z}}</div>

3.3.1

diff

Preserve empty lines in front matter (#16347 by @​fisker)

<!-- Input -->
---
foo:
  - bar1


bar2


bar3



Markdown
<!-- Prettier 3.3.0 -->

foo:

bar1
bar2
bar3


Markdown
<!-- Prettier 3.3.1 -->
</tr></table>

... (truncated)

Commits

• 1596a60 Release 3.3.2
• aebcee5 chore(deps): update dependency esbuild to v0.21.5 (#16379)
• 57aa928 chore(deps): update dependency c8 to v10 (#16380)
• c3d0b7f chore(deps): update typescript-eslint to v7.13.0 (#16376)
• 27c35db chore(deps): update dependency codemirror-graphql to v2.0.12 (#16369)
• 6de3258 chore(deps): update dependency jest to v30.0.0-alpha.5 (#16371)
• b5f983d Upgrade yarn to v4.3.0 (#16377)
• d6f37c4 chore(deps): update dependency browserslist to v4.23.1 (#16368)
• 5055b7d chore(deps): update dependency execa to v9.2.0 (#16372)
• f4608cc chore(deps): update dependency cspell to v8.8.4 (#16370)
• 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 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)

[github-actions[bot]]

Our Pull Request Approval Process

We have these basic policies to make the approval process smoother for our volunteer team.

Testing Your Code

Please make sure your code passes all tests and there are no merge conflicts.

The process helps maintain accurate and well-formatted documentation and is a prerequisite for getting your PR approved. Assigned reviewers regularly review the PR queue and tend to focus on PRs that are passing.

Reviewers

When your PR has been assigned reviewers contact them to get your code reviewed and approved via:

1. comments in this PR or
2. our slack channel

Reviewing Your Code

Your reviewer(s) will have the following roles:

1. arbitrators of future discussions with other contributors about the validity of your changes
2. point of contact for evaluating the validity of your work
3. person who verifies matching issues by others that should be closed.
4. person who gives general guidance in fixing your tests

CONTRIBUTING.md

Read our CONTRIBUTING.md file. Most importantly:

1. PRs with issues not assigned to you will be closed by the reviewer
2. Fix the first comment in the PR so that each issue listed automatically closes

Other

1. :dart: Please be considerate of our volunteers' time. Contacting the person who assigned the reviewers is not advised unless they ask for your input. Do not @ the person who did the assignment otherwise.