Open
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
9568b6f to
f6ef130
Compare
7b9968a to
4d33e8c
Compare
6b8b9bb to
9bb759d
Compare
472f104 to
46c8e73
Compare
7eff884 to
1c06c0d
Compare
1c06c0d to
7afaaa7
Compare
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:
3.958.0→3.997.04.20260101.0→4.20260304.02.14.2→2.19.217.2.3→17.3.125.0.2→25.0.34.54.0→4.68.1Release Notes
aws/aws-sdk-js-v3 (@aws-sdk/s3-request-presigner)
v3.997.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.996.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.995.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.994.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.993.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.992.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.991.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.990.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.989.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.988.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.987.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.986.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.985.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.984.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.983.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.982.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.981.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.980.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.978.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.975.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.974.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.972.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.971.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.970.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.969.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.968.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.967.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.966.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.965.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.964.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
v3.962.0Compare Source
Note: Version bump only for package @aws-sdk/s3-request-presigner
cloudflare/workerd (@cloudflare/workers-types)
v4.20260304.0Compare Source
v4.20260303.0Compare Source
v4.20260302.0Compare Source
v4.20260301.1Compare Source
v4.20260228.1Compare Source
v4.20260228.0Compare Source
v4.20260227.0Compare Source
v4.20260226.1Compare Source
v4.20260219.0Compare Source
v4.20260218.0Compare Source
v4.20260217.0Compare Source
v4.20260214.0Compare Source
v4.20260213.0Compare Source
v4.20260212.0Compare Source
v4.20260210.0Compare Source
v4.20260207.0Compare Source
v4.20260206.0Compare Source
v4.20260205.0Compare Source
v4.20260203.0Compare Source
v4.20260131.0Compare Source
v4.20260130.0Compare Source
v4.20260129.0Compare Source
v4.20260128.0Compare Source
v4.20260127.0Compare Source
v4.20260124.0Compare Source
v4.20260123.0Compare Source
v4.20260122.0Compare Source
v4.20260120.0Compare Source
v4.20260118.0Compare Source
v4.20260117.0Compare Source
v4.20260116.0Compare Source
v4.20260115.0Compare Source
v4.20260114.0Compare Source
v4.20260113.0Compare Source
v4.20260111.0Compare Source
v4.20260109.0Compare Source
v4.20260108.0Compare Source
v4.20260107.1Compare Source
v4.20260103.0Compare Source
Redocly/redocly-cli (@redocly/cli)
v2.19.2Compare Source
Patch Changes
scorecardClassicconfigurations were not resolved.v2.19.1Compare Source
Patch Changes
v2.19.0Compare Source
Minor Changes
spec-querystring-parametersrule (OpenAPI 3.2).This rule enforces that
queryandquerystringare not mixed in the same operation/path parameter set, and that at most onequerystringparameter is declared per operation or path.Patch Changes
v2.18.2Compare Source
Patch Changes
v2.18.1Compare Source
Patch Changes
requiredwithreadOnlyorwriteOnlyproperties would incorrectly generate warnings.v2.18.0Compare Source
Minor Changes
lintEntityWithScorecardLevelfunction to validate entity files against scorecard level configurations andlintSchemafunction to lint individual schemas from API description files.Patch Changes
v2.17.0Compare Source
Minor Changes
outputs-definedArazzo rule, ensuring outputs are defined before use.v2.16.0Compare Source
Minor Changes
--component-renaming-conflicts-severityoption for thebundlecommand to control how naming conflicts are reported when bundling API descriptions with external references.Patch Changes
stderrinstead ofstdoutto avoid interfering with the bundled output.v2.15.2Compare Source
Patch Changes
v2.15.1Compare Source
Patch Changes
descriptionanddocumentationLinkproperties to NodeTypes.Renamed Redocly configuration types to better reflect their purpose and relations.
v2.15.0Compare Source
Patch Changes
chokidardependency.v2.14.9Compare Source
Patch Changes
v2.14.8Compare Source
Patch Changes
v2.14.7Compare Source
Patch Changes
v2.14.6Compare Source
Patch Changes
v2.14.5Compare Source
Patch Changes
ajvnpm alias dependency to satisfy peer dependency requirements and prevent installation warnings.v2.14.4Compare Source
Patch Changes
Respectdid not properly JSON-encode request bodies for custom content-types containing numbers.v2.14.3Compare Source
Patch Changes
splitcommand to properly handle root-level paths.Previously, the root path
/was converted to an empty string as a filename, leading to incorrect file structure and broken links.Now, it correctly maps to the specified path separator.
motdotla/dotenv (dotenv)
v17.3.1Compare Source
Changed
v17.3.0Compare Source
Added
Changed
v17.2.4Compare Source
Changed
DotenvPopulateInputacceptNodeJS.ProcessEnvtype (#915)semantic-release/semantic-release (semantic-release)
v25.0.3Compare Source
Bug Fixes
cloudflare/workers-sdk (wrangler)
v4.68.1Compare Source
Patch Changes
#12648
3d6e421Thanks @petebacondarwin! - Fix Angular scaffolding to allow localhost SSR in development modeRecent versions of Angular's
AngularAppEngineblock serving SSR onlocalhostby default. This causedwrangler dev/wrangler pages devto fail withURL with hostname "localhost" is not allowed.The fix passes
allowedHosts: ["localhost"]to theAngularAppEngineconstructor inserver.ts, which is safe to do even in production since Cloudflare will already restrict which host is allowed.#12657
294297eThanks @dario-piotrowicz! - Update Waku autoconfig logicAs of
1.0.0-alpha.4, Waku projects can be built on top of the Cloudflare Vite plugin, and the changes here allow Wrangler autoconfig to support this. Running autoconfig on older versions of Waku will result in an error.Updated dependencies []:
v4.68.0Compare Source
Minor Changes
#12614
8d882faThanks @dario-piotrowicz! - Enable autoconfig forwrangler deployby default (while allowing users to still disable it via--x-autoconfig=falseif necessary)#12614
8d882faThanks @dario-piotrowicz! - Mark thewrangler setupcommand as stablev4.67.1Compare Source
Patch Changes
#12595
e93dc01Thanks @dario-piotrowicz! - Add a warning in the autoconfig logic letting users know that support for projects inside workspaces is limited#12582
c2ed7c2Thanks @penalosa! - Internal refactor to use capnweb's nativeReadableStreamsupport to power remote Media and Dispatch Namespace bindings.#12618
d920811Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12637
896734dThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12601
ebdbe52Thanks @43081j! - Switch toempathicfor file-system upwards traversal to reduce dependency bloat.#12602
58a4020Thanks @anonrig! - Optimize filesystem operations by using Node.js's throwIfNoEntry: false optionThis reduces the number of system calls made when checking for file existence by avoiding the overhead of throwing and catching errors for missing paths. This is an internal performance optimization with no user-visible behavioral changes.
#12591
6f6cd94Thanks @martinezjandrew! - Implemented logic withinwrangler containers registries configureto check if a specified secret name is already in-use and offer to reuse that secret. Also added--skip-confirmationflag to the command to skip all interactive prompts.Updated dependencies [
c2ed7c2,d920811,896734d,58a4020]:v4.67.0Compare Source
Minor Changes
#12401
8723684Thanks @jonesphillip! - Add validation retry loops to pipelines setup commandThe
wrangler pipelines setupcommand now prompts users to retry when validation errors occur, instead of failing the entire setup process. This includes:This improves the setup experience by allowing users to correct mistakes without restarting the entire configuration flow.
#12395
aa82c2bThanks @cmackenzie1! - Generate typed pipeline bindings from stream schemasWhen running
wrangler types, pipeline bindings now generate TypeScript types based on the stream's schema definition. This gives you full autocomplete and type checking when sending data to your pipelines.If your stream has a schema with fields like
user_id(string) andevent_count(int32), the generated types will be:For unstructured streams or when not authenticated, bindings fall back to the generic
Pipeline<PipelineRecord>type.Patch Changes
#12592
aaa7200Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12606
2f19a40Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12604
e2a6600Thanks @petebacondarwin! - fix: pass--envflag to auxiliary workers in multi-worker modeWhen running
wrangler devwith multiple config files (e.g.-c ./apps/api/wrangler.jsonc -c ./apps/queues/wrangler.jsonc -e=dev), the--envflag was not being passed to auxiliary (non-primary) workers. This meant that environment-specific configuration (such as queue bindings) was not applied to auxiliary workers, causing features like queue consumers to not be triggered in local development.#12597
0b17117Thanks @sdnts! - The maximum allowed delivery and retry delays for Queues is now 24 hours#12598
ca58062Thanks @mattzcarey! - Stop redactingwrangler whoamioutput in non-interactive modewrangler whoamiis explicitly invoked to retrieve account info, so email and account names should always be visible. Redacting them in non-interactive/CI environments makes it difficult for coding agents and automated tools to identify which account to use. Other error messages that may appear unexpectedly in CI logs (e.g. multi-account selection errors) remain redacted.Updated dependencies [
f239077,aaa7200,2f19a40,5f9f0b4,452cdc8,527e4f5,0b17117]:v4.66.0Compare Source
Minor Changes
#12466
caf9b11Thanks @petebacondarwin! - AddWRANGLER_CACHE_DIRenvironment variable and smart cache directory detectionWrangler now intelligently detects where to store cache files:
WRANGLER_CACHE_DIRenv var if setnode_modules/.cache/wrangleror.wrangler/cache)node_modules/.cache/wranglerifnode_modulesexists.wrangler/cacheThis improves compatibility with Yarn PnP, pnpm, and other package managers that don't use traditional
node_modulesdirectories, without requiring any configuration.#12572
936187dThanks @dario-piotrowicz! - Ensure thenodejs_compatflag is always applied in autoconfigPreviously, the autoconfig feature relied on individual framework configurations to specify Node.js compatibility flags, some could set
nodejs_compatwhile othersnodejs_als.Now instead
nodejs_compatis always included as a compatibility flag, this is generally beneficial and the user can always remove the flag afterwards if they want to.#12560
c4c86f8Thanks @taylorlee! - Support--tagand--messageflags onwrangler deployThey have the same behavior that they do as during
wrangler versions upload, as bothare set on the version.
The message is also reused for the deployment as well, with the same behavior as used
during
wrangler versions deploy.Patch Changes
#12543
5a868a0Thanks @G4brym! - Fix AI Search binding failing in local devUsing AI Search bindings with
wrangler devwould fail with "RPC stub points at a non-serializable type". AI Search bindings now work correctly in local development.#12552
c58e81bThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12568
33a9a8fThanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12576
8077c14Thanks @dependabot! - Update dependencies of "miniflare", "wrangler"The following dependency versions have been updated:
#12466
caf9b11Thanks @petebacondarwin! - fix: exclude.wranglerdirectory from Pages uploadsThe
.wranglerdirectory contains local cache and state files that should never be deployed. This aligns Pages upload behavior with Workers Assets, which already excludes.wranglervia.assetsignore.#12556
7d2355eThanks @ascorbic! - Fix port availability check probing the wrong host when host changesmemoizeGetPortcorrectly invalidated its cached port when called with a different host, but then still probed the original host for port availability. This could return a port that was free on the original host but already in use on the requested one, leading to bind failures at startup.#12562
7ea69afThanks @MattieTK! - Support function-based Vite configs in autoconfig setupwrangler setupandwrangler deploy --x-autoconfigcan now automatically add the Cloudflare Vite plugin to projects that use function-baseddefineConfig()patterns. Previously, autoconfig would fail with "Cannot modify Vite config: expected an object literal but found ArrowFunctionExpression" for configs like:This pattern is used by several official framework templates, including React Router's
node-postgresandnode-custom-servertemplates. The followingdefineConfig()patterns are now supported:defineConfig({ ... })(object literal, already worked)defineConfig(() => ({ ... }))(arrow function with expression body)defineConfig(({ isSsrBuild }) => ({ ... }))(arrow function with destructured params)defineConfig(() => { return { ... }; })(arrow function with block body)defineConfig(function() { return { ... }; })(function expression)#12548
5cc7158Thanks @dario-piotrowicz! - Fix.assetsignoreformatting when autoconfig creates a new filePreviously, when
wrangler setuporwrangler deploy --x-autoconfigcreated a new.assetsignorefile via autoconfig, it would add unnecessary leading empty lines before the wrangler-specConfiguration
📅 Schedule: Branch creation - "after 2pm on Monday" in timezone Europe/Zurich, 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.