-
Notifications
You must be signed in to change notification settings - Fork 0
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
Update dependencies (patch) #344
Open
renovate
wants to merge
1
commit into
main
Choose a base branch
from
renovate/dependencies-(patch)
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.
Open
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
changed the title
Update dependency @types/node to v22.9.1
Update dependency @types/node to v22.9.2
Nov 23, 2024
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
from
November 23, 2024 01:31
247e2f9
to
6d64e5b
Compare
renovate
bot
changed the title
Update dependency @types/node to v22.9.2
Update dependency @types/node to v22.9.3
Nov 23, 2024
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
from
November 23, 2024 06:09
6d64e5b
to
21030d5
Compare
renovate
bot
changed the title
Update dependency @types/node to v22.9.3
Update dependency @types/node to v22.9.4
Nov 25, 2024
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
from
November 25, 2024 22:03
21030d5
to
26671fb
Compare
renovate
bot
changed the title
Update dependency @types/node to v22.9.4
Update dependency @types/node to v22.9.4 - autoclosed
Nov 26, 2024
renovate
bot
changed the title
Update dependency @types/node to v22.9.4 - autoclosed
Update dependency @types/node to v22.9.4
Nov 26, 2024
renovate
bot
changed the title
Update dependency @types/node to v22.9.4
Update dependency vitest to v2.1.6
Nov 26, 2024
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
6 times, most recently
from
December 2, 2024 03:43
d360f16
to
05338d5
Compare
renovate
bot
changed the title
Update dependency vitest to v2.1.6
Update dependency vitest to v2.1.7
Dec 2, 2024
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
from
December 2, 2024 14:11
05338d5
to
ef8eb18
Compare
renovate
bot
changed the title
Update dependency vitest to v2.1.7
Update dependency vitest to v2.1.8
Dec 2, 2024
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
2 times, most recently
from
December 4, 2024 11:38
1bbdbb7
to
a2d385a
Compare
renovate
bot
changed the title
Update dependency vitest to v2.1.8
Update dependencies (patch)
Dec 4, 2024
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
2 times, most recently
from
December 11, 2024 15:33
ce4f186
to
b5e6700
Compare
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
3 times, most recently
from
December 21, 2024 07:43
3ffdfc6
to
2bffdae
Compare
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
4 times, most recently
from
January 5, 2025 12:45
e53a510
to
ea1e9df
Compare
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
3 times, most recently
from
January 13, 2025 22:07
9ea0435
to
6f58671
Compare
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
2 times, most recently
from
January 17, 2025 04:30
bae6dd9
to
0e9ab32
Compare
renovate
bot
force-pushed
the
renovate/dependencies-(patch)
branch
from
January 17, 2025 17:07
0e9ab32
to
0a8cd66
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:
12.1.1
->12.1.2
22.10.1
->22.10.7
11.0.0
->11.0.1
3.4.1
->3.4.2
5.7.2
->5.7.3
3.0.1
->3.0.2
Release Notes
rollup/plugins (@rollup/plugin-typescript)
v12.1.2
2024-12-15
Bugfixes
isaacs/node-glob (glob)
v11.0.1
Compare Source
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.
microsoft/TypeScript (typescript)
v5.7.3
Compare Source
vitest-dev/vitest (vitest)
v3.0.2
Compare Source
🐞 Bug Fixes
expect().resolves/rejects
chain typings - by @hi-ogawa in https://github.com/vitest-dev/vitest/issues/7273 (fa415)View changes on GitHub
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.