-
Notifications
You must be signed in to change notification settings - Fork 10
build(deps): bump prettier from 3.6.2 to 3.7.3 #508
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Bumps [prettier](https://github.com/prettier/prettier) from 3.6.2 to 3.7.3. - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](prettier/prettier@3.6.2...3.7.3) --- updated-dependencies: - dependency-name: prettier dependency-version: 3.7.3 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dependabot merge
|
Beginning January 27, 2026, Dependabot will no longer support the @dependabot merge command. Please use GitHub's native pull request controls instead. Please see the changelog announcement for additional details. |
|
Sorry, only users with push access can use that command. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR updates prettier from 3.6.2 -> 3.7.3 (package.json + package-lock.json). Codacy analysis shows the project is up to standards; there are no new issues reported. If you rely on Prettier integrations (editors/CI), verify CLI behavior and CI formatting steps post-upgrade — the release notes mention fixes to API getFileInfo(), quote handling, and printer perf.
About this PR
- Since this upgrades Prettier (tooling), run CI that includes formatting/linting steps and integration with editors/IDE plugins (e.g., VSCode) to ensure no regressions (release notes mention API changes that previously affected the VSCode extension).
Low confidence findings
- PR description is automatically generated by Dependabot. Consider adding a short confirmation that you ran the formatter and CI locally (or a note to trigger CI) so maintainers know formatting/linters pass with the new Prettier.
💡 Codacy uses AI. Check for mistakes.
| "version": "3.7.3", | ||
| "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.7.3.tgz", | ||
| "integrity": "sha512-QgODejq9K3OzoBbuyobZlUhznP5SKwPqp+6Q6xw6o8gnhr4O85L2U915iM2IDcfF2NPXVaM9zlo9tdwipnYwzg==", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
❗ Issue
package-lock.json: updated node_modules/prettier entry to 3.7.3 (version/resolved/integrity) and added top-level prettier lock entries. After lockfile updates, run a fresh install (npm ci) in CI to verify the lockfile is consistent and that no other package resolutions changed unexpectedly.
Also ensure package-lock.json was regenerated with the same npm version used in CI to avoid lockfile differences across environments.
🟡 Medium risk
| "postcss-styled-syntax": "^0.7.1", | ||
| "postcss-syntax": "^0.36.2", | ||
| "prettier": "^3.6.2", | ||
| "prettier": "^3.7.3", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Suggestion
Bumped Prettier version in package.json dependency list. This changes the formatting engine used by the repo; please ensure:
- CI formatting/linting jobs (and any pre-commit hooks) are compatible with Prettier 3.7.3.
- Any editor/IDE plugins (VSCode extension) used by the team are updated — release notes mention a getFileInfo() fix that previously broke the VSCode extension.
If you want me to, I can run format and push updates to affected files.
🟡 Medium risk
| "version": "3.7.3", | ||
| "resolved": "https://registry.npmjs.org/prettier/-/prettier-3.7.3.tgz", | ||
| "integrity": "sha512-QgODejq9K3OzoBbuyobZlUhznP5SKwPqp+6Q6xw6o8gnhr4O85L2U915iM2IDcfF2NPXVaM9zlo9tdwipnYwzg==" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
💡 Suggestion
package-lock.json: top-level prettie r entry updated to 3.7.3. Confirm any CI steps that call prettier programmatically (via API) still behave as expected — 3.7.x had internal API refactors noted in the changelog.
⚪ Low risk
|
Superseded by #509. |
Bumps prettier from 3.6.2 to 3.7.3.
Release notes
Sourced from prettier's releases.
Changelog
Sourced from prettier's changelog.
... (truncated)
Commits
fdfa670Release 3.7.32dce3ecFix typo27d6c64Revert previous change togetFileInfo(#18375)f4a7afaAdd types for config related functions (#18376)9266e3eAdd resolved test cases (#18358)3bfc014Bump Prettier dependency to 3.7.2081b846Clean changelog_unreleased03384c9Release 3.7.2514e51aRelease@prettier/plugin-hermes&@prettier/plugin-oxcv0.1.229a11aeFix comment in empty type literal (#18364)Maintainer changes
This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for prettier since your current version.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)