Update dependency wrangler to v4.34.0 - autoclosed #472
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
changed the title
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.28.1->4.34.0Release Notes
cloudflare/workers-sdk (wrangler)
v4.34.0Compare Source
Minor Changes
#10478
cc47b51Thanks @danielrs! - Beta feature preview_urls is now disabled by default.This change makes preview_urls disabled by default when it's not provided, making
the feature opt-in instead of opt-out.
Patch Changes
#10489
6e8dd80Thanks @WalshyDev! - Allow Wrangler to upload 100,000 assets inline with the newly increased Workers Paid limit.#10517
7211609Thanks @edmundhung! - fix:wrangler vectorize list-vectors --jsonnow output valid json without an extra log line#10527
818ce22Thanks @vicb! - Bumpunenvto 2.0.0-rc.20The latest release include a fix for
node:ttydefault export.See the changelog for full details.
#10519
5d69df4Thanks @dario-piotrowicz! - Slightly improvewrangler init --from-dasherror message#10519
5d69df4Thanks @dario-piotrowicz! - Internally refactor diffing andwrangler init --from-dashlogic#10533
c22acc6Thanks @emily-shen! - If unset, containers.max_instances should default to 1 instead of 0.#10503
c0fad5fThanks @ichernetsky-cf! - Support setting container affinities#10515
c6a39f5Thanks @emily-shen! - fix: script should be accepted as a positional arg in theversions uploadcommandUpdated dependencies [
4cb3370,818ce22,cb22f5f,a565291]:v4.33.2Compare Source
Patch Changes
#10401
3c15bbbThanks @dario-piotrowicz! - improve diff lines ordering in remote deploy config diffing logic#10520
dc81221Thanks @emily-shen! - fix: wrangler deploy dry run should not require you to be logged inFixes a bug where if you had a container where the image was an image registry link, dry run would require you to be logged in.
Also fixes a bug where container deployments were not respecting
account_idset in Wrangler config.#10393
4492eb0Thanks @dario-piotrowicz! - Use resolved local config for remote deploy config diffing logicUpdated dependencies [
31ecfeb,f656d1a,22c8ae6,bd21fc5,38bdb78,4851955]:v4.33.1Compare Source
Patch Changes
#10427
85be2b6Thanks @dario-piotrowicz! - Simplify ENOENT debug logs for.envfilesUpdated dependencies [
76d9aa2,452ad0b,7c339ae]:v4.33.0Compare Source
Minor Changes
e81c2cfThanks @penalosa! - Support automatically updating the user's config file with newly created resourcesPatch Changes
#10424
c4fd176Thanks @penalosa! - Remove the--experimental-json-config/-jflag, which is no longer required.#10432
19e2aabThanks @anonrig! - Remove "node:tls" polyfill#10424
c4fd176Thanks @penalosa! - Expose global flags fromexperimental_getWranglerCommands()Updated dependencies [
19e2aab]:v4.32.0Compare Source
Minor Changes
#10354
da40571Thanks @edmundhung! - Enable cross-process communication forwrangler devwith multiple config filesWorkers running in separate
wrangler devsessions can now communicate with each other regardless of whether you are running with single or multiple config files.Check out the Developing with multiple Workers guide to learn more about the different approaches and when to use each one.
#10012
4728c68Thanks @penalosa! - Support unsafe dynamic worker loading bindingsPatch Changes
#10245
d304055Thanks @edmundhung! - Migrate wrangler dev to use Miniflare dev registry implementationUpdated
wrangler devto use a shared dev registry implementation that now powers both the Cloudflare Vite plugin and Wrangler. This internal refactoring has no user-facing changes but consolidates registry logic for better consistency across tools.#10407
f534c0dThanks @emily-shen! - defaultcontainers.rollout_active_grace_periodto 0#10425
0a96e69Thanks @dario-piotrowicz! - Fix debugging logs not including headers for CF API requests and responsesFix the fact that
wrangler, when run with theWRANGLER_LOG=DEBUGandWRANGLER_LOG_SANITIZE=falseenvironment variables, displays{}instead of the actual headers for requests and responses for CF API fetches#10337
f9f7519Thanks @emily-shen! - containers:rollout_step_percentagenow also accepts an array of numbers. Previously it accepted a single number, and each rollout step would target the same percentage of instances. Now users can customise percentages for each step.rollout_step_percentagealso now defaults to[10,100](previously25), which should make rollouts progress slightly faster.You can also use
wrangler deploy --containers-rollout=immediateto override rollout settings in Wrangler configuration and update all instances in one step. Note this doesn't overriderollout_active_grace_periodif configured.Updated dependencies [
4728c68]: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 - Between 12:00 AM and 03:59 AM ( * 0-3 * * * ) (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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.