Skip to content

fix(deps): update external fixes#236

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate-external-fixes
Open

fix(deps): update external fixes#236
renovate[bot] wants to merge 1 commit intomainfrom
renovate-external-fixes

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jan 19, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@aws-sdk/s3-request-presigner (source) 3.958.03.997.0 age confidence
@cloudflare/workers-types 4.20260101.04.20260304.0 age confidence
@redocly/cli 2.14.22.19.2 age confidence
dotenv 17.2.317.3.1 age confidence
semantic-release 25.0.225.0.3 age confidence
wrangler (source) 4.54.04.68.1 age confidence

Release Notes

aws/aws-sdk-js-v3 (@​aws-sdk/s3-request-presigner)

v3.997.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.996.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.995.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.994.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.993.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.992.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.991.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.990.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.989.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.988.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.987.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.986.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.985.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.984.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.983.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.982.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.981.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.980.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.978.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.975.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.974.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.972.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.971.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.970.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.969.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.968.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.967.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.966.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.965.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.964.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

v3.962.0

Compare Source

Note: Version bump only for package @​aws-sdk/s3-request-presigner

cloudflare/workerd (@​cloudflare/workers-types)

v4.20260304.0

Compare Source

v4.20260303.0

Compare Source

v4.20260302.0

Compare Source

v4.20260301.1

Compare Source

v4.20260228.1

Compare Source

v4.20260228.0

Compare Source

v4.20260227.0

Compare Source

v4.20260226.1

Compare Source

v4.20260219.0

Compare Source

v4.20260218.0

Compare Source

v4.20260217.0

Compare Source

v4.20260214.0

Compare Source

v4.20260213.0

Compare Source

v4.20260212.0

Compare Source

v4.20260210.0

Compare Source

v4.20260207.0

Compare Source

v4.20260206.0

Compare Source

v4.20260205.0

Compare Source

v4.20260203.0

Compare Source

v4.20260131.0

Compare Source

v4.20260130.0

Compare Source

v4.20260129.0

Compare Source

v4.20260128.0

Compare Source

v4.20260127.0

Compare Source

v4.20260124.0

Compare Source

v4.20260123.0

Compare Source

v4.20260122.0

Compare Source

v4.20260120.0

Compare Source

v4.20260118.0

Compare Source

v4.20260117.0

Compare Source

v4.20260116.0

Compare Source

v4.20260115.0

Compare Source

v4.20260114.0

Compare Source

v4.20260113.0

Compare Source

v4.20260111.0

Compare Source

v4.20260109.0

Compare Source

v4.20260108.0

Compare Source

v4.20260107.1

Compare Source

v4.20260103.0

Compare Source

Redocly/redocly-cli (@​redocly/cli)

v2.19.2

Compare Source

Patch Changes
  • Fixed an issue where scorecardClassic configurations were not resolved.

v2.19.1

Compare Source

Patch Changes

v2.19.0

Compare Source

Minor Changes
  • Added the spec-querystring-parameters rule (OpenAPI 3.2).
    This rule enforces that query and querystring are not mixed in the same operation/path parameter set, and that at most one querystring parameter is declared per operation or path.
Patch Changes
  • Fixed an issue where running CLI commands would result in "ReferenceError: React is not defined" message.
  • Updated @​redocly/respect-core to v2.19.0.

v2.18.2

Compare Source

Patch Changes
  • Fixed false positive errors in example validation for OpenAPI 3.0.x and OpenAPI 2.x.
  • Updated @​redocly/openapi-core to v2.18.2.

v2.18.1

Compare Source

Patch Changes
  • Fixed validation of examples where combining required with readOnly or writeOnly properties would incorrectly generate warnings.
  • Updated @​redocly/respect-core to v2.18.1.

v2.18.0

Compare Source

Minor Changes
  • Added lintEntityWithScorecardLevel function to validate entity files against scorecard level configurations and lintSchema function to lint individual schemas from API description files.
Patch Changes

v2.17.0

Compare Source

Minor Changes
  • Added support for Media Types in the Components model.
  • Added new outputs-defined Arazzo rule, ensuring outputs are defined before use.

v2.16.0

Compare Source

Minor Changes
  • Added a new --component-renaming-conflicts-severity option for the bundle command to control how naming conflicts are reported when bundling API descriptions with external references.
Patch Changes
  • Redirected bundling problems (such as lint errors and warnings) to stderr instead of stdout to avoid interfering with the bundled output.

v2.15.2

Compare Source

Patch Changes
  • Fixed an issue where improperly structured OpenAPI examples caused the linter to fail.

v2.15.1

Compare Source

Patch Changes
  • Updated @​redocly/config to v0.41.4.
  • Added description and documentationLink properties to NodeTypes.
    Renamed Redocly configuration types to better reflect their purpose and relations.
  • Updated @​redocly/config to v0.41.3.

v2.15.0

Compare Source

Patch Changes

v2.14.9

Compare Source

Patch Changes

v2.14.8

Compare Source

Patch Changes
  • Fixed an issue where multi-line lint error messages could break Markdown formatting.
  • Updated @​redocly/openapi-core to v2.14.8.

v2.14.7

Compare Source

Patch Changes

v2.14.6

Compare Source

Patch Changes

v2.14.5

Compare Source

Patch Changes
  • Added an ajv npm alias dependency to satisfy peer dependency requirements and prevent installation warnings.
  • Updated @​redocly/openapi-core to v2.14.5.

v2.14.4

Compare Source

Patch Changes
  • Corrected an issue where Respect did not properly JSON-encode request bodies for custom content-types containing numbers.
  • Updated @​redocly/respect-core to v2.14.4.

v2.14.3

Compare Source

Patch Changes
  • Fixed the split command 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.
  • Updated @​redocly/openapi-core to v2.14.3.
motdotla/dotenv (dotenv)

v17.3.1

Compare Source

Changed
  • Fix as2 example command in README and update spanish README

v17.3.0

Compare Source

Added
  • Add a new README section on dotenv’s approach to the agentic future.
Changed
  • Rewrite README to get humans started more quickly with less noise while simultaneously making more accessible for llms and agents to go deeper into details.

v17.2.4

Compare Source

Changed
  • Make DotenvPopulateInput accept NodeJS.ProcessEnv type (#​915)
  • Give back to dotenv by checking out my newest project vestauth. It is auth for agents. Thank you for using my software.
semantic-release/semantic-release (semantic-release)

v25.0.3

Compare Source

Bug Fixes
cloudflare/workers-sdk (wrangler)

v4.68.1

Compare Source

Patch Changes
  • #​12648 3d6e421 Thanks @​petebacondarwin! - Fix Angular scaffolding to allow localhost SSR in development mode

    Recent versions of Angular's AngularAppEngine block serving SSR on localhost by default. This caused wrangler dev / wrangler pages dev to fail with URL with hostname "localhost" is not allowed.

    The fix passes allowedHosts: ["localhost"] to the AngularAppEngine constructor in server.ts, which is safe to do even in production since Cloudflare will already restrict which host is allowed.

  • #​12657 294297e Thanks @​dario-piotrowicz! - Update Waku autoconfig logic

    As 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 []:

    • miniflare@​4.20260302.0

v4.68.0

Compare Source

Minor Changes

v4.67.1

Compare Source

Patch Changes
  • #​12595 e93dc01 Thanks @​dario-piotrowicz! - Add a warning in the autoconfig logic letting users know that support for projects inside workspaces is limited

  • #​12582 c2ed7c2 Thanks @​penalosa! - Internal refactor to use capnweb's native ReadableStream support to power remote Media and Dispatch Namespace bindings.

  • #​12618 d920811 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260219.0 1.20260227.0
  • #​12637 896734d Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260227.0 1.20260302.0
  • #​12601 ebdbe52 Thanks @​43081j! - Switch to empathic for file-system upwards traversal to reduce dependency bloat.

  • #​12602 58a4020 Thanks @​anonrig! - Optimize filesystem operations by using Node.js's throwIfNoEntry: false option

    This 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 6f6cd94 Thanks @​martinezjandrew! - Implemented logic within wrangler containers registries configure to check if a specified secret name is already in-use and offer to reuse that secret. Also added --skip-confirmation flag to the command to skip all interactive prompts.

  • Updated dependencies [c2ed7c2, d920811, 896734d, 58a4020]:

    • miniflare@​4.20260302.0

v4.67.0

Compare Source

Minor Changes
  • #​12401 8723684 Thanks @​jonesphillip! - Add validation retry loops to pipelines setup command

    The wrangler pipelines setup command now prompts users to retry when validation errors occur, instead of failing the entire setup process. This includes:

    • Validation retry prompts for pipeline names, bucket names, and field names
    • A "simple" mode for sink configuration that uses sensible defaults
    • Automatic bucket creation when buckets don't exist
    • Automatic Data Catalog enablement when not already active

    This improves the setup experience by allowing users to correct mistakes without restarting the entire configuration flow.

  • #​12395 aa82c2b Thanks @​cmackenzie1! - Generate typed pipeline bindings from stream schemas

    When 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.

    // wrangler.json
    {
    	"pipelines": [
    		{ "binding": "ANALYTICS", "pipeline": "analytics-stream-id" },
    	],
    }

    If your stream has a schema with fields like user_id (string) and event_count (int32), the generated types will be:

    declare namespace Cloudflare {
    	type AnalyticsStreamRecord = { user_id: string; event_count: number };
    	interface Env {
    		ANALYTICS: Pipeline<Cloudflare.AnalyticsStreamRecord>;
    	}
    }

    For unstructured streams or when not authenticated, bindings fall back to the generic Pipeline<PipelineRecord> type.

Patch Changes
  • #​12592 aaa7200 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260217.0 1.20260218.0
  • #​12606 2f19a40 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260218.0 1.20260219.0
  • #​12604 e2a6600 Thanks @​petebacondarwin! - fix: pass --env flag to auxiliary workers in multi-worker mode

    When running wrangler dev with multiple config files (e.g. -c ./apps/api/wrangler.jsonc -c ./apps/queues/wrangler.jsonc -e=dev), the --env flag 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 0b17117 Thanks @​sdnts! - The maximum allowed delivery and retry delays for Queues is now 24 hours

  • #​12598 ca58062 Thanks @​mattzcarey! - Stop redacting wrangler whoami output in non-interactive mode

    wrangler whoami is 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.0

Compare Source

Minor Changes
  • #​12466 caf9b11 Thanks @​petebacondarwin! - Add WRANGLER_CACHE_DIR environment variable and smart cache directory detection

    Wrangler now intelligently detects where to store cache files:

    1. Use WRANGLER_CACHE_DIR env var if set
    2. Use existing cache directory if found (node_modules/.cache/wrangler or .wrangler/cache)
    3. Create cache in node_modules/.cache/wrangler if node_modules exists
    4. Otherwise use .wrangler/cache

    This improves compatibility with Yarn PnP, pnpm, and other package managers that don't use traditional node_modules directories, without requiring any configuration.

  • #​12572 936187d Thanks @​dario-piotrowicz! - Ensure the nodejs_compat flag is always applied in autoconfig

    Previously, the autoconfig feature relied on individual framework configurations to specify Node.js compatibility flags, some could set nodejs_compat while others nodejs_als.

    Now instead nodejs_compat is always included as a compatibility flag, this is generally beneficial and the user can always remove the flag afterwards if they want to.

  • #​12560 c4c86f8 Thanks @​taylorlee! - Support --tag and --message flags on wrangler deploy

    They have the same behavior that they do as during wrangler versions upload, as both
    are 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 5a868a0 Thanks @​G4brym! - Fix AI Search binding failing in local dev

    Using AI Search bindings with wrangler dev would fail with "RPC stub points at a non-serializable type". AI Search bindings now work correctly in local development.

  • #​12552 c58e81b Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260212.0 1.20260213.0
  • #​12568 33a9a8f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260213.0 1.20260214.0
  • #​12576 8077c14 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    workerd 1.20260214.0 1.20260217.0
  • #​12466 caf9b11 Thanks @​petebacondarwin! - fix: exclude .wrangler directory from Pages uploads

    The .wrangler directory contains local cache and state files that should never be deployed. This aligns Pages upload behavior with Workers Assets, which already excludes .wrangler via .assetsignore.

  • #​12556 7d2355e Thanks @​ascorbic! - Fix port availability check probing the wrong host when host changes

    memoizeGetPort correctly 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 7ea69af Thanks @​MattieTK! - Support function-based Vite configs in autoconfig setup

    wrangler setup and wrangler deploy --x-autoconfig can now automatically add the Cloudflare Vite plugin to projects that use function-based defineConfig() patterns. Previously, autoconfig would fail with "Cannot modify Vite config: expected an object literal but found ArrowFunctionExpression" for configs like:

    export default defineConfig(({ isSsrBuild }) => ({
    	plugins: [reactRouter(), tsconfigPaths()],
    }));

    This pattern is used by several official framework templates, including React Router's node-postgres and node-custom-server templates. The following defineConfig() 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 5cc7158 Thanks @​dario-piotrowicz! - Fix .assetsignore formatting when autoconfig creates a new file

    Previously, when wrangler setup or wrangler deploy --x-autoconfig created a new .assetsignore file via autoconfig, it would add unnecessary leading empty lines before the wrangler-s


Configuration

📅 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 is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@codecov
Copy link

codecov bot commented Jan 19, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@renovate renovate bot force-pushed the renovate-external-fixes branch 12 times, most recently from 9568b6f to f6ef130 Compare January 27, 2026 02:55
@renovate renovate bot force-pushed the renovate-external-fixes branch 14 times, most recently from 7b9968a to 4d33e8c Compare February 3, 2026 02:52
@renovate renovate bot force-pushed the renovate-external-fixes branch 3 times, most recently from 6b8b9bb to 9bb759d Compare February 5, 2026 02:43
@renovate renovate bot force-pushed the renovate-external-fixes branch 13 times, most recently from 472f104 to 46c8e73 Compare February 18, 2026 22:56
@renovate renovate bot force-pushed the renovate-external-fixes branch 15 times, most recently from 7eff884 to 1c06c0d Compare February 25, 2026 20:45
@renovate renovate bot force-pushed the renovate-external-fixes branch from 1c06c0d to 7afaaa7 Compare February 26, 2026 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants