Skip to content

chore(deps-dev): bump the dev-dependencies group across 1 directory with 7 updates - #588

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-c4d0f0f8b7
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/dev-dependencies-c4d0f0f8b7

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 7, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the dev-dependencies group with 7 updates in the / directory:

Package From To
@cloudflare/workers-types 5.20261021.1 5.20261104.1
@fedify/fedify 2.4.4 2.4.5
@fedify/vocab 2.4.4 2.4.5
@types/node 26.6.5 26.6.6
eslint 10.13.0 10.14.0
typescript-eslint 8.72.0 8.72.1
wrangler 4.151.3 4.157.0

Updates @cloudflare/workers-types from 5.20261021.1 to 5.20261104.1

Commits

Updates @fedify/fedify from 2.4.4 to 2.4.5

Release notes

Sourced from @​fedify/fedify's releases.

Fedify 2.4.5

Released on October 24, 2026.

@​fedify/fedify

  • Fixed DNS rebinding bypassing the SSRF protection on Node.js and Bun. Deno requires a separate deployment mitigation, described below, and remains vulnerable without it. getAuthenticatedDocumentLoader(), outbound activity delivery (sendActivity()), and the NodeInfo client (getNodeInfo()) resolved a hostname once to check that it was public, and then let fetch() resolve it again to connect, so a hostname answering with a public address for the check and a private one for the connection could reach internal services. On Node.js and Bun, connections are now made only to the addresses that passed the check. Bun deployments that set the HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY environment variables should use Bun 1.4.3 or later, since earlier versions ignore the option to connect directly and send the requests through the proxy; see Bun behind an HTTP proxy for mitigations. On Bun versions before 1.3.11, requests to HTTPS servers on non-default ports now fail, since those versions cannot verify the certificate of a pinned connection against the original hostname; see HTTPS servers on non-default ports with Bun. [GHSA-r48c-xx2h-fv4g]
  • On Deno, fetch() offers no way to choose the addresses it connects to, so Fedify cannot close the gap above. Run Deno 2.8.1 or later with --deny-net listing private IPv4 ranges, [::1], and [::], and listen on a Unix domain socket. IPv6 private ranges cannot be listed in --deny-net and need to be blocked at the network layer. See Restricting outbound connections on Deno for details. For new and long-lived deployments, we recommend Node.js or Bun instead of Deno, since the Deno team has announced that it will end its development of the Deno runtime after a year of bug-fix and security releases. [GHSA-r48c-xx2h-fv4g]
  • Fixed FedifySpanExporter.getRecentTraces()'s activityCount drifting from the number of records getActivitiesByTraceId() actually returns for a trace when a span was re-exported, and a trace becoming permanently undiscoverable through getRecentTraces() if the separate summary entry it depended on was never successfully written. Both problems shared the same cause: counting and discovery depended on a separately maintained counter instead of the records that are actually stored. getRecentTraces() now computes every summary it returns directly from the activity records currently retained for each trace. This costs a scan of every retained record on each call, so its cost grows with the total number of retained records rather than with how much changed since the previous call, and limit does not reduce that cost; a deployment that retains many traces and polls getRecentTraces() should size its polling interval, TTL, and KvStore choice accordingly. [#1257, #1322 by Yujin Jung]
  • Fixed installation failures with strict peer dependency checks by keeping the OpenTelemetry API dependency within the range supported by the OpenTelemetry SDK. [#1324 by Jiwon Kwon]
  • Fixed repeated HTTP signature verification and signing-key owner lookups when a request context was checked concurrently with the same document and context loaders. null key-verification and owner-lookup results are now reused for those loaders within the request; checks that reject can still be retried. An owner result of null caused by an unverified key is not retained, allowing an owner lookup after another loader verifies the key. [#1313, #1315]
  • Fixed incoming requests failing to reach dispatchers when Mastodon decoded percent-encoded colons in path identifiers. Generated URIs and HTTP signature verification retain their existing behavior. [#1325]

@​fedify/cli

  • Fixed fedify nodeinfo fetching remote page and favicon URLs that lead to private network addresses. The command now skips the favicon when the page, icon, or a redirect points to a private address, while still showing the NodeInfo document. Upgrade @fedify/cli to protect the machine running the command. Reported by Zachariah Mithani. [GHSA-cj5r-cw77-6gwp]

@​fedify/postgres

  • PostgresKvStore no longer scans the entire table for expired entries after every write. Cleanup now deletes up to 1,000 rows per batch, including across partitioned or inherited tables, with a delay between attempts that shortens after a full batch. Store instances sharing a table do not sweep it concurrently. With a pooled client, writes no longer wait for cleanup, and a cleanup failure no longer fails the write. Caller-owned transactions and reserved connections still await cleanup and propagate its errors to avoid hiding a rollback. Reads continue to exclude expired entries before physical deletion. [#1308, #1314]
  • Fixed PostgresKvStore.set() retaining an old creation time when replacing an existing key. TTLs are now measured from the SQL statement clock on both insert and update, and expiration checks use that same clock inside caller-owned transactions. Replacing an expired value works before its row is physically deleted, and a replacement written with a zero TTL still reads as absent. [#1308, #1314]

@​fedify/testing

  • Fixed createFederation() ignoring allowPrivateAddress: true. Received activities and federation-created contexts now use document loaders that allow local servers, so calls such as follow.getActor() can resolve localhost actors in inbox listeners. [#1302, #1306]
  • Fixed missing runtime dependencies in the npm package. @fedify/vocab and @js-temporal/polyfill are now installed automatically so importing @fedify/testing works even when dependency hoisting is disabled on Node.js and Bun. [#1305, #1307]

@​fedify/uri-template

  • Added the allowUnencodedColon option to Router.route() for matching HTTP request paths containing decoded colons in variable values. Exact matches take precedence, and matching remains strict by default. [#1325]
  • Reduced excessive routing work on paths containing many colons, including paths with invalid percent encoding. Candidate traversal avoids repeated states, and matching rejects output that the template cannot produce while preserving route priority and colon compatibility. [#1325]

@​fedify/vocab-runtime

  • Fixed DNS rebinding bypassing the SSRF protection of getDocumentLoader() on Node.js and Bun. Deno requires a separate deployment mitigation, described in the @fedify/fedify section above, and remains vulnerable without it. The document loader resolved a hostname once to check that it was public, and then let fetch() resolve it again to connect. On Node.js and Bun, connections are now made only to the addresses that passed the check. The behavior of allowPrivateAddress is unchanged. [GHSA-r48c-xx2h-fv4g]
  • Added undici ^7.30.1 as a dependency, which is used on Node.js to connect only to validated addresses. [GHSA-r48c-xx2h-fv4g]
  • Documented that validatePublicUrl() only checks the addresses a hostname currently resolves to and does not pin the connection, so it alone does not prevent DNS rebinding. [GHSA-r48c-xx2h-fv4g]

@​fedify/webfinger

  • Fixed DNS rebinding bypassing the SSRF protection of lookupWebFinger() on Node.js and Bun. Deno requires a separate deployment mitigation, described in the @fedify/fedify section above, and remains vulnerable without it. [GHSA-r48c-xx2h-fv4g]
Changelog

Sourced from @​fedify/fedify's changelog.

Version 2.4.5

Released on October 24, 2026.

@​fedify/fedify

  • Fixed DNS rebinding bypassing the SSRF protection on Node.js and Bun. Deno requires a separate deployment mitigation, described below, and remains vulnerable without it. getAuthenticatedDocumentLoader(), outbound activity delivery (sendActivity()), and the NodeInfo client (getNodeInfo()) resolved a hostname once to check that it was public, and then let fetch() resolve it again to connect, so a hostname answering with a public address for the check and a private one for the connection could reach internal services. On Node.js and Bun, connections are now made only to the addresses that passed the check. Bun deployments that set the HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY environment variables should use Bun 1.4.3 or later, since earlier versions ignore the option to connect directly and send the requests through the proxy; see [Bun behind an HTTP proxy] for mitigations. On Bun versions before 1.3.11, requests to HTTPS servers on non-default ports now fail, since those versions cannot verify the certificate of a pinned connection against the original hostname; see [HTTPS servers on non-default ports with Bun]. [[GHSA-r48c-xx2h-fv4g]]
  • On Deno, fetch() offers no way to choose the addresses it connects to, so Fedify cannot close the gap above. Run Deno 2.8.1 or later with --deny-net listing private IPv4 ranges, [::1], and [::], and listen on a Unix domain socket. IPv6 private ranges cannot be listed in --deny-net and need to be blocked at the network layer. See [Restricting outbound connections on Deno] for details. For new and long-lived deployments, we recommend Node.js or Bun instead of Deno, since the Deno team has announced that it will end its development of the Deno runtime after a year of bug-fix and security releases. [[GHSA-r48c-xx2h-fv4g]]
  • Fixed FedifySpanExporter.getRecentTraces()'s activityCount drifting from the number of records getActivitiesByTraceId() actually returns for a trace when a span was re-exported, and a trace becoming permanently undiscoverable through getRecentTraces() if the separate summary entry it depended on was never successfully written. Both problems shared the same cause: counting and discovery depended on a separately maintained counter instead of the records that are actually stored. getRecentTraces() now computes every summary it returns directly from the activity records currently retained for each trace. This costs a scan of every retained record on each call, so its cost grows with the total number of retained records rather than with how much changed since the previous call, and limit does not reduce that cost; a deployment that retains many traces and polls getRecentTraces() should size its polling interval, TTL, and KvStore choice accordingly. [#1257, #1322 by Yujin Jung]

... (truncated)

Commits
  • daf84e3 Merge tag '2.3.15' into 2.4-maintenance
  • e174063 Merge tag '2.2.20' into 2.3-maintenance
  • 0777faa Merge tag '2.1.31' into 2.2-maintenance
  • fc72547 Merge tag '2.0.35' into 2.1-maintenance
  • d176ea2 Accept decoded colons in HTTP route variables
  • a87a1d3 Pin outbound connections to validated addresses on Bun
  • 7c65ca7 Cover trace summary recovery and reexports
  • 34b42b1 Compute getRecentTraces() straight from retained records
  • 4478836 Prefer Node.js in package documentation
  • bd2e373 Clarify null signing-key owner results
  • Additional commits viewable in compare view

Updates @fedify/vocab from 2.4.4 to 2.4.5

Release notes

Sourced from @​fedify/vocab's releases.

Fedify 2.4.5

Released on October 24, 2026.

@​fedify/fedify

  • Fixed DNS rebinding bypassing the SSRF protection on Node.js and Bun. Deno requires a separate deployment mitigation, described below, and remains vulnerable without it. getAuthenticatedDocumentLoader(), outbound activity delivery (sendActivity()), and the NodeInfo client (getNodeInfo()) resolved a hostname once to check that it was public, and then let fetch() resolve it again to connect, so a hostname answering with a public address for the check and a private one for the connection could reach internal services. On Node.js and Bun, connections are now made only to the addresses that passed the check. Bun deployments that set the HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY environment variables should use Bun 1.4.3 or later, since earlier versions ignore the option to connect directly and send the requests through the proxy; see Bun behind an HTTP proxy for mitigations. On Bun versions before 1.3.11, requests to HTTPS servers on non-default ports now fail, since those versions cannot verify the certificate of a pinned connection against the original hostname; see HTTPS servers on non-default ports with Bun. [GHSA-r48c-xx2h-fv4g]
  • On Deno, fetch() offers no way to choose the addresses it connects to, so Fedify cannot close the gap above. Run Deno 2.8.1 or later with --deny-net listing private IPv4 ranges, [::1], and [::], and listen on a Unix domain socket. IPv6 private ranges cannot be listed in --deny-net and need to be blocked at the network layer. See Restricting outbound connections on Deno for details. For new and long-lived deployments, we recommend Node.js or Bun instead of Deno, since the Deno team has announced that it will end its development of the Deno runtime after a year of bug-fix and security releases. [GHSA-r48c-xx2h-fv4g]
  • Fixed FedifySpanExporter.getRecentTraces()'s activityCount drifting from the number of records getActivitiesByTraceId() actually returns for a trace when a span was re-exported, and a trace becoming permanently undiscoverable through getRecentTraces() if the separate summary entry it depended on was never successfully written. Both problems shared the same cause: counting and discovery depended on a separately maintained counter instead of the records that are actually stored. getRecentTraces() now computes every summary it returns directly from the activity records currently retained for each trace. This costs a scan of every retained record on each call, so its cost grows with the total number of retained records rather than with how much changed since the previous call, and limit does not reduce that cost; a deployment that retains many traces and polls getRecentTraces() should size its polling interval, TTL, and KvStore choice accordingly. [#1257, #1322 by Yujin Jung]
  • Fixed installation failures with strict peer dependency checks by keeping the OpenTelemetry API dependency within the range supported by the OpenTelemetry SDK. [#1324 by Jiwon Kwon]
  • Fixed repeated HTTP signature verification and signing-key owner lookups when a request context was checked concurrently with the same document and context loaders. null key-verification and owner-lookup results are now reused for those loaders within the request; checks that reject can still be retried. An owner result of null caused by an unverified key is not retained, allowing an owner lookup after another loader verifies the key. [#1313, #1315]
  • Fixed incoming requests failing to reach dispatchers when Mastodon decoded percent-encoded colons in path identifiers. Generated URIs and HTTP signature verification retain their existing behavior. [#1325]

@​fedify/cli

  • Fixed fedify nodeinfo fetching remote page and favicon URLs that lead to private network addresses. The command now skips the favicon when the page, icon, or a redirect points to a private address, while still showing the NodeInfo document. Upgrade @fedify/cli to protect the machine running the command. Reported by Zachariah Mithani. [GHSA-cj5r-cw77-6gwp]

@​fedify/postgres

  • PostgresKvStore no longer scans the entire table for expired entries after every write. Cleanup now deletes up to 1,000 rows per batch, including across partitioned or inherited tables, with a delay between attempts that shortens after a full batch. Store instances sharing a table do not sweep it concurrently. With a pooled client, writes no longer wait for cleanup, and a cleanup failure no longer fails the write. Caller-owned transactions and reserved connections still await cleanup and propagate its errors to avoid hiding a rollback. Reads continue to exclude expired entries before physical deletion. [#1308, #1314]
  • Fixed PostgresKvStore.set() retaining an old creation time when replacing an existing key. TTLs are now measured from the SQL statement clock on both insert and update, and expiration checks use that same clock inside caller-owned transactions. Replacing an expired value works before its row is physically deleted, and a replacement written with a zero TTL still reads as absent. [#1308, #1314]

@​fedify/testing

  • Fixed createFederation() ignoring allowPrivateAddress: true. Received activities and federation-created contexts now use document loaders that allow local servers, so calls such as follow.getActor() can resolve localhost actors in inbox listeners. [#1302, #1306]
  • Fixed missing runtime dependencies in the npm package. @fedify/vocab and @js-temporal/polyfill are now installed automatically so importing @fedify/testing works even when dependency hoisting is disabled on Node.js and Bun. [#1305, #1307]

@​fedify/uri-template

  • Added the allowUnencodedColon option to Router.route() for matching HTTP request paths containing decoded colons in variable values. Exact matches take precedence, and matching remains strict by default. [#1325]
  • Reduced excessive routing work on paths containing many colons, including paths with invalid percent encoding. Candidate traversal avoids repeated states, and matching rejects output that the template cannot produce while preserving route priority and colon compatibility. [#1325]

@​fedify/vocab-runtime

  • Fixed DNS rebinding bypassing the SSRF protection of getDocumentLoader() on Node.js and Bun. Deno requires a separate deployment mitigation, described in the @fedify/fedify section above, and remains vulnerable without it. The document loader resolved a hostname once to check that it was public, and then let fetch() resolve it again to connect. On Node.js and Bun, connections are now made only to the addresses that passed the check. The behavior of allowPrivateAddress is unchanged. [GHSA-r48c-xx2h-fv4g]
  • Added undici ^7.30.1 as a dependency, which is used on Node.js to connect only to validated addresses. [GHSA-r48c-xx2h-fv4g]
  • Documented that validatePublicUrl() only checks the addresses a hostname currently resolves to and does not pin the connection, so it alone does not prevent DNS rebinding. [GHSA-r48c-xx2h-fv4g]

@​fedify/webfinger

  • Fixed DNS rebinding bypassing the SSRF protection of lookupWebFinger() on Node.js and Bun. Deno requires a separate deployment mitigation, described in the @fedify/fedify section above, and remains vulnerable without it. [GHSA-r48c-xx2h-fv4g]
Changelog

Sourced from @​fedify/vocab's changelog.

Version 2.4.5

Released on October 24, 2026.

@​fedify/fedify

  • Fixed DNS rebinding bypassing the SSRF protection on Node.js and Bun. Deno requires a separate deployment mitigation, described below, and remains vulnerable without it. getAuthenticatedDocumentLoader(), outbound activity delivery (sendActivity()), and the NodeInfo client (getNodeInfo()) resolved a hostname once to check that it was public, and then let fetch() resolve it again to connect, so a hostname answering with a public address for the check and a private one for the connection could reach internal services. On Node.js and Bun, connections are now made only to the addresses that passed the check. Bun deployments that set the HTTP_PROXY, HTTPS_PROXY, or ALL_PROXY environment variables should use Bun 1.4.3 or later, since earlier versions ignore the option to connect directly and send the requests through the proxy; see [Bun behind an HTTP proxy] for mitigations. On Bun versions before 1.3.11, requests to HTTPS servers on non-default ports now fail, since those versions cannot verify the certificate of a pinned connection against the original hostname; see [HTTPS servers on non-default ports with Bun]. [[GHSA-r48c-xx2h-fv4g]]
  • On Deno, fetch() offers no way to choose the addresses it connects to, so Fedify cannot close the gap above. Run Deno 2.8.1 or later with --deny-net listing private IPv4 ranges, [::1], and [::], and listen on a Unix domain socket. IPv6 private ranges cannot be listed in --deny-net and need to be blocked at the network layer. See [Restricting outbound connections on Deno] for details. For new and long-lived deployments, we recommend Node.js or Bun instead of Deno, since the Deno team has announced that it will end its development of the Deno runtime after a year of bug-fix and security releases. [[GHSA-r48c-xx2h-fv4g]]
  • Fixed FedifySpanExporter.getRecentTraces()'s activityCount drifting from the number of records getActivitiesByTraceId() actually returns for a trace when a span was re-exported, and a trace becoming permanently undiscoverable through getRecentTraces() if the separate summary entry it depended on was never successfully written. Both problems shared the same cause: counting and discovery depended on a separately maintained counter instead of the records that are actually stored. getRecentTraces() now computes every summary it returns directly from the activity records currently retained for each trace. This costs a scan of every retained record on each call, so its cost grows with the total number of retained records rather than with how much changed since the previous call, and limit does not reduce that cost; a deployment that retains many traces and polls getRecentTraces() should size its polling interval, TTL, and KvStore choice accordingly. [#1257, #1322 by Yujin Jung]

... (truncated)

Commits

Updates @types/node from 26.6.5 to 26.6.6

Commits

Updates eslint from 10.13.0 to 10.14.0

Release notes

Sourced from eslint's releases.

v10.14.0

Features

  • d23a7f9 feat: fix property descriptor handling in func-name-matching (#21400) (xbinaryx)

Bug Fixes

  • 4a12580 fix: require minimatch 10.2.6 to avoid vulnerable brace-expansion (#21460) (lumir)
  • 827a8f3 fix: no-restricted-globals crash on global objects as property values (#21449) (xbinaryx)
  • 161558a fix: handle LS, PS and empty hashbang comments (#21419) (lumir)
  • 6194939 fix: no-invalid-this crash on accessor fields without initializer (#21442) (xbinaryx)
  • 9155e14 fix: Update @​humanfs/node dependency version (#21434) (Nicholas C. Zakas)
  • cb2b9d4 fix: avoid invalid object-shorthand fixes for super methods (#21323) (dvd233)
  • 5ee3915 fix: yoda invalid autofix at statement start (#21424) (Daniel Pinto)

Documentation

  • 0f94f47 docs: remove zh-hans from docs language switcher (#21437) (lumir)
  • dab466e docs: Update README (GitHub Actions Bot)
  • 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#21452) (Pixel)
  • 7697550 docs: Update README (GitHub Actions Bot)
  • 0c699d5 docs: Remove Tidelift commercial support (#21416) (Milos Djermanovic)
  • 0880666 docs: update loadESLint() documentation for v10 (#21374) (Minseon Kim)
  • e06fe87 docs: Revise AI acknowledgment options in PR template (#21414) (Nicholas C. Zakas)

Chores

  • 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#21462) (Francesco Trotta)
  • 6e3f988 chore: update github/codeql-action action to v4.39.1 (#21450) (renovate[bot])
  • a031c40 chore: update ecosystem plugins (#21445) (ESLint Bot)
  • 67d2ca2 chore: add troubleshooting page URL to circular fixes warning message (#21429) (Milos Djermanovic)
  • 276021d chore: update github/codeql-action action to v4.39.0 (#21432) (renovate[bot])
  • 449724e chore: update ecosystem plugins (#21420) (ESLint Bot)
  • 8ffeb8c chore: update dependency prettier to v3.9.10 (#21417) (renovate[bot])
Commits
  • 12cbff4 10.14.0
  • 6b696e7 Build: changelog update for 10.14.0
  • 0e2ab70 ci: disable eslint-plugin-unicorn ecosystem test (#21462)
  • 4a12580 fix: require minimatch 10.2.6 to avoid vulnerable brace-expansion (#21460)
  • 0f94f47 docs: remove zh-hans from docs language switcher (#21437)
  • dab466e docs: Update README
  • 827a8f3 fix: no-restricted-globals crash on global objects as property values (#21449)
  • 97431f8 docs: replace --rulesdir with a virtual plugin in custom rules docs (#21452)
  • 6e3f988 chore: update github/codeql-action action to v4.39.1 (#21450)
  • 161558a fix: handle LS, PS and empty hashbang comments (#21419)
  • Additional commits viewable in compare view

Updates typescript-eslint from 8.72.0 to 8.72.1

Release notes

Sourced from typescript-eslint's releases.

v8.72.1

8.72.1 (2026-10-26)

🩹 Fixes

  • eslint-plugin: [no-unnecessary-condition] false positives on unresolved conditional types (#13062)
  • eslint-plugin: [no-unnecessary-type-assertion] bound recursive type traversal instead of catching stack overflows (#13039)
  • typescript-estree: use one Program per tsconfig for the project service in single-run mode (#12988)

❤️ Thank You

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Changelog

Sourced from typescript-eslint's changelog.

8.72.1 (2026-10-26)

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

Commits

Updates wrangler from 4.151.3 to 4.157.0

Release notes

Sourced from wrangler's releases.

wrangler@4.157.0

Minor Changes

  • #16660 34f34b3 Thanks @​punkeel! - Allow opting into zstd compression for Wrangler-built container image layers with WRANGLER_CONTAINER_IMAGE_COMPRESSION=zstd.

Patch Changes

  • #16670 b14b9dc Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-03

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16011 44d1ee4 Thanks @​wra-sol! - Offer to delete a Worker's Container applications when running wrangler delete

    Previously, wrangler delete removed only the Worker, leaving the Container applications that wrangler deploy created for it running and billing. It now offers to delete them as well. With --force, or in CI and other non-interactive contexts, it lists them instead so they can be removed with wrangler containers delete <id>.

  • #16670 b14b9dc Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261102.1 ^5.20261103.1
    workerd 1.20261102.1 1.20261103.1
  • Updated dependencies [b14b9dc, b14b9dc, d2eda1c, 2750917]:

wrangler@4.156.2

Patch Changes

  • #16642 d38cb02 Thanks @​dependabot! - Update DEFAULT_COMPAT_DATE to 2026-11-02

    Use the bundled workerd release's compatibility date by default when scaffolding new projects or when no compatibility date is configured.

  • #16642 d38cb02 Thanks @​dependabot! - Update dependencies of "miniflare", "wrangler"

    The following dependency versions have been updated:

    Dependency From To
    @​cloudflare/workers-types ^5.20261101.1 ^5.20261102.1
    workerd 1.20261101.1 1.20261102.1
  • #16623 51bbf8b Thanks @​petebacondarwin! - Deprecate shared tooling helper exports from Miniflare

    Miniflare continues to export getNodeCompat, NodeJSCompatMode, and getFreshSourceMapSupport for compatibility. These exports are deprecated and now use the implementations in @cloudflare/workers-utils. Add a dependency on that package and replace the Miniflare imports with:

    import {
      getNodeCompat,

... (truncated)

Commits
  • 9a0732c Version Packages (#16654)
  • 44d1ee4 fix(wrangler): stop wrangler delete orphaning Container applications (#16011)
  • 8ac43df Require explicit route metadata flags when downloading Worker configuration (...
  • 680666e Version Packages (#16646)
  • e5b1798 Avoid unrelated route permission checks when comparing dashboard configuratio...
  • 51bbf8b [miniflare] Move shared tooling helpers to workers-utils (#16623)
  • 1598fd3 [vitest-plugin] Support cloudflare.config.ts with the new config option (#16424)
  • ca55031 Version Packages (#16598)
  • 2667a9f [wrangler] Fix Pages Functions middleware routing for repeated slashes (#16603)
  • 5740867 [wrangler] Enforce the Pages development asset directory boundary (#16535)
  • Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

…ith 7 updates

Bumps the dev-dependencies group with 7 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@cloudflare/workers-types](https://github.com/cloudflare/workerd) | `5.20261021.1` | `5.20261104.1` |
| [@fedify/fedify](https://github.com/fedify-dev/fedify/tree/HEAD/packages/fedify) | `2.4.4` | `2.4.5` |
| [@fedify/vocab](https://github.com/fedify-dev/fedify/tree/HEAD/packages/vocab) | `2.4.4` | `2.4.5` |
| [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node) | `26.6.5` | `26.6.6` |
| [eslint](https://github.com/eslint/eslint) | `10.13.0` | `10.14.0` |
| [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint) | `8.72.0` | `8.72.1` |
| [wrangler](https://github.com/cloudflare/workers-sdk/tree/HEAD/packages/wrangler) | `4.151.3` | `4.157.0` |



Updates `@cloudflare/workers-types` from 5.20261021.1 to 5.20261104.1
- [Release notes](https://github.com/cloudflare/workerd/releases)
- [Changelog](https://github.com/cloudflare/workerd/blob/main/RELEASE.md)
- [Commits](https://github.com/cloudflare/workerd/commits)

Updates `@fedify/fedify` from 2.4.4 to 2.4.5
- [Release notes](https://github.com/fedify-dev/fedify/releases)
- [Changelog](https://github.com/fedify-dev/fedify/blob/main/CHANGES.md)
- [Commits](https://github.com/fedify-dev/fedify/commits/2.4.5/packages/fedify)

Updates `@fedify/vocab` from 2.4.4 to 2.4.5
- [Release notes](https://github.com/fedify-dev/fedify/releases)
- [Changelog](https://github.com/fedify-dev/fedify/blob/main/CHANGES.md)
- [Commits](https://github.com/fedify-dev/fedify/commits/2.4.5/packages/vocab)

Updates `@types/node` from 26.6.5 to 26.6.6
- [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases)
- [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node)

Updates `eslint` from 10.13.0 to 10.14.0
- [Release notes](https://github.com/eslint/eslint/releases)
- [Commits](eslint/eslint@v10.13.0...v10.14.0)

Updates `typescript-eslint` from 8.72.0 to 8.72.1
- [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases)
- [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md)
- [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.72.1/packages/typescript-eslint)

Updates `wrangler` from 4.151.3 to 4.157.0
- [Release notes](https://github.com/cloudflare/workers-sdk/releases)
- [Commits](https://github.com/cloudflare/workers-sdk/commits/wrangler@4.157.0/packages/wrangler)

---
updated-dependencies:
- dependency-name: "@cloudflare/workers-types"
  dependency-version: 5.20261104.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: "@fedify/fedify"
  dependency-version: 2.4.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@fedify/vocab"
  dependency-version: 2.4.5
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: "@types/node"
  dependency-version: 26.6.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: eslint
  dependency-version: 10.14.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
- dependency-name: typescript-eslint
  dependency-version: 8.72.1
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: dev-dependencies
- dependency-name: wrangler
  dependency-version: 4.157.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: dev-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from davidwkeith as a code owner November 7, 2026 23:54
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 7, 2026
@dependabot @github

dependabot Bot commented on behalf of github Nov 14, 2026

Copy link
Copy Markdown
Contributor Author

Looks like these dependencies are updatable in another way, so this is no longer needed.

@dependabot dependabot Bot closed this Nov 14, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/dev-dependencies-c4d0f0f8b7 branch November 14, 2026 23:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants