chore(deps-dev): bump prettier from 3.0.3 to 3.2.5

[dependabot]

Bumps prettier from 3.0.3 to 3.2.5.

Release notes

Sourced from prettier's releases.

3.2.5

🔗 Changelog

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

Changelog

Sourced from prettier's changelog.

3.2.5

diff

Support Angular inline styles as single template literal (#15968 by @​sosukesuzuki)

Angular v17 supports single string inline styles.

// Input
@Component({
  template: `<div>...</div>`,
  styles: `h1 { color: blue; }`,
})
export class AppComponent {}
// Prettier 3.2.4
@​Component({
template: &lt;div&gt;...&lt;/div&gt;,
styles: h1 { color: blue; },
})
export class AppComponent {}
// Prettier 3.2.5
@​Component({
template: &lt;div&gt;...&lt;/div&gt;,
styles: h1 { color: blue; },
})
export class AppComponent {}

Unexpected embedded formatting for Angular template (#15969 by @​JounQin)

Computed template should not be considered as Angular component template

// Input
const template = "foobar";
@​Component({
[template]: <h1>{{       hello }}</h1>,
})
export class AppComponent {}
</tr></table>

... (truncated)

Commits

• 7142cf3 Release 3.2.5
• 8cbee2e chore(deps): update glimmer to v0.88.1 (#15991)
• 45baee0 chore(deps): update dependency magic-string to v0.30.6 (#16022)
• 9fb32a1 Minor refactor to property print (#15924)
• 08f1940 Update install script for husky v9 (#16000)
• 6d0b1d2 Update yarn to v4.1.0 (#16021)
• c8ba8db chore(deps): update dependency @​angular/compiler to v17.1.2 (#16018)
• e2250ec chore(deps): update typescript-eslint to v6.20.0 (#16015)
• 02865f6 chore(deps): update dependency npm-run-all2 to v6.1.2 (#16017)
• 014ee5d chore(deps): update dependency hermes-parser to v0.19.0 (#16014)
• 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)

[github-actions]

Current branch is dependabot/npm_and_yarn/prettier-3.2.5.
(execution 7955208554 / attempt 1)

[github-actions]

Comment Pull Request - GitHub Actions

What is it ?

A GitHub action that comments with a given message the pull request linked to the pushed branch.
You can even put dynamic data thanks to Contexts and expression syntax.

Usage

Classic usage

on: pull_request

jobs:
  example_comment_pr:
    runs-on: ubuntu-latest
    name: An example job to comment a PR
    steps:
      - name: Checkout
        uses: actions/checkout@v3

      - name: Comment PR
        uses: thollander/actions-comment-pull-request@v2
        with:
          message: |
            Hello world ! :wave:

Comment a file content

Thanks to the filePath input, a file content can be commented.
You can either pass an absolute filePath or a relative one that will be by default retrieved from GITHUB_WORKSPACE.
(Note that if both a message and filePath are provided, message will take precedence.)

- name: PR comment with file
  uses: thollander/actions-comment-pull-request@v2
  with:
    filePath: /path/to/file.txt

Setting reactions

You can also set some reactions on your comments through the reactions input.
It takes only valid reactions and adds it to the comment you've just created. (See https://docs.github.com/en/rest/reactions#reaction-types)

- name: PR comment with reactions
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      Hello world ! :wave:
    reactions: eyes, rocket

Specifying which pull request to comment on

You can explicitly input which pull request should be commented on by passing the pr_number input.
That is particularly useful for manual workflow for instance (workflow_run).

...
- name: Comment PR
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      Hello world ! :wave:
    pr_number: 123 # This will comment on pull request #123

Update a comment

Editing an existing comment is also possible thanks to the comment_tag input.

Thanks to this parameter, it will be possible to identify your comment and then to upsert on it.
If the comment is not found at first, it will create a new comment.

That is particularly interesting while committing multiple times in a PR and that you just want to have the last execution report printed. It avoids flooding the PR.

...
- name: Comment PR with execution number
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      _(execution **${{ github.run_id }}** / attempt **${{ github.run_attempt }}**)_
    comment_tag: execution

Note: the input mode can be used to either upsert (by default) or recreate the comment (= delete and create)

Delete a comment

Deleting an existing comment is also possible thanks to the comment_tag input combined with mode: delete.

This will delete the comment at the end of the job.

...
- name: Write a comment that will be deleted at the end of the job
  uses: thollander/actions-comment-pull-request@v2
  with:
    message: |
      The PR is being built...
    comment_tag: to_delete
    mode: delete

Inputs

Action inputs

Name	Description	Required	Default
GITHUB_TOKEN	Token that is used to create comments. Defaults to ${{ github.token }}	✅
message	Comment body
filePath	Path of the file that should be commented
reactions	List of reactions for the comment (comma separated). See https://docs.github.com/en/rest/reactions#reaction-types
pr_number	The number of the pull request where to create the comment		current pull-request/issue number (deduced from context)
comment_tag	A tag on your comment that will be used to identify a comment in case of replacement
mode	Mode that will be used to update comment (upsert/recreate/delete)		upsert
create_if_not_exists	Whether a comment should be created even if comment_tag is not found		true

Outputs

Action outputs

You can get some outputs from this actions :

Name	Description
id	Comment id that was created or updated
body	Comment body
html_url	URL of the comment created or updated

Example output

- name: Comment PR
  uses: thollander/actions-comment-pull-request@v2
  id: hello
  with:
    message: |
      Hello world ! :wave:
- name: Check outputs
  run: |
    echo "id : ${{ steps.hello.outputs.id }}"
    echo "body : ${{ steps.hello.outputs.body }}"
    echo "html_url : ${{ steps.hello.outputs.html_url }}"

Permissions

Depending on the permissions granted to your token, you may lack some rights.
To run successfully, this actions needs at least :

permissions: 
   pull-requests: write 

Add this in case you get Resource not accessible by integration error.
See jobs.<job_id>.permissions for more information.

Note that, if the PR comes from a fork, it will have only read permission despite the permissions given in the action for the pull_request event.
In this case, you may use the pull_request_target event. With this event, permissions can be given without issue (the difference is that it will execute the action from the target branch and not from the origin PR).

Contributing

Build

The build steps transpiles the src/main.ts to lib/index.js which is used in a NodeJS environment.
It is handled by vercel/ncc compiler.

$ npm run build

[github-actions]

Content of file referenced with absolute path

[thollander]

@dependabot rebase

[dependabot]

Looks like this PR is already up-to-date with main! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.