Skip to content

chore(deps): update dependency chalk to v6 #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
renovate wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −1
Open

chore(deps): update dependency chalk to v6 #27

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@
},
"dependencies": {
"@wave-av/sdk": "^2.0.11",
"chalk": "^5.4.1",
"chalk": "^6.0.0",

@devin-ai-integration devin-ai-integration Bot Aug 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔴 CLI can break for users on Node 18 after the color-library upgrade

The color library is upgraded to a major version that no longer supports Node 18 ("chalk": "^6.0.0" at package.json:59) while the package still advertises Node 18 as supported, so users on Node 18 get engine warnings and a CLI that can fail to run.
Impact: People running the CLI on Node 18 may see install-time engine errors or runtime failures instead of a working tool.

Engine range mismatch between dependency and declared support

package.json:49-51 still declares "engines": { "node": ">=18.0.0" }, but chalk 6 dropped support for Node 18 (its own engines requires Node 20+). With npm's default engine-strict=false, installation proceeds with an EBADENGINE warning, and any use of chalk (used broadly, e.g. src/commands/stream/index.ts:2) risks failing on Node 18. Either raise the package's engines.node (and CI/docs) to match chalk 6, or stay on chalk 5.

Prompt for agents 
package.json bumps chalk to ^6.0.0, whose own engines field requires Node 20+, while this package still declares engines.node ">=18.0.0" (package.json:49-51). Decide whether to raise the supported Node floor (updating engines, README/docs, and any CI node-version matrix) or to keep chalk on the 5.x line so Node 18 remains genuinely supported.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@devin-ai-integration devin-ai-integration Bot Aug 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changelog not updated for the dependency upgrade

The upgrade of the color library ("chalk": "^6.0.0" at package.json:59) ships without any note added to the changelog's Unreleased section, so the repo's contribution rule about recording user-facing changes is not met.
Impact: Users and maintainers get no record that the tool's supported runtime/dependencies changed.

Repo rule reference

AGENTS.md requires: "Conventional Commit titles; update CHANGELOG.md (Unreleased) for user-facing changes." The ## [Unreleased] section in CHANGELOG.md:7 is still empty, while this change raises the effective minimum Node version for end users.

Prompt for agents 
Per AGENTS.md, user-facing changes must be recorded under the Unreleased heading in CHANGELOG.md. Add an entry describing the chalk 6 upgrade and any resulting change in the minimum supported Node version.
Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

@devin-ai-integration devin-ai-integration Bot Aug 16, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔍 chalk API surface used is limited to stable helpers

All usage in src/ is limited to chalk.green/red/yellow/bold/dim/cyan-style helpers (e.g. src/commands/stream/index.ts:23, src/commands/doctor/index.ts:115), which remain unchanged in chalk 6, so no code changes are required beyond the runtime/engine consideration. There is no lockfile committed, so the actual resolved chalk version (and its engine constraint) cannot be verified from the repo — worth confirming during install/CI.

Open in Devin Review

Was this helpful? React with 👍 or 👎 to provide feedback.

"cli-table3": "^0.6.5",
"commander": "^13.1.0",
"conf": "^13.1.0",
Expand Down
Loading