chore(deps): update all non-major dependencies #42
+881
−627
Conversation
This file contains hidden or 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}
✅ Deployed chat-template
|
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
901b764 to
ed38e0a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
ed38e0a to
f756113
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
f756113 to
3f7326d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
2 times, most recently
from
514721b to
044e080
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
044e080 to
0d4dade
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
0d4dade to
84c90a6
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
84c90a6 to
db911b8
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
db911b8 to
de84f8d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
de84f8d to
988d3a5
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
988d3a5 to
4178a04
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
4178a04 to
93d0d71
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
93d0d71 to
3aaeab7
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
3aaeab7 to
cb1c02b
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
cb1c02b to
48ed14c
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
48ed14c to
1ac54de
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
1ac54de to
109e07d
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
109e07d to
bac4b1a
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
bac4b1a to
dbac201
Compare
renovate
bot
force-pushed
the
renovate/all-minor-patch
branch
from
dbac201 to
981799b
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:
^1.2.4->^1.2.5^1.2.57->^1.2.61^1.2.43->^1.2.46^1.5.2->^1.8.0^3.2.0->^3.3.0^0.17.1->^0.17.2^22.16.4->^22.17.0^0.44.3->^0.44.4^9.31.0->^9.32.0^0.5.20->^0.5.2310.13.1->10.14.0^5.8.3->^5.9.2^3.0.1->^3.0.5^4.24.4->^4.28.1Release Notes
nuxt/eslint (@nuxt/eslint)
v1.8.0Compare Source
🚀 Features
View changes on GitHub
v1.7.1Compare Source
🐞 Bug Fixes
eslint-typegen.d.tsinnuxt.node.d.ts, close #596 - by @antfu in https://github.com/nuxt/eslint/issues/596 (ab74e)View changes on GitHub
v1.7.0Compare Source
🚀 Features
View changes on GitHub
v1.6.0Compare Source
🐞 Bug Fixes
eslint-plugin-import-xas default, close #590 - by @antfu in https://github.com/nuxt/eslint/issues/590 (e43d6)View changes on GitHub
nuxt/ui-pro (@nuxt/ui-pro)
v3.3.0Compare Source
drizzle-team/drizzle-orm (drizzle-orm)
v0.44.4Compare Source
eslint/eslint (eslint)
v9.32.0Compare Source
atinux/nuxt-auth-utils (nuxt-auth-utils)
v0.5.23Compare Source
compare changes
🚀 Enhancements
stateparam (#423)🩹 Fixes
🏡 Chore
❤️ Contributors
v0.5.22Compare Source
compare changes
🚀 Enhancements
🩹 Fixes
📖 Documentation
🏡 Chore
❤️ Contributors
v0.5.21Compare Source
compare changes
🩹 Fixes
📖 Documentation
🏡 Chore
❤️ Contributors
pnpm/pnpm (pnpm)
v10.14.0Compare Source
Minor Changes
Added support for JavaScript runtime resolution
Declare Node.js, Deno, or Bun in
devEngines.runtime(insidepackage.json) and let pnpm download and pin it automatically.Usage example:
{ "devEngines": { "runtime": { "name": "node", "version": "^24.4.0", "onFail": "download" (we only support the "download" value for now) } } }How it works:
pnpm installresolves your specified range to the latest matching runtime version.Why this is better:
useNodeVersionandexecutionEnv.nodeVersion)executionEnv.nodeVersion). So, different projects in a workspace can use different runtimes.devEngines.runtimesetting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.Related PR: #9755.
Add
--cpu,--libc, and--ostopnpm install,pnpm add, andpnpm dlxto customizesupportedArchitecturesvia the CLI #7510.Patch Changes
pnpm adddownloads packages whoselibcdiffer frompnpm.supportedArchitectures.libc.dlxto parse CLI flags and options between thedlxcommand and the command to run or between thedlxcommand and--#9719.pnpm install --prodshould removing hoisted dev dependencies #9782.pnpm installto incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.microsoft/TypeScript (typescript)
v5.9.2Compare Source
vuejs/language-tools (vue-tsc)
v3.0.5Compare Source
Features
compileSFCStyleto provide style related infomation (#5548) - Thanks to @KazariEX!v-for(#5553) - Thanks to @KazariEX!Bug Fixes
modelModifiersfor explicitly declared default model name (#5558) - Thanks to @KazariEX!.valueinsertionclassscope fallback forcomponentsemantic tokens (#5559) - Thanks to @KazariEX!globalTypesPathfor FS filesrestartExtensionHostOther Changes
v3.0.4Compare Source
Features
Bug Fixes
skipTemplateCodegenwhen exposing$slots- Thanks to @KazariEX!Other Changes
checkUnknownEventsandcheckUnknownComponentsin sfc (#5537) - Thanks to @KazariEX!v3.0.3Compare Source
Bug Fixes
node_modulesbased on file's directory (#5525) - Thanks to @KazariEX!Other Changes
v3.0.2Compare Source
Features
globalTypesPathoption for non-npm like environment (#5505) - Thanks to @KazariEX!Bug Fixes
/or)- Thanks to @KazariEX!colorizedBracketPairsconfig for plaintext<component>withoutisprop as normal component - Thanks to @KazariEX!@vue/typescript-pluginlast (#5483)namevalue of<slot>- Thanks to @KazariEX!allowJsto reactivity analyze host - Thanks to @KazariEX!mdfor markdown (#5497) - Thanks to @KazariEX!modulefrom template completion - Thanks to @KazariEX!Other Changes
minimatchtopicomatch(#5499) - Thanks to @KazariEX!.d.${ext}.tsfile exists (volarjs/volar.js#277)cloudflare/workers-sdk (wrangler)
v4.28.1Compare Source
Patch Changes
#10130
773cca3Thanks @dario-piotrowicz! - updatemaybeStartOrUpdateRemoteProxySessionconfig argument (to allow callers to specify an environment)Before this change
maybeStartOrUpdateRemoteProxySessioncould be called with either the path to a wrangler config file or the configuration of a worker. The former override however did not allow the caller to specify an environment, so themaybeStartOrUpdateRemoteProxySessionAPI has been updated so that in the wrangler config case an object (with the path and a potential environment) needs to be passed instead.For example, before callers could invoke the function in the following way
note that there is no way to tell the function what environment to use when parsing the wrangle configuration.
Now callers will instead call the function in the following way:
note that now a target environment can be specified.
#10130
773cca3Thanks @dario-piotrowicz! - fixgetPlatformProxynot taking into account the potentially specified environment for remote bindings#10122
2e8eb24Thanks @dario-piotrowicz! - fixstartWorkernot respectingauthoptions for remote bindingsfix
startWorkercurrently not taking into account theauthfieldthat can be provided as part of the
devoptions when used in conjunctionwith remote bindings
example:
Given the following
wranglerwill now use the provided<ACCOUNT_ID>and<API_TOKEN>to integrate withthe remote AI binding instead of requiring the user to authenticate.
#10209
93c4c26Thanks @devin-ai-integration! - fix: strip ANSI escape codes from log files to improve readability and parsing#9774
48853a6Thanks @nikitassharma! - Validate container configuration against account limits in wrangler to give early feedback to the user#10122
2e8eb24Thanks @dario-piotrowicz! - fix incorrect TypeScript type for AI binding in thestartWorkerAPIv4.28.0Compare Source
Minor Changes
e82aa19Thanks @Akshit222! - Add --json flag to r2 bucket info command for machine-readable output.Patch Changes
#10004
b4d1373Thanks @dario-piotrowicz! - fixwrangler devlogs being logged on the incorrect level in some casescurrently the way
wrangler devprints logs is faulty, for example the following codeinside a worker would cause the following logs:
(note that the warning is printed as an error and the debug log is printed even if by default it should not)
the changes here make sure that the logs are instead logged to their correct level, so for the code about the following will be logged instead:
(running
wrangler devwith the--log-level=debugflag will also cause the debug log to be included as well)#10099
360004dThanks @emily-shen! - fix: move local dev container cleanup to process exit hook. This should ensure containers are cleaned up even when Wrangler is shut down programatically.#10186
dae1377Thanks @matthewdavidrodgers! - Deleting when Pages project binds to worker requires confirmation#10169
1655becThanks @devin-ai-integration! - fix: report startup errors before workerd profiling#10136
354a001Thanks @nikitassharma! - Updatewrangler containers images listto make fewer API calls to improve command runtime#10157
5c3b83fThanks @devin-ai-integration! - Enforce 64-character limit for Workflow binding names locally to match production validation#10154
502a8e0Thanks @devin-ai-integration! - Fix UTF BOM handling in config files - remove UTF-8 BOM and error on other BOMs#10176
07c8611Thanks @devin-ai-integration! - Add macOS version validation to prevent EPIPE errors on unsupported macOS versions (below 13.5). Miniflare and C3 fail hard while Wrangler shows warnings but continues execution.Updated dependencies [
6b9cd5b,631f26d,d6ecd05,b4d1373,8ba7736,07c8611,7e204a9,3f83ac1]:v4.27.0Compare Source
Minor Changes
#9914
a24c9d8Thanks @petebacondarwin! - Add support for loading local dev vars from .env filesIf there are no
.dev.varsor.dev.vars.<environment>files, when running Wrangler or the Vite plugin in local development mode,they will now try to load additional local dev vars from
.env,.env.local,.env.<environment>and.env.<environment>.localfiles.These loaded vars are only for local development and have no effect in production to the vars in a deployed Worker.
Wrangler and Vite will continue to load
.envfiles in order to configure themselves as a tool.Further details:
vite buildthe local vars will be computed and stored in a.dev.varsfile next to the compiled Worker code, so thatvite previewcan use them.wrangler typescommand will similarly read the.envfiles (if no.dev.varsfiles) in order to generate theEnvinterface.CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENVenvironment variable is"false"then local dev variables will not be loaded from.envfiles.CLOUDFLARE_INCLUDE_PROCESS_ENVenvironment variable is"true"then all the environment variables found onprocess.envwill be included as local dev vars.--env-file=<path/to/dotenv/file>global CLI option. This affects both loading.envto configure Wrangler the tool as well as loading local dev vars.Patch Changes
#10051
0f7820eThanks @nikitassharma! - Add support for custom instance limits for containers. For example, instead ofhaving to use the preconfigured dev/standard/basic instance types, you can now
set:
This feature is currently only available to customers on an enterprise plan.
#10149
e9bb8d3Thanks @vicb! - fixrequire("debug")in nodejs_compat modeUpdated dependencies [
9b61f44]:v4.26.1Compare Source
Patch Changes
#10061
f8a80a8Thanks @emily-shen! - feat(containers): try to automatically get the socket path that the container engine is listening on.Currently, if your container engine isn't set up to listen on
unix:///var/run/docker.sock(or isn't symlinked to that), then you have to manually set this via thedev.containerEnginefield in your Wrangler config, or via the env varsWRANGLER_DOCKER_HOST. This change means that we will try and get the socket of the current context automatically. This should reduce the occurrence of opaqueinternal errors thrown by the runtime when the daemon is not listening onunix:///var/run/docker.sock.In addition to
WRANGLER_DOCKER_HOST,DOCKER_HOSTcan now also be used to set the container engine socket address.#10048
dbdbb8cThanks @vicb! - pass the compatibility date and flags to the unenv preset#10096
687655fThanks @vicb! - bump unenv to 2.0.0-rc.19#9897
755a249Thanks @edmundhung! - fix: wrangler types should infer the types of the default worker entrypointUpdated dependencies [
82a5b2e,f8f7352,2df1d06,dbdbb8c,5991a9c,687655f]:v4.26.0Compare Source
Minor Changes
#10016
c5b291dThanks @emily-shen! - Interactively handlewrangler deploys that are probably assets-only, where there is no config file and flags are incorrect or missing.For example:
npx wrangler deploy ./publicwill now ask if you meant to deploy a folder of assets only, ask for a name, set the compat date and then ask whether to write your choices out towrangler.jsonfor subsequent deployments.npx wrangler deploy --assets=./publicwill now ask for a name, set the compat date and then ask whether to write your choices out towrangler.jsonfor subsequent deployments.In non-interactive contexts, Wrangler will error as it currently does.
#9971
19794bfThanks @edmundhung! - Improved script source display on the pretty error screenPatch Changes
#9800
3d4f946Thanks @helloimalastair! - remove banner from r2 getobject in pipe mode#9910
7245101Thanks @dario-piotrowicz! - make sure that the ready-on message is printed after the appropriate runtime controller is readyfix the fact that when starting a local (or remote) dev session the log saying
Ready on http://localhost:xxxxcould be displayed before the runtime is actually ready to handle requests (this is quite noticeable when locally running dev sessions with containers, where the ready message currently gets displayed before the container images building/pulling process)#10031
823cba8Thanks @vicb! - wrangler and vite-plugin now depend upon the latest version of unenv-preset#10032
154acf7Thanks @dario-piotrowicz! - add support for containers in wrangler multiworker devcurrently when running
wrangler devwith different workers (meaning that the-c|--configflag is used multiple times) containers are not being included, meaning that trying to interact with them at runtime would not work and cause errors instead. The changes here address the above making wrangler correctly detect and wire up the containers.#9988
7fb0bfdThanks @penalosa! - Correctly labelmtlsremote bindings warningUpdated dependencies [
823cba8,19794bf,059a39e]:v4.25.1Compare Source
Patch Changes
#10000
c02b067Thanks @emily-shen! - Include more (sanitised) user errors in telemetry.We manually vet and sanitised error messages before including them in our telemetry collection - this PR just includes a couple more.
#9996
b0217f9Thanks @nikitassharma! - Disallow users from pushing images with unsupported platforms to the container image registry#10009
e87198aThanks @gpanders! - Fix containers diff output when using JSONC config files#9976
ad02ad3Thanks @dario-piotrowicz! - add warning for when users runwrangler dev --remotewith (enabled) containers#9819
0c4008cThanks @CarmenPopoviciu! - feat(vite-plugin): Add containers support invite devAdds support for Cloudflare Containers in
vite dev. Please note that at the time of this PR a container image can only specify the path to aDockerfile. Support for registry links will be added in a later version, as will containers support invite preview.Updated dependencies [
189fe23,7e5585d]:v4.25.0Compare Source
Minor Changes
9f0c175Thanks @thomasgauvin! - Added rename namespace command to Workers KVPatch Changes
6cc24c0Thanks @emily-shen! - Add more thorough validation to containers configurationConfiguration
📅 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.