-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
Bump prettier from 3.0.3 to 3.1.0 #30241
Conversation
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 squash and merge
One of your CI runs failed on this pull request, so Dependabot won't merge it. Dependabot will still automatically merge this pull request if you amend it and your tests pass. |
c5d6b3f
to
fbc836e
Compare
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 squash and merge
Bumps [prettier](https://github.com/prettier/prettier) from 3.0.3 to 3.1.0. - [Release notes](https://github.com/prettier/prettier/releases) - [Changelog](https://github.com/prettier/prettier/blob/main/CHANGELOG.md) - [Commits](prettier/prettier@3.0.3...3.1.0) --- updated-dependencies: - dependency-name: prettier dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
fbc836e
to
548586f
Compare
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 squash and merge
I believe these are the changes that must land in content first for this: |
See #30243 |
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.
Technical "request changes" so that it doesn't get merged automatically
...s/en-us/learn/tools_and_testing/client-side_javascript_frameworks/svelte_typescript/index.md
Show resolved
Hide resolved
...s/en-us/learn/tools_and_testing/client-side_javascript_frameworks/svelte_typescript/index.md
Show resolved
Hide resolved
...us/learn/tools_and_testing/client-side_javascript_frameworks/svelte_variables_props/index.md
Show resolved
Hide resolved
files/en-us/web/api/webgl_api/by_example/hello_vertex_attributes/index.md
Show resolved
Hide resolved
@@ -215,7 +215,7 @@ if (!(mycar instanceof Car)) { | |||
This is really different from: | |||
|
|||
```js example-bad | |||
if (!mycar instanceof Car) { | |||
if ((!mycar) instanceof Car) { |
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.
[mdn-linter] reported by reviewdog 🐶
if ((!mycar) instanceof Car) { | |
if (!mycar instanceof Car) { |
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.
Accepted this one, added a no-lint
in a subsequent commit.
…x.md Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@bsmth I've merged both PR into one: that way, when we land this one, everything should be fixed. (I used
I wonder if "lint and review content files" fails because the linter runs with the Prettier from Yari (and it may be 3.0.0!) instead of the new version. I'm away this morning, so I'm a bit afraid of landing this now as I think it may lead to lint errors elsewhere, and I won't be there to do a revert. My 'Request for change' is purely technical (to be sure the MDN bot will not merge this on its own), so if you want to go ahead, feel free to override it; I wouldn't mind. |
Is that what's happening? That would be surprising. Prettier counterpart in Yari is mdn/yari#10016 although it would be great to check if this is the case with the Prettier version. I will take a look today 👀 |
@teoli2003 and @bsmth for security reasons in linting workflow we run scripts from The best way in such case is to push locally linted code to PR branch and force merge the PR. |
So, it looks like all will be "normal" once we push this. |
Gotcha, tnx. It might be nice to have this documented in https://github.com/mdn/content/tree/main/.github/workflows for future (adding a README.md in this dir, possibly). |
@teoli2003 Heads up that you checked in an entire |
Bumps prettier from 3.0.3 to 3.1.0.
Release notes
Sourced from prettier's releases.
Changelog
Sourced from prettier's changelog.
Commits
e8ac9f8
Release 3.1.06a1d409
chore(deps): update dependency eslint-plugin-regexp to v2 (#15521)f4d93d3
chore(deps): update dependency esbuild to v0.19.5 (#15630)4fc71a5
chore(deps): update dependency flow-parser to v0.221.0 (#15637)d452f45
chore(deps): update dependency eslint-plugin-jest to v27.6.0 (#15635)eb84a60
chore(deps): update dependency@types/estree
to v1.0.5 (#15625)2af23ee
chore(deps): update dependency webpack to v5.89.0 (#15640)8f27c73
chore(deps): update dependency eslint-plugin-unicorn to v49 (#15642)cdc5f5a
chore(deps): update dependency webpack to v5.89.0 (#15639)14607ef
chore(deps): update dependency eslint-plugin-n to v16.3.1 (#15636)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 will merge this PR once CI passes on it, as requested by @mdn-bot.
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)