chore(deps): update all dependencies #5
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
from
02fd841 to
41b4f2f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
10 times, most recently
from
56224b7 to
756221f
Compare
renovate
bot
force-pushed
the
renovate/all
branch
10 times, most recently
from
23f3c41 to
255189b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
255189b to
fa8a38b
Compare
renovate
bot
force-pushed
the
renovate/all
branch
3 times, most recently
from
cbe4a6d to
5cd0029
Compare
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
8e876de to
e8a4f69
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
2 times, most recently
from
b61d582 to
124a7f9
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
d02ed0a to
98a3788
Compare
renovate
bot
force-pushed
the
renovate/all
branch
6 times, most recently
from
933b2ed to
2693b94
Compare
renovate
bot
force-pushed
the
renovate/all
branch
4 times, most recently
from
f7443a3 to
1c32bf0
Compare
renovate
bot
force-pushed
the
renovate/all
branch
from
1c32bf0 to
4de6fb0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
22.10.2->22.10.78.18.1->8.20.08.18.1->8.20.09.17.0->9.18.0^9.1.0->^10.0.0v3.28.0->v3.28.115.2.11->15.4.15.7.2->5.7.3^2.0.0->^3.0.0Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.20.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.19.1Compare Source
🩹 Fixes
declarekeyword (#10543)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.19.0Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.18.2Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.20.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.19.1Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.19.0Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.18.2Compare Source
This was a version bump only for parser to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
eslint/eslint (eslint)
v9.18.0Compare Source
prettier/eslint-config-prettier (eslint-config-prettier)
v10.0.1Compare Source
eslint-config-prettier
10.0.0
Major Changes
5be64beThanks @abrahamguo! - add support for @stylistic formatting rulesVersions before 10.0.0
Version 9.1.0 (2023-12-02)
ESLINT_CONFIG_PRETTIER_NO_DEPRECATEDenvironment variable.Version 9.0.0 (2023-08-05)
"unicode-bom": "off"to your config to disable it again, or run ESLint with--fixto fix all files according to the rule (add or remove BOM). Thanks to Nicolas Stepien (@nstepien)!Version 8.10.0 (2023-08-03)
Version 8.9.0 (2023-07-27)
Version 8.8.0 (2023-03-20)
Version 8.7.0 (2023-03-06)
Version 8.6.0 (2023-01-02)
Version 8.5.0 (2022-03-02)
Version 8.4.0 (2022-02-19)
Version 8.3.0 (2021-04-24)
Version 8.2.0 (2021-04-13)
Version 8.1.0 (2021-02-24)
Version 8.0.0 (2021-02-21)
Changed: All configs have been merged into one!
To upgrade, change:
{ "extends": [ "some-other-config-you-use", "prettier", "prettier/@​typescript-eslint", "prettier/babel", "prettier/flowtype", "prettier/react", "prettier/standard", "prettier/unicorn", "prettier/vue" ] }Into:
{ "extends": [ "some-other-config-you-use", "prettier" ] }The
"prettier"config now includes not just ESLint core rules, but also rules from all plugins. Much simpler!So … what’s the catch? Why haven’t we done this earlier? Turns out it’s just a sad mistake. I (@lydell) was confused when testing, and thought that turning off unknown rules in a config was an error. Thanks to Georgii Dolzhykov (@thorn0) for pointing this out!
If you use eslint-plugin-prettier, all you need is plugin:prettier/recommended:
{ "extends": [ "some-other-config-you-use", "plugin:prettier/recommended" ] }(The "prettier/prettier" config still exists separately. It’s the odd one out. The main
"prettier"config does not include the rules from it.)Changed: The CLI helper tool now only prints warnings for arrow-body-style and prefer-arrow-callback, just like other “special rules.” This means that if you’ve decided to use those rules and eslint-plugin-prettier at the same time, you’ll get warnings but exit code zero (success).
Version 7.2.0 (2021-01-18)
Version 7.1.0 (2020-12-19)
Version 7.0.0 (2020-12-05)
Changed: At least ESLint 7.0.0 is now required.
Changed: arrow-body-style and prefer-arrow-callback are no longer turned off by default. They only need to be turned off if you use eslint-plugin-prettier. If you do, add
"prettier/prettier"to your"extends"array to turn them off again.{ "extends": ["prettier", "prettier/prettier"], "plugins": ["prettier"], "rules": { "prettier/prettier": "error" } }Alternatively, update eslint-plugin-prettier to version 3.2.0 or later which automatically turns off these two rules in its
"plugin:prettier/recommended"config.The CLI helper tool only warns about these rules if you have the
"prettier/prettier"rule enabled for a file.Changed:
no-tabsis now a validatable rule. If you use it, you should enableallowIndentationTabsso that the rule works regardless of your Prettier config:{ "rules": { "no-tabs": ["error", { "allowIndentationTabs": true }] } }Changed: The CLI helper tool is now called just
eslint-config-prettierinstead ofeslint-config-prettier-check. This is so thatnpx eslint-config-prettieralways works regardless of whether you have already installedeslint-config-prettieror not: If you have, the local installation is used; if you haven’t,npxdownloads a temporary copy.Changed: The CLI helper tool no longer requires you to pipe the output of
eslint --print-configto it. Instead, it does that automatically for you via ESLint API:s added in ESLint v7.Before:
After:
Improved: The npm package is now 75% smaller.
Version 6.15.0 (2020-10-27)
Version 6.14.0 (2020-10-21)
Version 6.13.0 (2020-10-16)
Version 6.12.0 (2020-09-25)
Version 6.11.0 (2020-04-21)
Version 6.10.1 (2020-03-22)
npxwhen running the CLI helper tool.Version 6.10.0 (2020-01-28)
Version 6.9.0 (2019-12-27)
Version 6.8.0 (2019-12-25)
Version 6.7.0 (2019-11-19)
Version 6.6.0 (2019-11-17)
Version 6.5.0 (2019-10-26)
Version 6.4.0 (2019-10-05)
Version 6.3.0 (2019-09-10)
Version 6.2.0 (2019-09-03)
Version 6.1.0 (2019-08-19)
Version 6.0.0 (2019-06-25)
Changed: The CLI helper tool now considers no-confusing-arrow to conflict if you use the default value of its
allowParensoption. The default was changed totruein ESLint 6, which conflicts with Prettier.If the CLI helper tool gives you errors about this after upgrading, the solution is to change this:
{ "rules": { "no-confusing-arrow": ["error"] } }Into this:
{ "rules": { "no-confusing-arrow": ["error", { "allowParens": false }] } }The latter works in both ESLint 6 as well as in ESLint 5 and older.
Improved:
eslint --print-configusage instructions. The CLI tool help text as well as the documentation has been updated to suggest commands that work in ESLint 6.0 as well as in ESLint 5 and older. (Instead ofeslint --print-config ., useeslint --print-config path/to/main.js.)Version 5.1.0 (2019-06-25)
Version 5.0.0 (2019-06-15)
Removed: react/self-closing-comp. This rule was added in v4.1.0 not because it conflicted with Prettier but because it was unnecessary when using Prettier. However, in v1.18.0 Prettier stopped converting empty elements to self-closing elements. So the rule is not unnecessary anymore.
If you use Prettier v1.17.1 or older you should be able to upgrade eslint-config-prettier to v5.0.0 without having to do anything else.
If you use Prettier v1.18.0 or newer, you might get lint errors about for example changing
<div></div>into<div />. You have two options:eslint --fixif you prefer to enforce self-closing elements where possible. This should fix all the errors."react/self-closing-comp": "off"to your ESLint config if you use autofix from your editor and you face the same issue as Prettier did.Changed: Node.js 6 is no longer officially supported, but v5.0.0 should still work with it.
Version 4.3.0 (2019-05-16)
Version 4.2.0 (2019-04-25)
Version 4.1.0 (2019-02-26)
Version 4.0.0 (2019-01-26)
--fix. They are turned off by default, and the CLI helper tool will warn about them (but not error if you do enable them). This won’t break your linting checks, but do note that these rules will be disabled unless you explicitly enable them again, and that you might see new warnings when running the CLI helper tool.Version 3.6.0 (2019-01-19)
Version 3.5.0 (2019-01-16)
vue/no-layout-ruleslist, since there can be layout rules that don’t conflict with but rather complement Prettier.Version 3.4.0 (2019-01-13)
vue/no-layout-rulesconfig behind the scenes, so it should automatically stay up-to-date when new eslint-plugin-vue versions are released. Thanks to Michał Sajnóg (@michalsnik)!Version 3.3.0 (2018-11-11)
Version 3.2.0 (2018-11-10)
Version 3.1.0 (2018-09-22)
Version 3.0.1 (2018-08-13)
eslint --print-configusage instructions.Version 3.0.0 (2018-08-13)
Version 2.10.0 (2018-08-13)
Version 2.9.0 (2017-11-26)
Version 2.8.0 (2017-11-19)
Version 2.7.0 (2017-11-01)
Version 2.6.0 (2017-09-23)
Version 2.5.0 (2017-09-16)
Version 2.4.0 (2017-09-02)
Version 2.3.0 (2017-06-30)
Version 2.2.0 (2017-06-17)
Version 2.1.1 (2017-05-20)
Version 2.1.0 (2017-05-13)
Version 2.0.0 (2017-05-07)
Changed/Improved: The CLI helper tool is now more helpful.
Changed: The no-confusing-arrow is now a special rule again, since it might conflict with recent Prettier versions.
Removed: The
react/wrap-multilinesrule (which has been deprecated for a while), since it was removed in eslint-plugin-react@7.Version 1.7.0 (2017-04-19)
Version 1.6.0 (2017-04-05)
Version 1.5.0 (2017-03-04)
Version 1.4.1 (2017-02-28)
Version 1.4.0 (2017-02-26)
Version 1.3.0 (2017-02-21)
Version 1.2.0 (2017-02-14)
Version 1.1.1 (2017-02-12)
Version 1.1.0 (2017-02-10)
Version 1.0.3 (2017-02-03)
"extends": "prettier/react"now actually works.Version 1.0.2 (2017-01-30)
Version 1.0.1 (2017-01-29)
npm publishmistake.Version 1.0.0 (2017-01-29)
v10.0.0Compare Source
Major Changes
5be64beThanks @abrahamguo! - add support for @stylistic formatting rulesgithub/codeql-action (github/codeql-action)
v3.28.1Compare Source
CodeQL Action Changelog
See the releases page for the relevant changes to the CodeQL CLI and language packs.
3.28.1 - 10 Jan 2025
See the full CHANGELOG.md for more information.
lint-staged/lint-staged (lint-staged)
v15.4.1Compare Source
Patch Changes
#1504
1c7a45eThanks @iiroj! - Default TypeScript config filenames match JS equivalents.#1504
9cc18c9Thanks @iiroj! - Add missing conditional exports syntax for TypeScript types.v15.4.0Compare Source
Minor Changes
#1500
a8ec1ddThanks @iiroj! - Lint-staged now provides TypeScript types for the configuration and main Node.js API. You can use the JSDoc syntax in your JS configuration files:It's also possible to use the
.tsfile extension for the configuration if your Node.js version supports it. The--experimental-strip-typesflag was introduced in Node.js v22.6.0 and unflagged in v23.6.0, enabling Node.js to execute TypeScript files without additional configuration.Patch Changes
9b79364Thanks @iiroj! - Handle possible failures when logging user shell for debug info.v15.3.0Compare Source
Minor Changes
#1495
e69da9eThanks @iiroj! - Added more info to the debug logs so that "environment" info doesn't need to be added separately to GitHub issues.#1493
fa0fe98Thanks @iiroj! - Added more help messages around the automaticgit stashthat lint-staged creates as a backup (by default). The console output also displays the short git hash of the stash so that it's easier to recover lost files in case some fatal errors are encountered, or the process is killed before completing.For example:
where the backup can be seen with
git show 20addf8, orgit stash list:microsoft/TypeScript (typescript)
v5.7.3Compare Source
vitest-dev/vitest (vitest)
v3.0.1Compare Source
🐞 Bug Fixes
View changes on GitHub
v3.0.0Compare Source
🚨 Breaking Changes
spy.mockResetchanges - by @Lordfirespeed in https://github.com/vitest-dev/vitest/issues/6426 (db7a8)Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.