fix(deps): update dependency chalk to v5

[renovate]

This PR contains the following updates:

Package	Type	Update	Change	OpenSSF
chalk	dependencies	major	^4.0.0 -> ^5.0.0

---

Release Notes

chalk/chalk (chalk)

v5.3.0

Compare Source

• Add sideEffects field to package.json 5aafc0a
• Add support for Gitea Actions (#​603) 29b8569

v5.2.0

Compare Source

• Improve Deno compatibility (#​579) 7443e9f
• Detect true-color support for GitHub Actions (#​579) 7443e9f
• Detect true-color support for Kitty terminal (#​579) 7443e9f
• Fix test for Azure DevOps environment (#​579) 7443e9f

v5.1.2

Compare Source

• Fix exported styles names (#​569) a34bcf6

v5.1.1

Compare Source

• Improved the names of exports introduced in 5.1.0 (#​567) 6e0df05
  • We of course preserved the old names.

v5.1.0

Compare Source

• Expose style names (#​566) d7d7571

v5.0.1

Compare Source

• Add main field to package.json for backwards compatibility with some developer tools 85f7e96

v5.0.0

Compare Source

Breaking

• This package is now pure ESM. Please read this.
  • If you use TypeScript, you need to use TypeScript 4.7 or later. Why.
  • If you use a bundler, make sure it supports ESM and that you have correctly configured it for ESM.
  • The Chalk issue tracker is not a support channel for your favorite build/bundler tool.
  • It's totally fine to stay on Chalk v4. It's been stable for years.
• Require Node.js 12.20 fa16f4e
• Move some properties off the default export to individual named exports:
  • chalk.Instance → Chalk
  • chalk.supportsColor → supportsColor
  • chalk.stderr → chalkStderr
  • chalk.stderr.supportsColor → supportsColorStderr
• Remove .keyword(), .hsl(), .hsv(), .hwb(), and .ansi() coloring methods (#​433) 4cf2e40
  • These were not commonly used and added a lot of bloat to Chalk. You can achieve the same by using the color-convert package.
• The tagged template literal support moved into a separate package: chalk-template (#​524) c987c61

-import chalk from 'chalk';
+import chalkTemplate from 'chalk-template';

-chalk`2 + 3 = {bold ${2 + 3}}`;
+chalkTemplate`2 + 3 = {bold ${2 + 3}}`;

Improvements

• Bundle dependencies 04fdbd6
  • This means Chalk no longer has any dependencies 🎉
• The install size is less than half of v4.
• Add overline style (#​433) 4cf2e40
• Preserve function prototype methods (#​434) 0fba91b

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml

Scope: all 14 projects
Progress: resolved 1, reused 0, downloaded 0, added 0
undefined
/tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace/node1:
 ERR_PNPM_FETCH_404  GET https://registry.npmjs.org/anotherExternal: Not Found - 404

This error happened while installing a direct dependency of /tmp/renovate/repos/github/stainless-api/release-please/test/fixtures/plugins/node-workspace/node1

anotherExternal is not in the npm registry, or you have no permission to fetch it.

No authorization header was set for the request.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 5.x releases. But if you manually upgrade to 5.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.