Repository navigation
Maintenance: Update dependency wrangler to ^4.118.0 - #228
Merged
Merged
Conversation
| datasource | package | from | to | | ---------- | -------- | ------- | ------- | | npm | wrangler | 4.116.0 | 4.118.0 |
|
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.116.0→^4.118.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.118.0Compare Source
Minor Changes
#14057
cc63aaeThanks @matingathani! - Add--jsonflag towrangler containers infofor consistent JSON output with sibling commandslistandinstances#14944
a249591Thanks @nickpatt! - Enable local observability capture by default in devwrangler devand the Vite plugin now capture request traces and console logs into the Local Explorer's Observability tab out of the box — previously this was opt-in behindX_LOCAL_OBSERVABILITY=true. SetX_LOCAL_OBSERVABILITY=falseto opt out (for example if the extra per-worker collector/streaming-tail services cause trouble in a multi-process dev-registry setup).#14919
e0bbf55Thanks @avenceslau! - Add additional triggers to WorkflowsWorkers can now declaratively start a locally defined Workflow. Configure event subscriptions under
triggers.events; Wrangler validates each target and updates the script's event triggers during deployment.{ "triggers": { "events": [ { "type": "cf.artifacts.repo.pushed", "filter": { "namespace": "my-namespace", "repo_name": "my-repo" }, "targets": [ { "type": "workflow", "workflow_name": "my-workflow" } ] } ] } }Patch Changes
#14936
f92d1fcThanks @petebacondarwin! - Fixjsx_fragmentbeing ignored whenwrangler devruns a custom buildIf your project uses a custom build and sets both
jsx_factoryandjsx_fragment,wrangler devused yourjsx_factoryvalue for JSX fragments as well, so fragments compiled incorrectly. Yourjsx_fragmentvalue is now used.#14936
f92d1fcThanks @petebacondarwin! - Stopwrangler devstarting new work after you stop it or it reloadsStopping
wrangler dev, or having it reload after a configuration change, could still leave it starting work for the state it had just left behind: your custom build command could run once more after dev had stopped, a change to a file in your assets directory could be reported against configuration that had already been replaced, and in some cases the process could stay alive instead of exiting.That work is now discarded, so stopping or reloading
wrangler devleaves nothing running behind it.#14936
f92d1fcThanks @petebacondarwin! - Stopwrangler devfrom running custom builds concurrentlyWhen several watched files changed at once — for example during a
git pullor a "save all" —wrangler devstarted a custom build for every file that changed, so multiple copies of your build command ran at the same time and fought over the same output files.A burst of file changes now results in a single build, and a build only starts once the previous one has finished.
#13746
cec9d88Thanks @edmundhung! - Report a clear error for account IDs that can't be used in a Cloudflare API requestAccount IDs are substituted straight into Cloudflare API URL paths, so a value containing non-ASCII characters previously failed deep inside the request layer with an opaque
Cannot convert argument to a ByteStringerror that gave no hint about which setting was at fault. Account IDs read fromCLOUDFLARE_ACCOUNT_IDand from theaccount_idconfiguration field are now validated up front, and an invalid value fails with a message naming both the offending value and where it came from.v4.117.0Compare Source
Minor Changes
#14586
5a56ddaThanks @emily-shen! - RemovecontainerEnginefrom the worker options returned byunstable_getMiniflareWorkerOptionsunstable_getMiniflareWorkerOptionsno longer includescontainerEnginein the returnedworkerOptions, since the container engine is a Miniflare instance-wide setting rather than a per-worker one. Callers that build a Miniflare instance from these options should setcontainerEngineat the top level instead.Patch Changes
#14586
5a56ddaThanks @emily-shen! - Rewrite local testing paths (/cdn-cgi/*)Miniflare v5 moved its internal local testing endpoints to
/cdn-cgi/local/*(and/__cf_local/*for endpoints that must remain reachable over tunnels) to prevent any potential collision with production routes.wrangler devand the Vite plugin now transparently rewrite the old paths to the new ones, meaning you can continue to use the old paths without issue.These are the new paths:
/cdn-cgi/handler/scheduled→/cdn-cgi/local/scheduled/cdn-cgi/handler/email→/cdn-cgi/local/email/cdn-cgi/explorer/*→/cdn-cgi/local/explorer/*/cdn-cgi/mf/scheduled→/cdn-cgi/local/scheduled(Note/cdn-cgi/mf/scheduledis already deprecated)/cdn-cgi/mf/stream/*→/__cf_local/stream/*/cdn-cgi/mf/imagedelivery/*→/__cf_local/imagedelivery/*Updated dependencies [
5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda,5a56dda]:Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.