Skip to content

chore(deps): update external dev fixes - #317

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate-external-dev-fixes
Open

chore(deps): update external dev fixes#317
renovate[bot] wants to merge 1 commit into
mainfrom
renovate-external-dev-fixes

Conversation

@renovate

@renovate renovate Bot commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@redocly/cli 2.44.1 → 2.51.2 age confidence
js-yaml 5.2.3 → 5.4.1 age confidence
lint-staged 17.3.0 → 17.5.0 age confidence
wrangler (source) 4.119.0 → 4.129.1 age confidence

Release Notes

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

v2.51.2

Compare Source

Patch Changes
  • Updated fast-uri to the 3.1.7 version to resolve CVE-2026-75931, CVE-2026-75975, CVE-2026-75899, and CVE-2026-76172.
  • Fixed drift and coverage failing to match a path template whose segment mixes literal text with parameters, such as /instances/{worldId}:{instanceId}.
  • Fixed an issue where Redocly config resolution failed when plugins used ESM syntax.
  • Updated @​redocly/openapi-core to v2.51.2.

v2.51.1

Compare Source

Patch Changes
  • Fixed an issue where generate-arazzo produced a malformed remote description URL in sourceDescriptions (https:// collapsed to https:/) when --output-file was provided.
  • Fixed an issue where $faker.string.email() used without options generated addresses at the undefined.com domain.
  • Updated @​redocly/respect-core to v2.51.1.
  • Updated @faker-js/faker to the 10.6.0 version to resolve the high severity advisory GHSA-qxc2-j82w-r537.

v2.51.0

Compare Source

Minor Changes
  • Enhanced the generate-arazzo command to print a ready-to-run respect command after generation, including an --input placeholder for every workflow input.
  • Added --with-ai, --ai-provider, --ai-model, --ai-concurrency, and --max-workflows options to the generate-arazzo command.
    --with-ai uses a local AI CLI (claude, codex, or cursor) and OpenAPI descriptions to redesign the generated one-workflow-per-operation skeleton into multi-step workflows.
    The AI designs at most --max-workflows workflows (default 10), and the generated file is marked as AI-inferred.
    For descriptions that don't fit a single prompt, the AI first selects scenarios from a compact operation index, then it designs each workflow separately.
Patch Changes
  • Fixed an issue where respect and the x-security-scheme-required-values rule incorrectly rejected x-security HTTP schemes written with non-lowercase casing (such as Basic, Bearer, or Digest).
    RFC 7235 scheme names are case-insensitive.
  • Updated @​redocly/openapi-core to v2.51.0.
  • Updated @​redocly/respect-core to v2.51.0.

v2.50.0

Compare Source

Minor Changes
  • Added a new schema assertion for configurable rules.
    The assertion validates a property value against a JSON Schema.
Patch Changes

v2.49.1

Compare Source

Patch Changes
  • Fixed an issue where rule incorrectly reported a duplicate parameter when two or more $refs pointed to the same path item.
  • Updated @​redocly/openapi-core to v2.49.1.

v2.49.0

Compare Source

Minor Changes

  • Added the no-illogical-composition-keywords rule.

    Note: the rule is set to warn in the recommended ruleset and to error in recommended-strict. Existing API descriptions may report new problems.

Patch Changes
  • Fixed an issue where telemetry silently failed to send when npm was not available.
  • Updated @​redocly/openapi-core to v2.49.0.

v2.48.0

Compare Source

Minor Changes
  • Added agent-friendly client generation: python, go, php, and cli generators beside the TypeScript client, each self-documenting with --docs, configurable per generator, and available as source in your own repository through eject-generator.
Patch Changes
  • Fixed an issue where the bundle command didn't resolve $refs inside an AsyncAPI 3 Multi Format Schema Object.
  • Fixed an issue where respect --har-output recorded an empty postData for every request.
    Request bodies are written to the HAR.
    Captures replayed through drift can have their request bodies validated instead of silently passing.
  • Updated @​redocly/client-generator to v0.4.0.
  • Updated @​redocly/openapi-core to v2.48.0.

v2.47.0

Compare Source

Minor Changes
  • Added a Vendor Extensions metric to the stats command that reports how many distinct x- extensions a description file uses and how often each one occurs.
Patch Changes
  • Fixed the stats command reporting wrong parameter count for AsyncAPI descriptions.
  • Updated @​redocly/openapi-core to v2.47.0.

v2.46.2

Compare Source

Patch Changes

v2.46.1

Compare Source

Patch Changes

v2.46.0

Compare Source

Minor Changes
  • Added the spec-ref-siblings rule that reports properties placed next to a $ref which the specification does not allow.
Patch Changes

v2.45.0

Compare Source

Minor Changes
  • Fixed the bundle command losing schema keywords (such as title, properties, or required) written next to a $ref when the referenced schemas started with their own $ref.
Patch Changes

v2.44.2

Compare Source

Patch Changes
  • Changed the severity of the security-defined rule for AsyncAPI 2.x and 3.x in the recommended ruleset from error to warn.
    AsyncAPI descriptions with undefined or unresolved security no longer fail linting by default.
  • Updated @​redocly/openapi-core to v2.44.2.
nodeca/js-yaml (js-yaml)

v5.4.1

Compare Source

v5.4.0

Compare Source

Added
  • Added the scalarStyleRules dumper option to customize string formatting.
    See Scalar styling for details.
Changed
  • [breaking] Flattened the low-level AST node style representation. Scalar
    and collection nodes now use SCALAR_STYLE and COLLECTION_STYLE values;
    explicit tags use the separate tagged property. Alias nodes now contain
    only kind and anchor. This only affects code that directly constructs or
    edits AST nodes.
  • [breaking] The sortKeys option was rewritten using AST mutation to avoid
    side effects.
  • Reworked scalar style selection. This can change formatting without changing
    loaded values; in particular, whitespace-only strings are now double-quoted.
Fixed
  • Accept a byte order mark at the start of each document in a stream, #​791.
  • Produce valid flow mappings with quoteFlowKeys and flowSkipColonSpace,
    including alias and property-only keys, #​786.
  • Preserve empty scalar items when converting block sequences to flow style.
  • Do not apply the 1024-character simple-key limit to flow mapping keys.
  • Count Unicode code points, rather than UTF-16 code units, for the
    1024-character simple-key limit.
  • Add an explicit document-end marker after keep-chomped block scalars when
    needed to preserve trailing newlines.

v5.3.0

Compare Source

This release focuses on reworking the documentation and making small
architectural improvements before moving forward.

Added
  • Added completely new documentation.
  • Exported DUMP_SCHEMA, the default schema used by the dumper.
  • Added YAMLException.throwAt() for throwing an error at a source position.
Changed
  • Changed flat constant exports to grouped exports: EVENT_ID, SCALAR_STYLE,
    COLLECTION_STYLE, and CHOMPING_MODE, along with their value types. The old
    exports are still preserved, but deprecated.
  • Made identify mandatory for custom tag definitions. Use
    identify: () => false for load-only tags.
Deprecated
  • Deprecated flat constant exports. Use grouped ones instead.
Removed
  • Removed the MERGE_KEY export (not used anymore after last fixes).
Fixed
  • Validate << sequence items at merge time, so aliased merge sources are
    checked too.
  • Resolve << outside of a mapping key as the plain string '<<', matching
    v4, instead of leaking an internal symbol into the result.
lint-staged/lint-staged (lint-staged)

v17.5.0

Compare Source

Minor Changes
  • #​1847 f9063b7 - Lint-staged now refuses to run when files were staged with --intent-to-add, because Git stash doesn't support them. Previously this was an unhandled error.
Patch Changes

  • #​1848 d718ccc - Lint-staged now handles color support better in non-TTY streams, and honors the FORCE_COLOR environment variable.

  • #​1845 7e5ece8 - Update tinyexec@1.3.1 so that local binaries from node_modules/.bin are resolved starting from the directory of each lint-staged configuration file (in monorepo setups). This behavior was broken in lint-staged@16.3.0 where they were only resolved from the current working directory and up.

  • #​1845 eb8a4e3 - Do not try to restore untracked files when using --hide-all and there is no initial commit yet.

v17.4.1

Compare Source

Patch Changes
  • #​1840 efe5b63 - This is a version-bump-only release because the previous version 17.4.0 was not published to npmjs.com due to problems with GitHub Actions and Changesets.
cloudflare/workers-sdk (wrangler)

v4.129.1

Compare Source

Patch Changes

  • #​15502 8bbcb9f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260903.1 ^5.20260904.1
    workerd 1.20260903.1 1.20260904.1

  • #​15543 2b42d6f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260904.1 ^5.20260907.1
    workerd 1.20260904.1 1.20260907.1

  • #​15323 ea5634e Thanks @​Sakshamm-Goyal! - Prevent Wrangler from exiting when a process capturing its output closes the pipe.

    Wrangler now ignores broken-pipe errors from stdout and stderr while preserving the existing failure behavior for other output errors.

  • #​14001 c0c6504 Thanks @​for-the-kidz! - Update bundle size warning thresholds to use uncompressed size instead of gzip size

    The compressed script size limits (3 MiB free / 10 MiB paid) have been removed server-side in favor of a single 64 MiB uncompressed limit. The bundle size reporter now compares the uncompressed bundle size against this 64 MiB limit for its color-coded warnings, instead of comparing gzip size against the old 3 MiB compressed limit.

  • #​15499 ffc7efd Thanks @​WillTaylorDev! - Honor Workers Builds name overrides in wrangler preview

    Preview commands now target the Worker name supplied by Workers Builds instead of the name in local Wrangler configuration. This prevents preview builds from failing when the two names differ.

  • #​15252 682cd44 Thanks @​GregoryCollett! - wrangler dev no longer exits when a request to your Worker fails transiently

    Previously, a transient network failure on a single request — most commonly a request arriving just as an idle internal connection was closed, after roughly five seconds without traffic — could take down the whole dev server with an empty ✘ [ERROR], leaving the port unbound until restarted. In CI test suites, one such failure caused every remaining test to fail with connection errors.

    wrangler dev now automatically retries the affected request if it is safe to repeat (GET and HEAD requests). If a request still fails, it fails individually — the error is logged with the request method and URL — and the dev server keeps serving.

  • Updated dependencies [8bbcb9f, 2b42d6f]:

v4.129.0

Compare Source

Minor Changes

  • #​15460 93d72a5 Thanks @​QnJ1c2kNCg! - Support gzip compression for JSON Pipelines sinks

    Pipelines is in open beta. wrangler pipelines sinks create and the interactive setup flow now pass the selected JSON compression to the Pipelines API. JSON sinks accept uncompressed or gzip, while Parquet retains its existing compression options and zstd default.

  • #​15358 d2d8eea Thanks @​pombosilva! - Add a --json flag to the wrangler workflows commands

    Every wrangler workflows command now accepts --json, which emits the raw API payload instead of the human-readable rendering. The formatted output remains the default, so existing usage is unaffected:

    wrangler workflows instances list my-workflow --json

    The JSON output carries raw values rather than a serialisation of the formatted view: ISO timestamps instead of locale-formatted dates, plain status strings instead of emojified labels, and no presentation-only derived fields.

Patch Changes

  • #​15469 d40a634 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260831.1 ^5.20260902.1
    workerd 1.20260831.1 1.20260902.1

  • #​15481 7c1b2a6 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260902.1 ^5.20260903.1
    workerd 1.20260902.1 1.20260903.1

  • #​15472 f6fb347 Thanks @​emily-shen! - Tolerate missing permissions during wrangler delete cleanup checks

    wrangler delete now warns and continues when it cannot inspect Worker dependencies or clean up legacy Workers Sites KV namespaces because of missing permissions. The Worker delete request itself still fails normally if the token cannot delete the Worker.

  • #​15472 f6fb347 Thanks @​emily-shen! - Tolerate missing resource permissions during resource provisioning

    When Wrangler cannot check whether a bound resource exists because the API returns a 403, it now skips automatic provisioning for that resource type and continues the deploy. The deploy may still fail later if the resource is missing.

  • #​15476 dc24057 Thanks @​christhorwarth! - Fix remote development with static assets for API tokens using granular Worker permissions

    Wrangler now creates Workers.dev preview sessions through the Worker-scoped endpoint and derives the preview hostname from the session response. This avoids requiring account-level Workers subdomain access.

  • Updated dependencies [00a9f2f, 1dba24a, d40a634, 7c1b2a6]:

v4.128.0

Compare Source

Minor Changes

  • #​15454 dbbb795 Thanks @​jamesopstad! - Move binding utilities into @cloudflare/workers-utils

    Binding conversion, printing, and local-development validation are now exported from @cloudflare/workers-utils so they can be shared by Wrangler, the Cloudflare Vite plugin, and other consumers.

    The corresponding exports have been removed from @cloudflare/deploy-helpers. Consumers should import them directly from @cloudflare/workers-utils instead.

    Wrangler's unstable_printBindings API now accepts the bindings and an options object instead of five positional parameters.

  • #​15353 87a7acf Thanks @​pombosilva! - Add --date-start and --date-end filters to wrangler workflows instances list

    You can now narrow an instance listing to a creation-time window:

    wrangler workflows instances list my-workflow --date-start 2026-01-01 --date-end 2026-01-31

    Either flag can be used independently. Both accept an ISO 8601 date or timestamp and are normalised to UTC before being sent, so a date-only value such as 2026-01-01 works as well as a full 2026-01-01T13:00:00Z. The bounds are inclusive and compose with the existing --status filter.

  • #​15379 ea28cc3 Thanks @​ibbykhazanchi! - Add query string redaction to Workers observability configuration

    Set observability.redact_query_string in wrangler.json or observability.redactQueryString in the experimental cloudflare.config.ts format to remove query strings from request URLs in logs and traces.

  • #​14915 707cb6f Thanks @​longlho! - Include exact raw and gzip-compressed Worker bundle sizes in structured deploy and version-upload output.

Patch Changes

  • #​15436 200780f Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260828.1 ^5.20260831.1
    workerd 1.20260828.1 1.20260831.1

  • #​15406 b3f2628 Thanks @​james-elicx! - Reduce the installed bundle sizes of Wrangler and Miniflare

    Wrangler now resolves bundled workspace dependencies from source during monorepo builds so unused exports can be removed. Miniflare, its shared CLI and container dependencies now use granular @cloudflare/workers-utils entry points instead of loading the package barrel, reducing the raw Wrangler and Miniflare artifacts by 6.16 MiB (31.4%) and 1.06 MiB (22.9%) respectively without changing runtime behavior or installed dependencies.

  • #​15398 1809c5e Thanks @​james-elicx! - Reduce Wrangler's published package size

    Stop including the unused build metafile in the npm package, reducing its unpacked size by approximately 3.1 MiB.

  • #​15382 b3fb2bf Thanks @​Om-singhaI! - Skip the skills install status lookup when telemetry is disabled

    Telemetry events include a currentAgentSkillsInstalled property, and computing it can query the GitHub API. The lookup used to start before the telemetry permission was checked, so users who opted out via WRANGLER_SEND_METRICS, DO_NOT_TRACK, or send_metrics in their Wrangler config still triggered network requests on behalf of telemetry. The dispatcher now checks the permission first and only performs the lookup when telemetry is enabled.

  • Updated dependencies [200780f, b3f2628, 87a7acf]:

v4.127.1

Compare Source

Patch Changes

v4.127.0

Compare Source

Minor Changes

  • #​15356 fe265f8 Thanks @​rubuy-74! - Add support for configuring a per-workflow max concurrency limit via workflows[].concurrency.limit in your Wrangler config.

    The limit is the maximum number of Workflow instances that can run concurrently. It is validated as a positive integer and persisted on deploy; the ceiling is enforced server-side. Concurrency is ignored in local development.

    {
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "concurrency": { "limit": 10 }
    }
  ]
}
Patch Changes

  • #​15367 412c79e Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20260825.1 ^5.20260826.1
    workerd 1.20260825.1 1.20260826.1

  • #​15375 92874f6 Thanks @​WillTaylorDev! - Upload wrangler preview modules as multipart form data

    wrangler preview used to base64 the bundle, its modules, and any sourcemaps into a single JSON request body. Base64 inflates content by a third, so a Worker with a large sourcemap could exceed the API request size limit and fail to deploy.

    The preview deployment request is now multipart/form-data. The deployment settings travel in a metadata part and each module follows as its own part carrying raw bytes, matching how wrangler deploy already uploads a Worker.

  • Updated dependencies [412c79e]:

v4.126.0

Compare Source

Minor Changes

  • #​15332 d1cc3af Thanks @​pombosilva! - Add default_retention to Workflow bindings for configuring how long instances are retained

    Workflow instances are retained for an account-wide default period after they finish. You can now set a per-Workflow default in your Wrangler configuration, applied to instances that do not specify their own retention:

    {
  "workflows": [
    {
      "binding": "MY_WORKFLOW",
      "name": "my-workflow",
      "class_name": "MyWorkflow",
      "default_retention": {
        "success_retention": "3 days",
        "error_retention": "7 days"
      }
    }
  ]
}

    Each side is optional and accepts either a duration string such as "3 days" or a whole number of milliseconds. Durations are interpreted by the Workflows API, which also caps them at your account's retention limit.

  • #​15064 693ca29 Thanks @​tpmmorris! - Include a chronological list of handler events in email test harness results, so programmatic local email tests can assert the order in which messages are received, forwarded, replied to, or rejected.

    const result = await server.getWorker().email({
  from: "sender@example.com",
  to: "inbox@example.com",
  raw: [
    "From: Sender <sender@example.com>",
    "To: Inbox <inbox@example.com>",
    "Message-ID: <test@example.com>",
    "Subject: Test email",
    "",
    "Hello from the test harness",
  ].join("\r\n"),
});

expect(result.events).toEqual([
  { type: "received", timestamp: expect.any(String) },
  {
    type: "forward",
    timestamp: expect.any(String),
    messageId: expect.any(String),
  },
  {
    type: "reply",
    timestamp: expect.any(String),
    messageId: expect.any(String),
  },
]);

  • #​15065 ad89456 Thanks @​mtlemilio! - Add experimental wrangler hyperdrive planetscale signature for provisioning Cloudflare-billed PlanetScale databases

    wrangler hyperdrive planetscale signature prints a signed authorization as JSON, proving to PlanetScale that Cloudflare will be billed for the database you are about to create:

    npx wrangler hyperdrive planetscale signature | \
  pscale database create <name> \
    --org <org> \
    --engine postgresql \
    --cloudflare-billing @- \
    --format json

    pscale database create defaults to Vitess, so pass --engine postgresql for a Postgres database, and --format json is recommended when the output is consumed by an agent.

    This requires pscale v0.313.0 or newer. Wrangler authorizes the Cloudflare billing side only, so your PlanetScale credentials stay between you and pscale.

    The signature is a cryptographically signed token that authorizes creating a database billed to your Cloudflare account. Treat it as a credential and do not share it. Piping it, as above, is recommended over passing it as a command line argument.

    This command is experimental and its interface may change.

  • #​15134 c66d2d5 Thanks @​gpanders! - Enable FUSE-capable local container development

    Miniflare now automatically passes the Docker privileges needed for FUSE to local Durable Object containers when using local rootless Docker on Linux with /dev/fuse available, or a local Docker engine on macOS or through WSL where Linux containers run in a VM. This applies to Wrangler, the Cloudflare Vite plugin, and direct Miniflare use.

  • #​15326 9fcb1c9 Thanks @​jamesopstad! - Record the selected mode in the Build Output Specification top-level config.json

    The mode a build was produced in is now written to .cloudflare/output/v0/config.json as a mode field, alongside the account and compliance settings.

  • #​14966 a4c3458 Thanks @​yomna-shousha! - Add pull request metadata to wrangler preview deployments

    wrangler preview now detects the pull request associated with the current CI run (GitHub Actions, GitLab CI, CircleCI, and a generic PULL_REQUEST_URL/PR_URL/CHANGE_URL fallback) and attaches it, along with the repository URL, to the preview deployment as annotations (workers/pull_request_number, workers/pull_request_url, workers/repository_url).

    This is best effort: if no pull request can be detected, nothing changes. When a pull request is detected, its URL is now also shown in the wrangler preview command output.

  • #​15307 433fa98 Thanks @​for-the-kidz! - Add pull request title to wrangler preview deployment annotations

    wrangler preview now also detects the title of the pull/merge request associated with the current CI run (GitHub Actions and GitLab CI, plus a generic PULL_REQUEST_TITLE fallback) and attaches it to the preview deployment as the workers/pull_request_title annotation, alongside the existing pull request number/URL, repository URL, and commit SHA annotations.

    This is best effort: if no pull request title can be detected, nothing changes.

Patch Changes

v4.125.0

Compare Source

Minor Changes

  • #​14995 59872c4 Thanks @​ThomasRubini! - Add connect trigger for raw sockets

    You can now configure a Worker to receive raw socket connections during wrangler dev, delivered directly to the Worker's connect(socket, env, ctx) handler:

    {
  "connect": [{ "protocol": "tcp", "port": 5432 }]
}

    Each entry opens a listening socket on 127.0.0.1 (or the given address) that forwards incoming connections straight to the Worker, bypassing the local dev HTTP entry point. This requires the experimental compatibility flag. Only "tcp" is supported at the moment.

    @cloudflare/config also supports declaring this trigger via triggers.connect(...), which lowers to the connect field above:

    import { defineWorker, triggers } from "@cloudflare/config";

export default defineWorker({
  triggers: [
    triggers.connect({ protocol: "tcp", port: 5432, address: "127.0.0.1" }),
  ],
});

  • #​15172 c68f9cb Thanks @​WillTaylorDev! - Add container support to worker previews

    Worker previews now support containers through a new previews.containers configuration block. Container configuration doesn't inherit, so declare containers explicitly in the previews block to enable them for previews. This mirrors how previews.durable_objects works today. Wrangler names each preview container application {worker_name}_{preview_slug}_{class_name}, normalising and shortening the result to what the API accepts. Either change appends a short digest of the composed name, so two names that would otherwise land on one stay distinct. An entry cannot set its own name, because application names are unique to an account and a fixed name would collide between two previews of the same Worker. A Durable Object class is backed by at most one container application, so the validator rejects two entries that share a class_name. Wrangler skips container applications bound to Durable Object classes that another Worker implements through script_name, because the implementing Worker owns its own container application. A binding is not required: a Durable Object declared through migrations or exports and reached only over ctx.exports can still back a container. Every entry must set class_name. A previews.containers entry whose class_name matches no Durable Object class at all is rejected before the preview deployment is created, so a typo fails loudly instead of producing a preview with no container.

    Wrangler creates the container applications on wrangler preview. Deleting a preview tears them down server side, so wrangler preview delete doesn't remove them.

    Container build and deploy progress prints to stdout. wrangler preview --json suppresses wrangler's own output so it doesn't interleave with the payload, and warnings and errors still go to stderr. Docker's build output and the progress spinner write to stdout directly and bypass that suppression, so parse --json from a non interactive shell, where the spinner is skipped, and prefer a prebuilt image over a Dockerfile.

  • #​15174 649f667 Thanks @​WillTaylorDev! - [private beta]: Create the parent Worker automatically when wrangler preview targets one that doesn't exist yet

    Previews hang off a parent Worker, so running wrangler preview before the Worker had ever been deployed failed with a raw API error naming the Preview endpoint. Wrangler now offers to create an empty parent Worker and then carries on creating the Preview. The parent uses the same workers.dev and Preview URL settings that wrangler deploy would resolve, without applying routes or cron triggers. In non-interactive environments, Wrangler creates the Worker without asking.

  • #​14735 30c2d47 Thanks @​vaishnav-mk! - Add individual and batch Workflow instance deletion to the runtime and SDK.

    • WorkflowInstance.delete() deletes one instance. Self-deletion stops the current execution.
    • env.MY_WORKFLOW.deleteBatch(instanceIds) deletes up to 100 instances and returns { deleted, errors } per input position.
    • wrangler workflows instances delete <name> [id..] deletes instances remotely or with --local; IDs can also come from a JSON array passed with --filename, with a combined limit of 100.
Patch Changes

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (in timezone Europe/Zurich)

  • Branch creation
    • "after 2pm on Monday"
  • 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.

@renovate

renovate Bot commented Aug 31, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: wrangler@4.129.1
npm error Found: @cloudflare/workers-types@5.20260804.1
npm error node_modules/@cloudflare/workers-types
npm error   @cloudflare/workers-types@"5.20260804.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional @cloudflare/workers-types@"^5.20260907.1" from wrangler@4.129.1
npm error node_modules/wrangler
npm error   dev wrangler@"4.129.1" from the root project
npm error
npm error Conflicting peer dependency: @cloudflare/workers-types@5.20260907.1
npm error node_modules/@cloudflare/workers-types
npm error   peerOptional @cloudflare/workers-types@"^5.20260907.1" from wrangler@4.129.1
npm error   node_modules/wrangler
npm error     dev wrangler@"4.129.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-09-21T23_07_46_064Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-09-21T23_07_46_064Z-debug-0.log

@renovate
renovate Bot force-pushed the renovate-external-dev-fixes branch 5 times, most recently from 682c314 to 7b78bc6 Compare September 8, 2026 09:29
@renovate
renovate Bot force-pushed the renovate-external-dev-fixes branch 7 times, most recently from fda43e6 to 030c7ef Compare September 15, 2026 21:35
@renovate
renovate Bot force-pushed the renovate-external-dev-fixes branch 5 times, most recently from 3d1f8a9 to 01636b2 Compare September 19, 2026 07:39
@renovate
renovate Bot force-pushed the renovate-external-dev-fixes branch from 01636b2 to 3288084 Compare September 21, 2026 23:07

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants