chore(deps): update all non-major dependencies #508
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:
^9.29.0
->^9.30.1
^0.4.2
->^0.5.0
10.12.3
->10.12.4
^3.6.1
->^3.6.2
^1.20250620.0
->^1.20250705.0
^4.21.2
->^4.23.0
Release Notes
eslint/eslint (eslint)
v9.30.1
Compare Source
v9.30.0
Compare Source
unjs/eslint-config (eslint-config-unjs)
v0.5.0
Compare Source
compare changes
📦 Build
❤️ Contributors
pnpm/pnpm (pnpm)
v10.12.4
Compare Source
Patch Changes
Fix
pnpm licenses
command for local dependencies #9583.Fix a bug in which
pnpm ls --filter=not-exist --json
prints nothing instead of an empty array #9672.Fix a deadlock that sometimes happens during peer dependency resolution #9673.
Running
pnpm install
afterpnpm fetch
should hoist all dependencies that need to be hoisted.Fixes a regression introduced in [v10.12.2] by [#9648]; resolves [#9689].
[v10.12.2]: https://redirect.github.com/pnpm/pnpm/releases/tag/v10.12.2Add commentMore actions
[#9648]: https://github.com/pnpm/pnpm/pull/9648
[#9689]: https://github.com/pnpm/pnpm/issues/9689
prettier/prettier (prettier)
v3.6.2
Compare Source
diff
Markdown: Add missing blank line around code block (#17675 by @fisker)
cloudflare/workerd (workerd)
v1.20250705.0
Compare Source
What's Changed
Full Changelog: cloudflare/workerd@v1.20250704.0...v1.20250705.0
v1.20250704.0
Compare Source
What's Changed
Full Changelog: cloudflare/workerd@v1.20250703.0...v1.20250704.0
v1.20250703.0
Compare Source
What's Changed
Full Changelog: cloudflare/workerd@v1.20250702.0...v1.20250703.0
v1.20250702.0
Compare Source
What's Changed
Full Changelog: cloudflare/workerd@v1.20250701.0...v1.20250702.0
v1.20250701.0
Compare Source
What's Changed
Full Changelog: cloudflare/workerd@v1.20250628.0...v1.20250701.0
v1.20250628.0
Compare Source
What's Changed
Full Changelog: cloudflare/workerd@v1.20250627.0...v1.20250628.0
v1.20250627.0
Compare Source
What's Changed
Full Changelog: cloudflare/workerd@v1.20250626.0...v1.20250627.0
cloudflare/workers-sdk (wrangler)
v4.23.0
Compare Source
Minor Changes
#9535
56dc5c4
Thanks @penalosa! - In 2023 we announced breakpoint debugging support for Workers, which meant that you could easily debug your Worker code in Wrangler's built-in devtools (accessible via the[d]
hotkey) as well as multiple other devtools clients, including VSCode. For most developers, breakpoint debugging via VSCode is the most natural flow, but until now it's required manually configuring alaunch.json
file, runningwrangler dev
, and connecting via VSCode's built-in debugger.Now, using VSCode's built-in JavaScript Debug Terminals, there are just two steps: open a JS debug terminal and run
wrangler dev
(orvite dev
). VSCode will automatically connect to your running Worker (even if you're running multiple Workers at once!) and start a debugging session.#9810
8acaf43
Thanks @WillTaylorDev! - WC-3626 Pull branch name from WORKERS_CI_BRANCH if exists.Patch Changes
#9775
4309bb3
Thanks @vicb! - Cap the number of errors and warnings for bulk KV put to avoid consuming too much memory#9799
d11288a
Thanks @penalosa! - Better messaging for account owned tokens inwrangler whoami
Updated dependencies [
56dc5c4
]:v4.22.0
Compare Source
Minor Changes
#7871
f2a8d4a
Thanks @dario-piotrowicz! - add support for assets bindings togetPlatformProxy
this change makes sure that that
getPlatformProxy
, when the input configurationfile contains an assets field, correctly returns the appropriate asset binding proxy
example:
Patch Changes
#9717
d2f2f72
Thanks @nikitassharma! - Containers should default to a "dev" instance type when no instance type is specified in the wrangler config#9620
1b967ea
Thanks @gpanders! - Simplify containers images list output format#9684
94a340e
Thanks @WillTaylorDev! - Select only successfully deployed deployments when tailing.Configuration
📅 Schedule: Branch creation - "after 2am and before 3am" (UTC), Automerge - "after 1am and before 2am" (UTC).
🚦 Automerge: Enabled.
♻ 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.