chore(deps): bump the runtime group across 1 directory with 3 updates

[dependabot]

Bumps the runtime group with 3 updates in the / directory: js-yaml, json-schema-faker and wrangler.

Updates js-yaml from 4.3.0 to 4.3.1

Changelog

Sourced from js-yaml's changelog.

4.3.1 - 2026-07-31

Security

• [backport] Remove quadratic complexity from !!omap duplicate key detection.

Commits

• 86e91b8 4.3.1 released
• c3cc4b0 Backport quadratic complexity fix for !!omap
• See full diff in compare view

Updates json-schema-faker from 0.6.2 to 0.6.3

Release notes

Sourced from json-schema-faker's releases.

v0.6.3

Features

• Add dependentSchemas and dependentRequired keyword support
• Add synchronous generateSync/createGeneratorSync API (#854)

Fixes

• Skip double generation in dependencies handler when a property is in both required and properties
• Scoped $defs resolution, quoted JSONPath keys, recursive descent fixes
• Register nested local definitions during schema walk (#869)
• Allow extensions to proceed into subschemas (#871)
• Parse bracket-quoted JSONPath keys (#873)
• Remove unused array item flag (#874)
• Isolate autoIncrement counters by schema path (#872)
• Apply optional property filtering to root example and default values
• Trampoline recursive schema walks to avoid stack overflow on deep schemas
• Prevent unhandled promise rejection at sync-mode async boundaries
• Allow refResolver in generateSync(), throw only if it returns a Promise

Commits

• 95b1845 chore: release 0.6.3
• 4a993cb Merge pull request #880 from json-schema-faker/fix/875-dependent-schemas
• 61d2af2 fix: address review feedback on dependentSchemas/dependentRequired
• 424f894 feat: implement dependentSchemas and dependentRequired keywords
• 9ba4cca Merge pull request #879 from json-schema-faker/feat/854-generate-sync
• 0316496 fix: trampoline recursive schema walks to avoid stack overflow on deep schemas
• 57d383b fix: prevent unhandled promise rejection at sync-mode async boundaries
• 92fb595 fix: allow refResolver in generateSync(), throw only if it returns a Promise
• fdc27f8 feat: add synchronous generateSync/createGeneratorSync API (#854)
• ca5eb00 Merge pull request #870 from luke-perry-ck/lp/fix-root-example-exclusions
• Additional commits viewable in compare view

Updates wrangler from 4.117.0 to 4.118.0

Release notes

Sourced from wrangler's releases.

wrangler@4.118.0

Minor Changes

• #14057 cc63aae Thanks @​matingathani! - Add --json flag to wrangler containers info for consistent JSON output with sibling commands list and instances

• #14944 a249591 Thanks @​nickpatt! - Enable local observability capture by default in dev

  wrangler dev and 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 behind X_LOCAL_OBSERVABILITY=true. Set X_LOCAL_OBSERVABILITY=false to opt out (for example if the extra per-worker collector/streaming-tail services cause trouble in a multi-process dev-registry setup).

• #14919 e0bbf55 Thanks @​avenceslau! - Add additional triggers to Workflows

  Workers 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 f92d1fc Thanks @​petebacondarwin! - Fix jsx_fragment being ignored when wrangler dev runs a custom build

  If your project uses a custom build and sets both jsx_factory and jsx_fragment, wrangler dev used your jsx_factory value for JSX fragments as well, so fragments compiled incorrectly. Your jsx_fragment value is now used.

• #14936 f92d1fc Thanks @​petebacondarwin! - Stop wrangler dev starting new work after you stop it or it reloads

  Stopping 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 dev leaves nothing running behind it.

• #14936 f92d1fc Thanks @​petebacondarwin! - Stop wrangler dev from running custom builds concurrently

  When several watched files changed at once — for example during a git pull or a "save all" — wrangler dev started 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.

... (truncated)

Commits

• 95d9b12 Version Packages (#14946)
• e0bbf55 [wrangler] Fix workflows errors messages (#14919)
• 38403cb [wrangler] Remove duplicated Workers + Assets deploy E2E (#14947)
• cec9d88 [workers-auth] Validate account IDs before using them in API requests (#13746)
• cc63aae [wrangler] fix(containers): add --json flag to wrangler containers info (#1...
• f92d1fc [wrangler] Serialize custom build watcher events to avoid concurrent runs (#1...
• 17dca96 [wrangler] Fix circular dependency build warning between api/index.ts and bin...
• See full diff in compare view