Skip to content

build(deps): bump the production-dependencies group across 1 directory with 6 updates - #58

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-9ad44178ec
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/production-dependencies-9ad44178ec

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 10, 2026

Copy link
Copy Markdown

Bumps the production-dependencies group with 6 updates in the / directory:

Package From To
@clack/prompts 1.8.0 1.8.1
ansis 4.3.1 4.5.0
p-limit 7.3.2 7.3.3
semver 7.8.5 7.8.6
undici 8.10.2 8.12.4
yaml 2.9.0 2.9.1

Updates @clack/prompts from 1.8.0 to 1.8.1

Release notes

Sourced from @​clack/prompts's releases.

@​clack/prompts@​1.8.1

Patch Changes

  • 8bd9129 Thanks @​gameroman! - Return type for prompts now correctly specifies CANCEL_SYMBOL instead of symbol

  • Updated dependencies [8bd9129]:

    • @​clack/core@​1.5.1
Changelog

Sourced from @​clack/prompts's changelog.

1.8.1

Patch Changes

  • 8bd9129 Thanks @​gameroman! - Return type for prompts now correctly specifies CANCEL_SYMBOL instead of symbol

  • Updated dependencies [8bd9129]:

    • @​clack/core@​1.5.1
Commits

Updates ansis from 4.3.1 to 4.5.0

Release notes

Sourced from ansis's releases.

v4.5.0

Bug Fixes

  • color-support: prevent colors in piped or redirected output when COLORTERM is set, #54
  • color-support: detect the color level for FORCE_COLOR=true and --color in non-TTY output

Behavior

Colors are enabled only for a TTY, CI, and the PM2 and Next.js runtimes. Output to a pipe or a file has no colors, even when COLORTERM is set. COLORTERM sets only the color level.

FORCE_COLOR=true, FORCE_COLOR= and --color in non-TTY output now detect the level from the environment (COLORTERM, TERM, Windows) instead of always using 16 colors.

Upgrade note

If your tests relied on COLORTERM to get colors, set FORCE_COLOR instead, for example FORCE_COLOR=3 npm test. See Testing.

Full Changelog: webdiscus/ansis@v4.4.0...v4.5.0

v4.4.0

Bug fixes

1. TERM=dumb now disables colors during auto-detection

Ansis now treats TERM=dumb as no color before applying COLORTERM, CI detection, PM2, Next.js runtime detection, and platform-specific defaults, #49.

Before, COLORTERM=truecolor or other later auto-detection checks could still enable colors even when the environment reported TERM=dumb. This could produce visible ANSI escape codes in environments such as Emacs M-x compile.

COLORTERM remains a color capability hint. FORCE_COLOR keeps the highest priority and can still explicitly enable colors.

Use case v4.3.1 v4.4.0 Notes
TERM=dumb ✅ may allow colors * ❌ no color TERM=dumb now has higher priority in autoDetectLevel.
TERM=dumb + COLORTERM=truecolor ✅ allow colors ❌ no color COLORTERM no longer overrides TERM=dumb.
TERM=dumb + CI ✅ allow colors ❌ no color CI detection runs after TERM=dumb.
TERM=dumb + PM2 ✅ may allow colors * ❌ no color PM2 detection runs after TERM=dumb.
TERM=dumb + Next.js runtime ✅ may allow colors * ❌ no color Next.js detection runs after TERM=dumb.
COLORTERM without TERM=dumb ✅ allow colors ✅ allow colors Unchanged.
CI without TERM=dumb ✅ allow colors ✅ allow colors Unchanged.
PM2 without TERM=dumb ✅ allow colors ✅ allow colors Unchanged.
Next.js without TERM=dumb ✅ allow colors ✅ allow colors Unchanged.

* - Depends on additional conditions.

Tests and CI

  • Added regression coverage for TERM=dumb with inherited COLORTERM=truecolor.
  • Added coverage for PM2 and Next.js runtime behavior where stdout.isTTY is not exposed.
  • Added a manual color checker. Run npm run color-checker to print the environment values used by color detection and visually inspect ANSI 16, ANSI 256, and Truecolor rendering.
  • Updated Deno CI to test Deno 2.3+ and the current LTS. Runtime compatibility with Deno 2.0-2.2 remains supported.
Changelog

Sourced from ansis's changelog.

4.5.0 (2026-11-01)

  • fix(color-support): prevent colors in piped or redirected output when COLORTERM is set, #54.

    Before: Ansis used to check COLORTERM before checking stdout. Apps can inherit COLORTERM from the parent terminal even when stdout goes to a pipe or file. This could add ANSI codes to that output.

    After: Ansis now checks the output environment first. COLORTERM only helps choose the color level when color output is enabled.

    Color output in supported non-TTY environments such as CI, PM2, and Next.js edge still works.

    Auto-detection behavior changes after the fix

    Environment Before After
    stdout is a TTY, COLORTERM=truecolor ✅ Level 3 ✅ Level 3
    stdout to a pipe or file, COLORTERM=truecolor ✅ Level 3 ❌ Level 0
    PM2 or Next.js edge, COLORTERM=truecolor ✅ Level 3 ✅ Level 3

    To explicitly enable colors in non-TTY environments, use FORCE_COLOR.

  • fix(color-support): detect the color level for FORCE_COLOR=true and --color in non-TTY output.

    Before: With FORCE_COLOR=true or --color, Ansis ignored Windows and TERM for a pipe or file. Without COLORTERM, it used 16 colors, even on Windows or with TERM=xterm-256color.

    After: Ansis uses Windows and TERM for any output when colors are enabled this way.

    Environment Before After
    FORCE_COLOR=true or --color, pipe or file, Windows ✅ Level 1 ✅ Level 3
    FORCE_COLOR=true or --color, pipe or file, TERM=xterm-256color ✅ Level 1 ✅ Level 2
    FORCE_COLOR=true or --color, pipe or file, COLORTERM=truecolor ✅ Level 3 ✅ Level 3

    FORCE_COLOR=1, 2 and 3 set the level directly. They work as before.

4.4.0 (2026-09-13)

  • fix(color-support): treat TERM=dumb as no color before applying COLORTERM, #49.

    COLORTERM is a color level hint. When TERM=dumb, Ansis now disables ANSI color output even if color environment variables such as COLORTERM=truecolor were inherited from a parent process (e.g. in Emacs M-x compile).

    FORCE_COLOR keeps the highest priority and can still explicitly enable colors.

    Auto-detection behavior changes after the fix

... (truncated)

Commits
  • 86cef44 fix(color-support): no colors in piped output when COLORTERM is set, #54
  • 670e062 docs: add description of TERM env variable
  • d5b557c Merge pull request #51 from webdiscus/next
  • a724646 fix(color-support): treat TERM=dumb as no color before applying COLORTERM...
  • 7985966 Merge pull request #48 from PingouinFerreux/fix/star-history-chart
  • 7cf8889 docs: fix broken star history chart in readme
  • 678da3a test: add tests to to control level in files usied ansis
  • See full diff in compare view

Updates p-limit from 7.3.2 to 7.3.3

Release notes

Sourced from p-limit's releases.

v7.3.3

  • Fix unhandled rejections in limit.map() when the iterable throws 9df0d27

sindresorhus/p-limit@v7.3.2...v7.3.3

Commits

Updates semver from 7.8.5 to 7.8.6

Release notes

Sourced from semver's releases.

v7.8.6

7.8.6 (2026-11-02)

Bug Fixes

Chores

Changelog

Sourced from semver's changelog.

7.8.6 (2026-11-02)

Bug Fixes

Chores

Commits

Updates undici from 8.10.2 to 8.12.4

Release notes

Sourced from undici's releases.

v8.12.4

⚠️ Security Fixes

This release fixes six vulnerabilities.

CVE-2026-116592 / GHSA-mqg3-3v4r-cm32 (high)

Undici 8.12.2 and 8.12.3 could cache the final response from a redirect chain under the original request key without applying the origin, cache policy, freshness, or Vary requirements of every intermediate hop. This could poison a cache or expose one user's response to another user. The fix validates every redirect hop, combines their Vary fields, limits freshness and stale serving to the most restrictive hop, and invalidates persistent SQLite entries written by vulnerable releases.

CVE-2026-120474 / GHSA-7xg3-fphp-28hg (medium)

A shared cache used with compose(redirect(), cache()) could store a credential-dependent response from a same-origin redirect under the original URL. A later authenticated or unauthenticated request could then receive another user's response. Redirected requests carrying Authorization, Cookie, or Proxy-Authorization are no longer stored under the original alias key.

CVE-2026-116630 / GHSA-5rm8-gv32-r954 (medium)

A cross-origin redirect during cache revalidation could let a 304 Not Modified response from the redirect target validate a cached response from the original origin. Undici now checks that the revalidation target matches the cached URL and that any returned validator matches the stored representation before replaying the cached body.

CVE-2026-120415 / GHSA-9v6h-8rgp-m69f (medium)

The redirect interceptor did not strip credentials correctly when request headers were supplied as an array of [name, value] pairs. With a header-normalizing interceptor outside redirect(), credentials could be sent to a cross-origin redirect target. Undici now handles both tuple arrays and flat header arrays when removing sensitive headers.

CVE-2026-120222 / GHSA-3g9m-rv3r-w5w2 (medium)

A downstream handler exception during cache replay could escape as an uncaught exception or unhandled promise rejection and terminate the process. This included dump size-limit failures, excessive Content-Encoding values in decompress, asynchronous cache-store failures, and cached-body replay after a 304. These failures are now reported as request errors.

CVE-2026-120423 / GHSA-r4pc-4jcp-7pqc (medium)

fetch() could skip Subresource Integrity verification when valid integrity metadata was separated or surrounded by ASCII whitespace other than a space, including a horizontal tab. Integrity metadata is now split on all ASCII whitespace before SHA-256, SHA-384, or SHA-512 verification.

What's Changed

... (truncated)

Commits
  • 779ee3e Bumped v8.12.4 (#6162)
  • 10fa822 docs: remove security release notes
  • 6228fc5 docs: add security release notes
  • 1dd2657 test(cache): align redirect caching with hop policy
  • 8ea1d61 fix(cache): detect an actual redirect, not a plain revalidation
  • 4257261 test(cache): cover credentialed revalidation refresh
  • aa7ccff fix(cache): treat proxy-authorization as a credential when caching redirects
  • 8cf5ce1 test(cache): cover proxy-authorization credential on same-origin redirect
  • 26c42c2 fix(cache): do not cache credential-bearing same-origin redirects under the a...
  • e958661 test: cover decompress too-many-content-encodings throw on async cache replay
  • Additional commits viewable in compare view

Updates yaml from 2.9.0 to 2.9.1

Release notes

Sourced from yaml's releases.

v2.9.1

  • Limit recursive merge aliases (#685, #713)
  • Simplify line unfolding during quoted string parsing (#714)
Commits

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

…y with 6 updates

Bumps the production-dependencies group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@clack/prompts](https://github.com/bombshell-dev/clack/tree/HEAD/packages/prompts) | `1.8.0` | `1.8.1` |
| [ansis](https://github.com/webdiscus/ansis) | `4.3.1` | `4.5.0` |
| [p-limit](https://github.com/sindresorhus/p-limit) | `7.3.2` | `7.3.3` |
| [semver](https://github.com/npm/node-semver) | `7.8.5` | `7.8.6` |
| [undici](https://github.com/nodejs/undici) | `8.10.2` | `8.12.4` |
| [yaml](https://github.com/eemeli/yaml) | `2.9.0` | `2.9.1` |



Updates `@clack/prompts` from 1.8.0 to 1.8.1
- [Release notes](https://github.com/bombshell-dev/clack/releases)
- [Changelog](https://github.com/bombshell-dev/clack/blob/main/packages/prompts/CHANGELOG.md)
- [Commits](https://github.com/bombshell-dev/clack/commits/@clack/prompts@1.8.1/packages/prompts)

Updates `ansis` from 4.3.1 to 4.5.0
- [Release notes](https://github.com/webdiscus/ansis/releases)
- [Changelog](https://github.com/webdiscus/ansis/blob/master/CHANGELOG.md)
- [Commits](webdiscus/ansis@v4.3.1...v4.5.0)

Updates `p-limit` from 7.3.2 to 7.3.3
- [Release notes](https://github.com/sindresorhus/p-limit/releases)
- [Commits](sindresorhus/p-limit@v7.3.2...v7.3.3)

Updates `semver` from 7.8.5 to 7.8.6
- [Release notes](https://github.com/npm/node-semver/releases)
- [Changelog](https://github.com/npm/node-semver/blob/main/CHANGELOG.md)
- [Commits](npm/node-semver@v7.8.5...v7.8.6)

Updates `undici` from 8.10.2 to 8.12.4
- [Release notes](https://github.com/nodejs/undici/releases)
- [Commits](nodejs/undici@v8.10.2...v8.12.4)

Updates `yaml` from 2.9.0 to 2.9.1
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](eemeli/yaml@v2.9.0...v2.9.1)

---
updated-dependencies:
- dependency-name: "@clack/prompts"
  dependency-version: 1.8.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: ansis
  dependency-version: 4.5.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: p-limit
  dependency-version: 7.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: semver
  dependency-version: 7.8.6
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: undici
  dependency-version: 8.12.4
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: yaml
  dependency-version: 2.9.1
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot requested a review from vcode-sh as a code owner November 10, 2026 19:06
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 10, 2026
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants