chore(deps): update all non-major dependencies #211
Merged
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:
^1.2.4->^1.2.5^1.2.8->^1.2.9^1.2.47->^1.2.48^1.2.3->^1.2.4^1.0.579->^1.0.586^3.0.0->^3.0.1^1.8.0->^1.9.0^24.2.1->^24.3.0^10.2.2->^10.2.3^1.1.1->^1.1.2^1.54.2->^1.55.010.14.0->10.15.0^7.1.1->^7.1.3^3.0.5->^3.0.6^4.28.1->^4.31.0Release Notes
nuxt/eslint (@nuxt/eslint-config)
v1.9.0Compare Source
🚀 Features
🐞 Bug Fixes
defineNuxtConfigas ESLint's globals, close #603 - by @antfu in https://github.com/nuxt/eslint/issues/603 (2e67f)View changes on GitHub
antfu-collective/bumpp (bumpp)
v10.2.3Compare Source
🐞 Bug Fixes
-aalias support for--all- by @kingyue737 in https://github.com/antfu-collective/bumpp/issues/93 (7c0bb)View changes on GitHub
antfu-collective/local-pkg (local-pkg)
v1.1.2Compare Source
No significant changes
View changes on GitHub
microsoft/playwright (playwright-core)
v1.55.0Compare Source
pnpm/pnpm (pnpm)
v10.15.0Compare Source
Minor Changes
cleanupUnusedCatalogsconfiguration. When set totrue, pnpm will remove unused catalog entries during installation #9793.@*/pnpm-plugin-*#9780.pnpm config getnow prints an INI string for an object value #9797.pnpm config getnow accepts property paths (e.g.pnpm config get catalog.react,pnpm config get .catalog.react,pnpm config get 'packageExtensions["@​babel/parser"].peerDependencies["@​babel/types"]'), andpnpm config setnow accepts dot-leading or subscripted keys (e.g.pnpm config set .ignoreScripts true).pnpm config get --jsonnow prints a JSON serialization of config value, andpnpm config set --jsonnow parses the input value as JSON.Patch Changes
pnpm createcommand, must verify whether the node version is supported even if a cache already exists #9775.*/*to theAcceptheader to avoid getting a 406 error on AWS CodeArtifact #9862.pnpm dlx pkg --helpdoesn't pass--helptopkg#9823.vitejs/vite (vite)
v7.1.3Compare Source
Features
generateCodeFrame(#20640) (1559577)Bug Fixes
Performance Improvements
resolveConfig(#20646) (f691f57)Miscellaneous Chores
Code Refactoring
importin worker threads (#20641) (530687a)Tests
checkNodeVersiontest (#20647) (731d3e6)v7.1.2Compare Source
Bug Fixes
[vite]prefixes to debug logs (#20595) (7cdef61)npm:prefix as a built-in module (#20558) (ab33803)Miscellaneous Chores
@jridgewell/remappingfrom@ampproject/remapping(#20577) (0a6048a)vuejs/language-tools (vue-tsc)
v3.0.6Compare Source
cloudflare/workers-sdk (wrangler)
v4.31.0Compare Source
Minor Changes
#10314
9b09751Thanks @dario-piotrowicz! - Show possible local vs. dashboard diff information on deploysWhen re-deploying a Worker using
wrangler deploy, if the configuration has been modified in the Cloudflare dashboard, the local configuration will overwrite the remote one. This can lead to unexpected results for users. To address this, currentlywrangler deploywarns users about potential configuration overrides (without presenting them) and prompts them to confirm whether they want to proceed.The changes here improve the above flow in the following way:
wrangler deploynow displays a git-like diff showing the differences between the dashboard and local configurations. This allows users to review and understand the impact of their changes before confirming the deployment.#10334
cadf19aThanks @jonesphillip! - Added queues subscription command to Wrangler including create, update, delete, get, listPatch Changes
#10374
20520faThanks @edmundhung! - Simplify debug package resolution with nodejs_compatA patched version of
debugwas previously introduced that resolved the package to a custom implementation. However, this caused issues due to CJS/ESM interop problems. We now resolve thedebugpackage to use the Node.js implementation instead.#10249
875197aThanks @penalosa! - Support JSRPC for remote bindings. This unlocks:Updated dependencies [
565c3a3,ddadb93,20520fa,875197a]:v4.30.0Compare Source
Minor Changes
76a6701Thanks @garvit-gupta! - feat: Add Wrangler command for Vectorize list-vectors operationPatch Changes
#10217
979984bThanks @veggiedefender! - Increase the maxBuffer size for capnp uploads#10356
80e964cThanks @WillTaylorDev! - fix: Update regex for valid branch name to remove 61 char length requirement, allowing for longer branch names to be specified for preview aliases.#10289
a5a1426Thanks @emily-shen! - Cleanup container images created during local dev if no changes have been made.We now untag old images that were created by Wrangler/Vite if we find that the image content and configuration is unchanged, so that we don't keep accumulating image tags.
#10315
0c04da9Thanks @emily-shen! - Addrollout_active_grace_periodoption to containers configuration.This allows users to configure how long an active container should keep running for during a rollout, before the upgrade is applied.
#10321
b524a6fThanks @emily-shen! - print prettier errors during container deployment#10253
eb32a3aThanks @emily-shen! - fix redeploying container apps when previous deploy failed or container (but not image) was deleted.Previously this failed with
No changes detected but no previous image foundas we assumed there would be a previous deployment when an image exists in the registry.#9990
4288a61Thanks @penalosa! - Fix startup profiling when sourcemaps are enabledUpdated dependencies [
d54d8b7,ae0c806]:v4.29.1Compare Source
Patch Changes
5020694]:v4.29.0Compare Source
Minor Changes
#10283
80960b9Thanks @WillTaylorDev! - Support long branch names in generation of branch aliases in WCI.#10312
bd8223dThanks @devin-ai-integration! - Added--domainflag towrangler deploycommand for deploying to custom domains. Use--domain example.comto deploy directly to a custom domain without manually configuring routes.#8318
8cf47f9Thanks @gnekich! - Introduce json output flag for wrangler pages deployment listPatch Changes
#10232
e7cae16Thanks @emily-shen! - fix: validatewrangler containers delete IDto ensure a valid ID has been provided. Previously if you provided the container name (or any non-ID shaped string) you would get an auth error instead of a 404.#10139
3b6ab8aThanks @dom96! - Removes mention of cf-requirements when Python Workers are enabled#10259
c58a05cThanks @dario-piotrowicz! - Ensure thatmaybeStartOrUpdateRemoteProxySessionconsiders the potential account_id from the user's wrangler configCurrently if the user has an
account_idin their wrangler config file, such id won't be taken into consideration for the remote proxy session, the changes here make sure that it is (note that theauthoption ofmaybeStartOrUpdateRemoteProxySession, if provided, takes precedence over this id value).The changes here also fix the same issue for
wrangler devandgetPlatformProxy(since they usemaybeStartOrUpdateRemoteProxySessionunder the hook).#10288
42aafa3Thanks @tgarg-cf! - Do not attempt to update queue producer settings when deploying a Worker with a queue bindingPreviously, each deployed Worker would update a subset of the queue producer's settings for each queue binding, which could result in broken queue producers or at least conflicts where different Workers tried to set different producer settings on a shared queue.
#10242
70bd966Thanks @devin-ai-integration! - Add experimental API to expose Wrangler command tree structure for documentation generation#10258
d391076Thanks @nikitassharma! - Add the option to allow all tiers when creating a container#10248
422ae22Thanks @emily-shen! - fix: re-push container images on deploy even if the only change was to the Dockerfile#10179
5d5ecd5Thanks @pombosilva! - Prevent defining multiple workflows with the same "name" property in the same wrangler file#10232
e7cae16Thanks @emily-shen! - include containers API calls in output of WRANGLER_LOG=debug#10243
d481901Thanks @devin-ai-integration! - Remove async_hooks polyfill - now uses native workerd implementationThe async_hooks module is now provided natively by workerd, making the polyfill unnecessary. This improves performance and ensures better compatibility with Node.js async_hooks APIs.
#10060
9aad334Thanks @edmundhung! - refactor: switchgetPlatformProxy()to use Miniflare's dev registry implementationUpdated
getPlatformProxy()to use Miniflare's dev registry instead of Wrangler's implementation. Previously, you had to start a wrangler or vite dev session before accessing the proxy bindings to connect to those workers. Now the order doesn't matter.#10219
28494f4Thanks @dario-piotrowicz! - fixNonRetryableErrorthrown with an empty error message not stopping workflow retries locallyUpdated dependencies [
1479fd0,05c5b28,e3d9703,d481901]:Configuration
📅 Schedule: Branch creation - "on Monday" (UTC), 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.