This repository has been archived by the owner on Dec 17, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2
chore(deps): update devdependencies (non-major) (minor) #432
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/devdependencies-(non-major)
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
8fa8007
to
dce8498
Compare
12d885a
to
38b3af4
Compare
94a2284
to
8746515
Compare
7aa326e
to
fae363a
Compare
3541bb3
to
7b852b4
Compare
7b852b4
to
d040701
Compare
d040701
to
224ded8
Compare
81a6b04
to
b241767
Compare
0a54953
to
4c33339
Compare
edae90c
to
a809a12
Compare
585df9c
to
93e1d38
Compare
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
ab7b15a
to
0ddd095
Compare
66cb3e6
to
c735110
Compare
c735110
to
68bc93f
Compare
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
6.5.0
->6.6.3
16.0.1
->16.1.0
20.16.10
->20.17.10
8.8.0
->8.18.1
8.8.0
->8.18.1
9.0.1
->9.1.0
13.15.0
->13.16.1
3.6.3
->3.7.0
3.3.3
->3.4.2
5.6.2
->5.7.2
Release Notes
testing-library/jest-dom (@testing-library/jest-dom)
v6.6.3
Compare Source
v6.6.2
Compare Source
Bug Fixes
v6.6.1
Compare Source
v6.6.0
Compare Source
testing-library/react-testing-library (@testing-library/react)
v16.1.0
Compare Source
typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)
v8.18.1
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.18.0
Compare Source
🚀 Features
🩹 Fixes
toString()
declarations are present for a type (#10432)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.17.0
Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.16.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.15.0
Compare Source
🚀 Features
ignoreConditionalTests
involving boolean!
operator (#10299)no-unsafe-type-assertion
(#10051)🩹 Fixes
as const satisfies
(#10315)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.14.0
Compare Source
🚀 Features
await using
statements (#10209)🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.13.0
Compare Source
🚀 Features
ignoreBooleanCoercion
(#9924)no-class-assign
rule ineslint-recommended
config (#10250)🩹 Fixes
undefined
(#10232)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.12.2
Compare Source
🩹 Fixes
considerDefaultExhaustiveForUnions
(#10223)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.12.1
Compare Source
This was a version bump only for eslint-plugin to align it with other projects, there were no code changes.
You can read about our versioning strategy and releases on our website.
v8.12.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.11.0
Compare Source
🚀 Features
🩹 Fixes
override
keyword (#10135)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.10.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.9.0
Compare Source
🩹 Fixes
eslint-plugin: [no-unnecessary-type-parameters] cannot assume variables are either type or value
scope-manager: [no-use-before-define] do not treat nested namespace aliases as variable references
eslint-plugin: [return-await] sync the behavior with await-thenable
eslint-plugin: [prefer-literal-enum-member] report a different error message when
allowBitwiseExpressions
is enabledeslint-plugin: [no-loop-func] sync from upstream base rule
eslint-plugin: [no-unused-vars] never report the naming of an enum member
eslint-plugin: correct use-at-your-own-risk type definitions
eslint-plugin: handle unions in await...for
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.8.1
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
v8.18.1
Compare 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.0
Compare Source
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.17.0
Compare 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.16.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.15.0
Compare 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.14.0
Compare 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.13.0
Compare 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.12.2
Compare 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.12.1
Compare 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.12.0
Compare 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.11.0
Compare 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.10.0
Compare Source
🚀 Features
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.9.0
Compare 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.8.1
Compare 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.
open-cli-tools/concurrently (concurrently)
v9.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: open-cli-tools/concurrently@v9.0.1...v9.1.0
cypress-io/cypress (cypress)
v13.16.1
Compare Source
Changelog: https://docs.cypress.io/app/references/changelog#13-16-1
v13.16.0
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-16-0
v13.15.2
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-15-2
v13.15.1
Compare Source
Changelog: https://docs.cypress.io/guides/references/changelog#13-15-1
import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)
v3.7.0
Compare Source
Minor Changes
#326
93ea130
Thanks @SukkaW! - This version has implemented theeslint-plugin-import-x
's v3 resolver interface. This allows you to use import/require to referenceeslint-import-resolver-typescript
directly in your ESLint flat config:Previously
Now
Note that this only works with
eslint-plugin-import-x@>=4.5.0
. You can't usecreateTypeScriptImportResolver
with the older versions ofeslint-plugin-import-x
or any existing versions ofeslint-plugin-import
.prettier/prettier (prettier)
v3.4.2
Compare Source
diff
Treat U+30A0 & U+30FB in Katakana Block as CJK (#16796 by @tats-u)
Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.
U+30A0 can be used as the replacement of the
-
in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン=サーンス”).Fix comments print on class methods with decorators (#16891 by @fisker)
Fix non-idempotent formatting (#16899 by @seiyab)
This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.
v3.4.1
Compare Source
diff
Remove unnecessary parentheses around assignment in
v-on
(#16887 by @fisker)<!-- Input --> <template> <button @​click="foo += 2">Click</button> </template> <!-- Prettier 3.4.0 --> <template> <button @​click="(foo += 2)">Click</button> </template> <!-- Prettier 3.4.1 --> <template> <button @​click="foo += 2">Click</button> </template>
v3.4.0
Compare Source
diff
🔗 Release Notes
microsoft/TypeScript (typescript)
v5.7.2
Compare Source
v5.6.3
Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "* 0-4,22-23 * * 1-5,* * * * 0,6" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, 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.