🌱 Bump github.com/fatih/color from 1.14.1 to 1.15.0

[dependabot]

Bumps github.com/fatih/color from 1.14.1 to 1.15.0.

Release notes

Sourced from github.com/fatih/color's releases.

v1.15.0

What's Changed

• windows: enable virtual terminal processing, fixes #169 by @​martinlindhe in fatih/color#186
• ci: update dependencies by @​fatih in fatih/color#191
• Bump golang.org/x/sys from 0.5.0 to 0.6.0 by @​dependabot in fatih/color#189
• Refactor color_windows.go by @​pellared in fatih/color#188

New Contributors

• @​martinlindhe made their first contribution in fatih/color#186

Full Changelog: fatih/color@v1.14.1...v1.15.0

Commits

• 12126ed Merge pull request #188 from pellared/patch-1
• 770038b Merge branch 'main' into patch-1
• c5d9a2b Merge pull request #189 from fatih/dependabot/go_modules/golang.org/x/sys-0.6.0
• 1ceb746 Bump golang.org/x/sys from 0.5.0 to 0.6.0
• 66a1b89 Merge pull request #191 from fatih/update-ci-deps
• 3228f5a ci: update dependencies
• 0226ec9 Refactor color_windows.go
• d080a5b Merge pull request #186 from martinlindhe/main
• 02ab2ea windows: enable virtual terminal processing, fixes #169
• See full diff 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[spectro-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: dependabot[bot]
To complete the pull request process, please assign
You can assign the PR to them by writing /assign in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[spectro-prow]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a spectrocloud member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[spectro-prow]

Hi @dependabot[bot]. Thanks for your PR.

I'm waiting for a spectrocloud member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.