Skip to content

deps(api): bump the minor-and-patch group across 1 directory with 9 updates - #95

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/api/minor-and-patch-6a6b9b051a
Closed

deps(api): bump the minor-and-patch group across 1 directory with 9 updates#95
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/bun/api/minor-and-patch-6a6b9b051a

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Sep 7, 2026 •
edited
Loading

Copy link
Copy Markdown

Bumps the minor-and-patch group with 9 updates in the /api directory:

Package From To
axios 1.18.1 1.20.0
dayjs 1.11.21 1.11.23
exiftool-vendored 37.0.0 37.2.0
fs-extra 11.3.6 11.4.0
i18next-http-middleware 3.9.7 3.9.8
posthog-node 5.45.2 5.51.6
pretty-bytes 7.1.1 7.1.3
@types/bun 1.3.14 1.4.0
bun-types 1.3.14 1.4.1

Updates axios from 1.18.1 to 1.20.0

Release notes

Sourced from axios's releases.

v1.20.0 — August 19, 2026

This release hardens runtime option handling, adds RFC 9110 status-code aliases, fixes Node.js and XHR reliability issues, and refreshes project tooling and documentation.

⚠️ Breaking Changes & Deprecations

  • HTTP Status Naming: Added ContentTooLarge (413) and UnprocessableContent (422), while retaining PayloadTooLarge and UnprocessableEntity as backward-compatible deprecated aliases. (#11082)

🔒 Security Fixes

  • Runtime Option Handling: Hardened behavioral configuration reads against shared and foreign prototype pollution and normalized unsafe interceptor replacement objects. This also clarifies Fetch redirect and custom implementation behavior, HTTP/2 DNS and proxy handling, CIDR-based NO_PROXY matching, and malformed data URI rejection; see the PR for documented compatibility effects. (#11141)

🐛 Bug Fixes

  • Interceptor Lifecycle: Prevented unbounded handler-array growth by trimming trailing ejected interceptors without changing iteration semantics, and kept interceptor operations safe when the public handlers field is nullish. (#11087, #11118)
  • Request Error Preservation: Prevented custom Error.prepareStackTrace implementations that return non-string values from replacing the original request failure with an unrelated TypeError. (#11109)
  • XHR Reliability: Navigation-canceled requests now reject with ECONNABORTED instead of resolving with status 0, while successful downloads flush their final progress callback during the live loadend dispatch. (#11094, #11121)
  • Node.js Socket Memory: Removed request-context retention from per-socket error listeners, preventing completed response data from being pinned for the lifetime of pooled keep-alive sockets. (#11091)
  • Core Methods and HTTP Errors: Prevented structural method-header buckets from leaking into outgoing headers, standardized invalid DNS lookup and httpVersion failures as AxiosError.ERR_BAD_OPTION_VALUE, and corrected the timeoutErrorMessage merge strategy. (#11096)

🔧 Maintenance & Chores

  • Dependencies: Updated fast-uri, postcss, js-yaml, mocha, development-tooling groups, and GitHub Actions dependencies. (#11092, #11098, #11099, #11106, #11107, #11122, #11123, #11126, #11127, #11133, #11140, #11143, #11144)
  • Documentation: Applied the v1.19.0 documentation updates, added the missing fs import to the README stream example, introduced localized global search, and repaired the interceptor test link. (#11101, #11113, #11097, #11119)
  • Sponsorship: Updated sponsorship links and data and added ScrapingBee as a sponsor. (#11124, #11136, #11137)
  • CI and Release: Switched ESM smoke tests to locked dependencies and synchronized package and runtime version metadata for v1.20.0. (#11128, #11152)

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve axios:

Full Changelog (axios/axios@v1.19.0...v1.20.0)

v1.19.0 - July 22, 2026

This release raises the form-data security floor, adds configuration and type-system capabilities, and fixes NO_PROXY matching, interceptor errors, progress reporting, and serialization edge cases.

🔒 Security Fixes

  • Multipart Form Data: Raised the form-data dependency floor to ^4.0.6, preventing fresh installations from resolving versions affected by the CRLF injection vulnerability GHSA-hmw2-7cc7-3qxx (GHSA-hmw2-7cc7-3qxx). (#11028)

... (truncated)

Changelog

Sourced from axios's changelog.

Changelog

v1.19.0 — July 22, 2026

This release raises the form-data security floor, adds configuration and type-system capabilities, and fixes NO_PROXY matching, interceptor errors, progress reporting, and serialization edge cases.

🔒 Security Fixes

  • Multipart Form Data: Raised the form-data dependency floor to ^4.0.6, preventing fresh installations from resolving versions affected by the CRLF injection vulnerability GHSA-hmw2-7cc7-3qxx (GHSA-hmw2-7cc7-3qxx). (#11028)

🚀 New Features

  • Configuration Extensibility: Preserved own-enumerable symbol-keyed fields through mergeConfig and added a generic params type across public TypeScript declarations, responses, errors, adapters, and serializers. (#11043, #11081)
  • Header Parameter Parsing: Added the opt-in AxiosHeaders.parseParameters() parser for quote-aware, RFC-style HTTP parameter parsing while preserving legacy parsing behavior. (#11051)
  • HTTP Status Codes: Added the missing Cloudflare 520 WebServerReturnsAnUnknownError status and matching ESM/CJS declarations. (#11067)

🐛 Bug Fixes

  • Form Data Conversion: Limited formDataToJSON path splitting to dot and bracket notation, preserving literal punctuation in keys, and removed browser-facing Buffer.from usage from toFormData to avoid unnecessary polyfills. (#11006, #11018)

  • Proxy Bypass: Canonicalized IPv4 shorthand, octal, and hexadecimal forms during NO_PROXY matching and honored * entries within comma- or space-separated bypass lists. (#11029, #11053)

  • Cancellation: Propagated already-aborted input signals immediately when composing abort signals. (#11035)

  • Header Handling: Preserved empty first values for duplicate singleton headers and made AxiosHeaders#getSetCookie() consistently return arrays for present values. (#11036, #11037)

  • URL Handling: Included normalized, safely redacted offending URLs in malformed-protocol errors and removed repeated trailing slashes when combining base URLs. (#11008, #11038)

  • Progress Events: Clamped malformed negative progress values to zero and ensured final Node.js download progress events are delivered before streamed responses close. (#11039, #11040)

  • Error and JSON Serialization: Serialized Set values as arrays in JSON-compatible snapshots and synthesized useful AxiosError messages from otherwise-empty AggregateError instances. (#11044, #11059)

  • Content-Length Enforcement: Corrected base64 data: URL size estimation so maxContentLength is enforced consistently by the HTTP and Fetch adapters. (#11061)

  • Synchronous Interceptors: Prevented requests from being dispatched after synchronous request interceptors fail unless their paired rejection handler resolves successfully. (#11071)

🔧 Maintenance & Chores

  • Dependencies: Updated development and test tooling, the docs fixture's Axios version, and GitHub Actions integrations including Checkout, Setup Node, Setup Deno, and Zizmor. (#11031, #11055, #11056, #11058, #11079, #11080, #11088, #11089, #11090)
  • Build Outputs: Limited sourcemap generation to published minified bundles, removing broken map references from non-minified builds. (#11054)
  • Form Data Internals: Centralized FormData header handling and made the Node.js adapter tolerate getHeaders() returning undefined under the content-only policy. (#11062)
  • Developer Experience: Ignored common local AI-tooling directories and fixed a constant-reassignment crash when the development sandbox serves its root path. (#11032, #11073)
  • Documentation: Updated sponsor information, clarified that baseURL is not a path-security boundary, scoped provenance claims to attested releases, and corrected the configuration-defaults documentation. (#11041, #11068, #11076, #11078)
  • Publishing: Simplified v1 publishing to use the npm version bundled with Node.js 26 and updated package metadata for the 1.19.0 release. (#11083, #11095)

🌟 New Contributors

We are thrilled to welcome our new contributors. Thank you for helping improve Axios:

... (truncated)

Commits
  • 84a9f3b chore(release): prepare release 1.20.0 (#11152)
  • e6824ee fix: core methodList, HTTP adapter errors, and add tests (#11096)
  • d8a919f fix(xhr): flush final progress during the live loadend dispatch (#11121)
  • 2d2a21a fix(interceptors): tolerate nullish handlers in syncHandlerEntries (#11118)
  • d19040b fix: harden runtime option handling (#11141)
  • e0a02dd chore(deps): bump zizmorcore/zizmor-action from 0.6.1 to 0.6.2 in the github-...
  • d10cb3a chore(deps-dev): bump the development_dependencies group with 4 updates (#11143)
  • 2c94646 chore(deps): bump js-yaml and mocha in /tests/smoke/cjs (#11133)
  • 76c12bc chore(deps-dev): bump js-yaml from 4.3.0 to 4.3.1 (#11140)
  • ba98559 docs: add ScrapingBee sponsor (#11137)
  • Additional commits viewable in compare view

Updates dayjs from 1.11.21 to 1.11.23

Release notes

Sourced from dayjs's releases.

v1.11.23

1.11.23 (2026-08-17)

Bug Fixes

  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (dad46e6)
  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (#3181) (2a3785f)

v1.11.22

1.11.22 (2026-08-16)

Bug Fixes

  • plugin: timezone compute instance .tz() offset without host DST (#3174) (e27ee80), closes #3169
Changelog

Sourced from dayjs's changelog.

1.11.23 (2026-08-17)

Bug Fixes

  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (dad46e6)
  • plugin: timezone plugin prevent RangeError for invalid Day.js values (#3180) (#3181) (2a3785f)

1.11.22 (2026-08-16)

Bug Fixes

  • plugin: timezone compute instance .tz() offset without host DST (#3174) (e27ee80), closes #3169
Commits
  • 4549b8d chore(release): 1.11.23 [skip ci]
  • 2a3785f fix(plugin): timezone plugin prevent RangeError for invalid Day.js values (#3...
  • dad46e6 fix(plugin): timezone plugin prevent RangeError for invalid Day.js values (#3...
  • ae3a550 chore(release): 1.11.22 [skip ci]
  • accfc67 D2M (#3177)
  • e27ee80 fix(plugin): timezone compute instance .tz() offset without host DST (#3174)
  • 98364bc chore: update doc
  • f6a1556 chore: update doc
  • 6609c5e chore: update doc
  • See full diff in compare view

Updates exiftool-vendored from 37.0.0 to 37.2.0

Release notes

Sourced from exiftool-vendored's releases.

Release 37.2.0

  • 🐞 Pull in new exiftool-vendored.pl and exiftool-vendored.exe that have this patch applied to avoid orphaned ExifTool processes if the parent process is killed or crashes

  • 📦 The published package now contains only runtime output, tag metadata, and the standard package documents. Compiled tests and maintainer-only update tools are no longer shipped, which removes 130 files from the tarball. Code that imported exiftool-vendored/dist/update/* or a compiled *.spec.js must stop doing so.

  • 📦 Replaced direct npm publishing with a least-privilege, tag-bound release flow. CI now verifies signed tags and the exact package artifact, stages the package behind maintainer 2FA approval, and excludes compiled tests and maintainer tools from the public tarball.

Commits

Full Changelog: photostructure/exiftool-vendored.js@37.1.0...37.2.0

Release 37.1.0

  • 📦 Updated to batch-cluster v19.0.0, which closes several ways an ExifTool child process could be leaked, and two ways a task's promise could be dropped: pending work now keeps the event loop alive (a task queued while the pool was momentarily empty used to be abandoned, with node exiting 0 and no error), and .end() now rejects still-queued tasks instead of leaving them unsettled. await exiftool.end() is now a barrier — it waits for in-flight spawns and recycling, so await exiftool.end(); process.exit(0) can no longer orphan a child — and may take slightly longer to resolve than in v37.0.0.

  • ✨ Documented maxFailedTasksPerProcess on ExifToolOptions. It stays disabled (0), matching batch-cluster v19's new default. Enabling it suits ExifTool poorly: a rejected task nearly always means the file was bad, not that ExifTool is sick, and -stay_open mode keeps working after per-file errors, so recycling costs a Perl interpreter startup per bad file. Sick processes are still recycled by taskTimeoutMillis, stream errors, and healthCheckCommand.

  • ✨ Documented batch-cluster's new killProcessGroup option on ExifToolOptions, defaulting to false. It only matters for a processFactory that spawns with detached: true, which ExifTool's default factory does not. TypeScript consumers who build a complete ExifToolOptions object by hand must add this new required property; Partial<ExifToolOptions> callers are unaffected.

    Commits

    Full Changelog: photostructure/exiftool-vendored.js@37.0.0...37.1.0

Changelog

Sourced from exiftool-vendored's changelog.

v37.2.0

  • 🐞 Pull in new exiftool-vendored.pl and exiftool-vendored.exe that have this patch applied to avoid orphaned ExifTool processes if the parent process is killed or crashes

  • 📦 The published package now contains only runtime output, tag metadata, and the standard package documents. Compiled tests and maintainer-only update tools are no longer shipped, which removes 130 files from the tarball. Code that imported exiftool-vendored/dist/update/* or a compiled *.spec.js must stop doing so.

  • 📦 Replaced direct npm publishing with a least-privilege, tag-bound release flow. CI now verifies signed tags and the exact package artifact, stages the package behind maintainer 2FA approval, and excludes compiled tests and maintainer tools from the public tarball.

v37.1.0

  • 📦 Updated to batch-cluster v19.0.0, which closes several ways an ExifTool child process could be leaked, and two ways a task's promise could be dropped: pending work now keeps the event loop alive (a task queued while the pool was momentarily empty used to be abandoned, with node exiting 0 and no error), and .end() now rejects still-queued tasks instead of leaving them unsettled. await exiftool.end() is now a barrier — it waits for in-flight spawns and recycling, so await exiftool.end(); process.exit(0) can no longer orphan a child — and may take slightly longer to resolve than in v37.0.0.

  • ✨ Documented maxFailedTasksPerProcess on ExifToolOptions. It stays disabled (0), matching batch-cluster v19's new default. Enabling it suits ExifTool poorly: a rejected task nearly always means the file was bad, not that ExifTool is sick, and -stay_open mode keeps working after per-file errors, so recycling costs a Perl interpreter startup per bad file. Sick processes are still recycled by taskTimeoutMillis, stream errors, and healthCheckCommand.

  • ✨ Documented batch-cluster's new killProcessGroup option on ExifToolOptions, defaulting to false. It only matters for a processFactory that spawns with detached: true, which ExifTool's default factory does not. TypeScript consumers who build a complete ExifToolOptions object by hand must add this new required property; Partial<ExifToolOptions> callers are unaffected.

Commits
  • efdf74c Release 37.2.0
  • 6f0a01a ci(publish.yaml): stage npm releases behind a signed tag and 2FA approval
  • 227314c fix(package.json): pull in vendored ExifTool that exits with its parent
  • 5e71d4b fix(package.json): spell out the build steps ignore-scripts disabled
  • fe948d2 chore: add .pinact.yaml configuration file with min_age settings
  • 33bf3d6 chore: update cooldown logic and npm configuration for dependency management
  • f5ff4be chore(package.json): update files field to include specific files and exclude...
  • 2cd59ca chore(skill): remove in deference to https://github.com/photostructure/coding...
  • 4525930 chore: update dependencies to latest versions
  • 321d8cf chore(package.json): rename the pre-release check to preflight
  • Additional commits viewable in compare view

Updates fs-extra from 11.3.6 to 11.4.0

Changelog

Sourced from fs-extra's changelog.

11.4.0 / 2026-07-23

  • Proper EEXIST error when trying to create a symlink and the dest already exists as a broken symlink (#925, #1076)
Commits

Updates i18next-http-middleware from 3.9.7 to 3.9.8

Changelog

Sourced from i18next-http-middleware's changelog.

v3.9.8

  • security: validate lng/ns in missingKeyHandler before forwarding them to backendConnector.saveMissing(). The route params were used unvalidated, while the sibling getResourcesHandler already filtered them since 3.9.3. Because those values become the {{lng}}/{{ns}} segments of the backend's addPath, and route params arrive percent-decoded, a request such as POST /locales/add/..%2f..%2f..%2ftmp%2fpwned/x could write outside the locales directory on i18next-fs-backend; lng=__proto__ additionally reached that backend's queuedWrites path walk. Unsafe values now get a 400 and never reach the backend. The same isSafeLangIdentifier/isSafeNsIdentifier split applies, so legitimate values (including nested namespaces like a/b) are unaffected.
  • security: apply utils.isSafeLangIdentifier to detected languages in LanguageDetector.detect(). Detected values come from untrusted request input (querystring, path, cookie, session, header) and were filtered only by utils.hasXSS, which targets markup payloads and does not reject .., /, \, control characters or prototype keys. With the default supportedLngs: false, i18next resolves any string, so a crafted ?lng= could reach the backend's loadPath as a traversal segment (arbitrary file read on i18next-fs-backend, request forgery on i18next-http-backend). The check runs after convertDetectedLanguage, so a custom converter cannot reintroduce an unsafe value. All five built-in detectors converge on this one filter.
Commits
  • e4c0285 3.9.8
  • 9dd7c94 security: validate lng/ns in missingKeyHandler and detected languages
  • fbce4c4 Bump i18next-fs-backend from 2.6.4 to 2.6.6 in /example/fastify-pug (#133)
  • fd3a7c8 Bump i18next-http-middleware in /example/basic-locize (#132)
  • 25815ef Bump @​babel/core from 7.29.0 to 7.29.6 (#131)
  • 40fdedc package.json: use HTTPS URL for repository metadata
  • 01f2dc2 changelog: link 3.9.7 entry to published advisory GHSA-f49m-vf83-692w
  • a3722a8 Bump i18next-fs-backend from 1.0.7 to 2.6.4 in /example/basic-pug (#129)
  • See full diff in compare view

Updates posthog-node from 5.45.2 to 5.51.6

Release notes

Sourced from posthog-node's releases.

posthog-node@5.51.6

5.51.6

Patch Changes

posthog-node@5.51.5

5.51.5

Patch Changes

posthog-node@5.51.4

5.51.4

Patch Changes

  • #4636 74ff567 Thanks @​yfwmaniish! - Narrow the pinterest entry in the bot-detection blocklist to pinterestbot, so real users on Pinterest's in-app browser (whose UA also contains the substring pinterest) are no longer misclassified as bots and silently excluded from analytics. The crawler's other UA variant remains covered by the existing generic bot.htm entry, so no bot-detection coverage is lost. (2026-08-27)

  • #4660 dfc3b59 Thanks @​posthog! - Honor evaluationContexts during local evaluation — flags whose evaluation contexts don't overlap the configured list are no longer evaluated locally and resolve to undefined. (2026-08-27)

  • Updated dependencies [74ff567]:

    • @​posthog/core@​1.49.1

posthog-node@5.51.3

5.51.3

Patch Changes

posthog-node@5.51.2

5.51.2

Patch Changes

... (truncated)

Changelog

Sourced from posthog-node's changelog.

5.51.6

Patch Changes

5.51.5

Patch Changes

5.51.4

Patch Changes

  • #4636 74ff567 Thanks @​yfwmaniish! - Narrow the pinterest entry in the bot-detection blocklist to pinterestbot, so real users on Pinterest's in-app browser (whose UA also contains the substring pinterest) are no longer misclassified as bots and silently excluded from analytics. The crawler's other UA variant remains covered by the existing generic bot.htm entry, so no bot-detection coverage is lost. (2026-08-27)

  • #4660 dfc3b59 Thanks @​posthog! - Honor evaluationContexts during local evaluation — flags whose evaluation contexts don't overlap the configured list are no longer evaluated locally and resolve to undefined. (2026-08-27)

  • Updated dependencies [74ff567]:

    • @​posthog/core@​1.49.1

5.51.3

Patch Changes

5.51.2

Patch Changes

  • #4639 1faeb74 Thanks @​marandaneto! - Handle empty feature flag evaluation key scopes without running local or remote evaluation. (2026-08-25)

  • #4610 930de19 Thanks @​marandaneto! - Share feature flag matching, hashing, variant, and payload evaluation helpers across the Node.js and Convex SDKs without changing their runtime-specific SemVer behavior. (2026-08-25)

  • Updated dependencies [930de19, d4eee8f]:

... (truncated)

Commits
  • cd4ba6b chore: update versions and lockfile [version bump]
  • 56148bd fix(node): expose exception capture methods on IPostHog (#4719)
  • b99bf99 chore: update versions and lockfile [version bump]
  • f136c60 chore: update versions and lockfile [version bump]
  • dfc3b59 fix(node): honor evaluationContexts during local evaluation (#4660)
  • db9c291 chore: update versions and lockfile [version bump]
  • e899b1c fix(flags): align presence operator semantics (#4651)
  • d22676a chore: update versions and lockfile [version bump]
  • 1faeb74 fix(flags): handle empty evaluation key scopes (#4639)
  • d4eee8f refactor(surveys): share property matching helpers (#4611)
  • Additional commits viewable in compare view

Updates pretty-bytes from 7.1.1 to 7.1.3

Release notes

Sourced from pretty-bytes's releases.

v7.1.3

  • Fix fractional digit formatting when localization is disabled (#92) 5cb9c95

sindresorhus/pretty-bytes@v7.1.2...v7.1.3

v7.1.2

  • Fix rounding across unit boundaries 059c979

sindresorhus/pretty-bytes@v7.1.1...v7.1.2

Commits

Updates @types/bun from 1.3.14 to 1.4.0

Commits

Updates bun-types from 1.3.14 to 1.4.1

Release notes

Sourced from bun-types's releases.

Bun v1.4.1

To install Bun v1.4.1

curl -fsSL https://bun.sh/install | bash
# or you can use npm
# npm install -g bun

Windows:

powershell -c "irm bun.sh/install.ps1|iex"

To upgrade to Bun v1.4.1:

bun upgrade

Read Bun v1.4.1's release notes on Bun's blog

Thanks to 7 contributors!

Bun v1.4

To install Bun v1.4

curl -fsSL https://bun.com/install | bash
# or you can use npm
# npm install -g bun

Windows:

powershell -c "irm bun.com/install.ps1|iex"

To upgrade to Bun v1.4.0:

bun upgrade

... (truncated)

Commits
  • 9c3683f bundler: make --min-chunk-size effective on React apps and cheap; fix the sta...
  • 7c18e0d bundler: modulepreload the chunks a split browser import() depends on (#41143)
  • d2b71fb bun-types: type with { type } imports on TypeScript 7.1 (#41076)
  • 70736fd webview: stop close() and browser death from raising uncatchable unhandled re...
  • e8eaae9 bundler: bind property accesses on re-exported namespaces directly (#41009)
  • 41906a4 bun-types: keep generic process.removeListener and off signatures visible wit...
  • 1ab272b bun-types: defer Event and EventTarget to lib.dom when it is loaded (#40576)
  • c6f335f Bun.serve: HTTP/2 support via http2: true (#40137)
  • 1a50bfa bundler: with --splitting --target bun, require() of an ES module is a chunk ...
  • 52baef6 WebSocket client: pause()/resume(), working bufferedAmount, and a ServerWebSo...
  • 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

@dependabot
deps(api): bump the minor-and-patch group across 1 directory with 9 u…
dcc184c 
…pdates

Bumps the minor-and-patch group with 9 updates in the /api directory:

| Package | From | To |
| --- | --- | --- |
| [axios](https://github.com/axios/axios) | `1.18.1` | `1.20.0` |
| [dayjs](https://github.com/iamkun/dayjs) | `1.11.21` | `1.11.23` |
| [exiftool-vendored](https://github.com/photostructure/exiftool-vendored.js) | `37.0.0` | `37.2.0` |
| [fs-extra](https://github.com/jprichardson/node-fs-extra) | `11.3.6` | `11.4.0` |
| [i18next-http-middleware](https://github.com/i18next/i18next-http-middleware) | `3.9.7` | `3.9.8` |
| [posthog-node](https://github.com/PostHog/posthog-js/tree/HEAD/packages/node) | `5.45.2` | `5.51.6` |
| [pretty-bytes](https://github.com/sindresorhus/pretty-bytes) | `7.1.1` | `7.1.3` |
| [@types/bun](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/bun) | `1.3.14` | `1.4.0` |
| [bun-types](https://github.com/oven-sh/bun/tree/HEAD/packages/bun-types) | `1.3.14` | `1.4.1` |



Updates `axios` from 1.18.1 to 1.20.0
- [Release notes](https://github.com/axios/axios/releases)
- [Changelog](https://github.com/axios/axios/blob/v1.x/CHANGELOG.md)
- [Commits](axios/axios@v1.18.1...v1.20.0)

Updates `dayjs` from 1.11.21 to 1.11.23
- [Release notes](https://github.com/iamkun/dayjs/releases)
- [Changelog](https://github.com/iamkun/dayjs/blob/v1.11.23/CHANGELOG.md)
- [Commits](iamkun/dayjs@v1.11.21...v1.11.23)

Updates `exiftool-vendored` from 37.0.0 to 37.2.0
- [Release notes](https://github.com/photostructure/exiftool-vendored.js/releases)
- [Changelog](https://github.com/photostructure/exiftool-vendored.js/blob/main/CHANGELOG.md)
- [Commits](photostructure/exiftool-vendored.js@37.0.0...37.2.0)

Updates `fs-extra` from 11.3.6 to 11.4.0
- [Changelog](https://github.com/jprichardson/node-fs-extra/blob/master/CHANGELOG.md)
- [Commits](jprichardson/node-fs-extra@11.3.6...11.4.0)

Updates `i18next-http-middleware` from 3.9.7 to 3.9.8
- [Changelog](https://github.com/i18next/i18next-http-middleware/blob/master/CHANGELOG.md)
- [Commits](i18next/i18next-http-middleware@v3.9.7...v3.9.8)

Updates `posthog-node` from 5.45.2 to 5.51.6
- [Release notes](https://github.com/PostHog/posthog-js/releases)
- [Changelog](https://github.com/PostHog/posthog-js/blob/main/packages/node/CHANGELOG.md)
- [Commits](https://github.com/PostHog/posthog-js/commits/posthog-node@5.51.6/packages/node)

Updates `pretty-bytes` from 7.1.1 to 7.1.3
- [Release notes](https://github.com/sindresorhus/pretty-bytes/releases)
- [Commits](sindresorhus/pretty-bytes@v7.1.1...v7.1.3)

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

Updates `bun-types` from 1.3.14 to 1.4.1
- [Release notes](https://github.com/oven-sh/bun/releases)
- [Commits](https://github.com/oven-sh/bun/commits/bun-v1.4.1/packages/bun-types)

---
updated-dependencies:
- dependency-name: axios
  dependency-version: 1.20.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: dayjs
  dependency-version: 1.11.23
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: exiftool-vendored
  dependency-version: 37.2.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: fs-extra
  dependency-version: 11.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: i18next-http-middleware
  dependency-version: 3.9.8
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: posthog-node
  dependency-version: 5.51.6
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: pretty-bytes
  dependency-version: 7.1.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: minor-and-patch
- dependency-name: "@types/bun"
  dependency-version: 1.4.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
- dependency-name: bun-types
  dependency-version: 1.4.1
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: minor-and-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Sep 7, 2026
@dependabot @github

dependabot Bot commented on behalf of github Sep 14, 2026

Copy link
Copy Markdown
Author

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

@dependabot dependabot Bot closed this Sep 14, 2026
@dependabot
dependabot Bot deleted the dependabot/bun/api/minor-and-patch-6a6b9b051a branch September 14, 2026 12:12
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

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

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants