Skip to content
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

Upgrade prettier since the old one is incompatible with newer libc versions #7741

Merged
merged 3 commits into from
Oct 16, 2024

Conversation

tempoz
Copy link
Contributor

@tempoz tempoz commented Oct 16, 2024

Ran into this on ubuntu 2204 when trying get buildbuddy building on arm.

jsxBracketSameLine is deprecated, now just bracketSameLine: https://prettier.io/blog/2021/09/09/2.4.0.html#:~:text=This%20release%20renames%20the%20jsxBracketSameLine,such%20as%20class%20static%20blocks

--loglevel was renamed to --log-level

Related issues: N/A

@tempoz tempoz requested a review from jdhollen October 16, 2024 18:25
@tempoz tempoz merged commit 28262a9 into master Oct 16, 2024
15 checks passed
@tempoz tempoz deleted the prettier-upgrade branch October 16, 2024 18:43
@tempoz tempoz removed the request for review from tylerwilliams October 16, 2024 18:57
bduffany added a commit that referenced this pull request Nov 13, 2024
The version upgrade in
#7741 is causing
unexpected prettier diffs whenever we change certain files. This is
because prettier 3.x introduced new formatting rules, but our prettier
script only checks/formats changed files. So, in the upgrade PR,
Checkstyle didn't complain about the formatting now being incorrect
after the upgrade, and the latent formatting errors are being surfaced
in PRs only as the files are edited.

This PR reverts prettier back to 2.1.1 and updates Checkstyle to catch
this error in CI - if the prettier version in yarn.lock changes, then
all files are checked/formatted, not just changed files.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants