chore(deps): update all non-major dependencies#156
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Deploying unsight with
|
| Latest commit: |
ff4607a
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://81de3380.unsight.pages.dev |
| Branch Preview URL: | https://renovate-all-minor-patch.unsight.pages.dev |
danielroe
approved these changes
May 26, 2025
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
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:
4.13.1->4.13.21.4.0->1.4.14.15.2->4.16.1Release Notes
antfu/eslint-config (@antfu/eslint-config)
v4.13.2Compare Source
No significant changes
View changes on GitHub
nuxt/eslint (@nuxt/eslint)
v1.4.1Compare Source
🐞 Bug Fixes
node:prefix to build-in modules - by @danielroe in https://github.com/nuxt/eslint/issues/579 (8180f)View changes on GitHub
cloudflare/workers-sdk (wrangler)
v4.16.1Compare Source
Patch Changes
7344344Thanks @gabivlj! -wrangler containers deletehandles API errors correctlyv4.16.0Compare Source
Minor Changes
#9288
3b8f7f1Thanks @petebacondarwin! - allow --name and --env args on wrangler deployPreviously it was not possible to provide a Worker name as a command line argument at the same time as setting the Wrangler environment.
Now specifying
--nameis supported and will override any names set in the Wrangler config:wrangler.json
{ "name": "config-worker" "env": { "staging": { "name": "config-worker-env" } } }#9265
16de0d5Thanks @edmundhung! - docs: add documentation links to individual config properties in the JSON schema of the Wrangler config filePatch Changes
#9234
2fe6219Thanks @emily-shen! - fix: add no-oppropstoctxingetPlatformProxyto fix type mismatch#9269
66d975eThanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for multi-workerwrangler devUnder the
--x-mixed-modeflag, make sure that bindings configurations withremote: trueactually generate bindings to remote resources during a multi-workerwrangler devsession, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.Also include the ai binding since the bindings is already remote by default anyways.
#9151
5ab035dThanks @gabivlj! - wrangler containers can be configured with the kind of application rollout onapply#9231
02d40edThanks @dario-piotrowicz! - Wire up mixed-mode remote bindings for (single-worker)wrangler devUnder the
--x-mixed-modeflag, make sure that bindings configurations withremote: trueactually generate bindings to remote resources during a single-workerwrangler devsession, currently the bindings included in this are: services, kv_namespaces, r2_buckets, d1_databases, queues and workflows.Also include the ai binding since the bindings is already remote by default anyways.
#9221
2ef31a9Thanks @vicb! - bump@cloudflare/unenv-preset#9277
db5ea8fThanks @penalosa! - Support Mixed Mode for more binding types#9266
f2a16f1Thanks @petebacondarwin! - fix: setting triggers.crons:[] in Wrangler config should delete deployed cron schedules#9245
b87b472Thanks @penalosa! - Support Mixed Mode Dispatch NamespacesUpdated dependencies [
db5ea8f,b87b472]: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.