Skip to content

feat(deps): update dependency aqua:kubecolor/kubecolor ( 0.5.3 → 0.7.1 ) - #1417

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/aqua-kubecolor-kubecolor-0.x
Open

feat(deps): update dependency aqua:kubecolor/kubecolor ( 0.5.3 → 0.7.1 )#1417
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/aqua-kubecolor-kubecolor-0.x

Conversation

@renovate

@renovate renovate Bot commented Aug 29, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
aqua:kubecolor/kubecolor tools minor 0.5.3 → 0.7.1

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Release Notes

kubecolor/kubecolor (aqua:kubecolor/kubecolor)

v0.7.1

Compare Source

Re-release of v0.7.0, as our CI/CD for releasing DEB & RPM packages was disabled

v0.7.0

Compare Source

Kubecolor has been getting a big influx of LLM PRs. Some good, some bad. Interesting times now that even small projects like kubecolor gets bombarded. Not to be too negative. Some clearly AI-generated PRs do bring value, and we of course thourougly review each PR. Kubecolor has not turned into slop. While we maintainers do not use LLMs, some outside contributors do. So to be clear: kubecolor v0.7.0 and beyond will contain some AI-generated code. If you have a personal strict no-AI policy, then you will want to stick to using v0.6.0.

What's Changed

  • logscan: add support for Ruby-style :key=>value log format by @​sinashahoveisi in #​341

    Logs with :key=>value syntax, commonly found in e.g Ruby logs and some Elastic products like Logstash, are now supported and get appropriate coloring:
    Before Screenshot_20260824_200705
    After Screenshot_20260824_200715

  • fix: handle negative JSON numbers by @​Vaibhav-C-S in #​339

    Before After
    Screenshot_20260824_184411 Screenshot_20260824_184353

  • Add support for kubectl apply edit-last-applied by @​utafrali in #​318

    Command Before After
    edit-last-applied Tried to parse the output to colorize it. But if the command launched an editor (e.g nano, vim, hx) then the terminal output got messed up kubecolor now skips trying to parse the output so your terminal-based editor works correctly, at the cost of the output not getting colorized.
    view-last-applied Screenshot_20260824_185527 Screenshot_20260824_185518
    set-last-applied Screenshot_20260824_185549 Screenshot_20260824_185640

  • feat: age-based coloring for kubectl get via duration thresholds by @​tenitski in #​360

    By using the KUBECOLOR_OBJ_FRESH environment variable, you could tell kubecolor to render AGE column values with different colors depending on if a row is considered "fresh" or not.

    # previously:
export KUBECOLOR_OBJ_FRESH="30h"
export KUBECOLOR_THEME_DATA_DURATIONFRESH="yellow"

    Before it was a "fresh or not fresh", but kubecolor now supports more levels of "freshness". For example:

    # new in v0.7.0:
export KUBECOLOR_OBJ_FRESH="30m/2h/1d/30d/10y"
export KUBECOLOR_THEME_DATA_DURATIONFRESH="hiblue/himagenta/yellow/white/hired"

    which would set:

    • age below 30min: use hiblue coloring
    • age between 30min - 2h: use himagenta coloring
    • age between 2h - 1 day (24h): use yellow coloring
    • age between 1 day - 30 days: use white coloring
    • age between 30 days - 10 years (10×365 days): use hired coloring
    • age above 10 years: use no special coloring
Fixes

  • fix: imply plain mode for interactive commands by @​terry-li-hm in #​346

    Kubecolor will now disable all coloring and just run the kubectl command as-is, giving kubectl raw access to the terminal, when using --interactive or -i flag.

    This is to avoid some bugs in kubecolor, such as when running kubectl delete pod my-pod --interactive. Previously, kubectl's promt of "Do you want to continue? (y/N)" was hidden until you pressed enter. But now the command will correctly show that promt, at the cost of not showing any colors in the output.

    To get colors and correct prompt output working would require a much bigger change. So this is an adequate middleground to keep kubectl's functionality intact.

  • fix(help): bracketed URLs lose their last character by @​VXNCXNX in #​354

Documentation
Other
Dependencies

New Contributors

Full Changelog: kubecolor/kubecolor@v0.6.0...v0.7.0

v0.6.0

Compare Source

What's Changed

Features

  • Colorize kubectl label & kubectl annotate by @​applejag in #​300

    Before After
    Screenshot_20260412_162302 Screenshot_20260412_162219

  • Colorize True/False bool status in kubectl get table output by @​tenitski in #​307

    Before After
    Screenshot_20260412_162616 Screenshot_20260412_162640

  • Improve 'executable not found' error by @​applejag in #​299

    Makes the error easier to understand.

    Before:

    $ kubecolor get pods
[kubecolor] [ERROR] exec: "kubectl": executable file not found in $PATH

    After:

    $ kubecolor get pods
[kubecolor] [ERROR] exec: "kubectl": executable file not found in $PATH; kubectl must be installed to use kubecolor
Fixes

  • Increase max line length from 65 kB to 1.5 MB by @​applejag in #​297

    Before this fix, kubecolor would freeze when it tried to parse a line that was too long. But with this buffer size increase you should now be able to use kubecolor without it freezing.

    In short, this fixes:

    • Running kubecolor get secret -o yaml on a secret with a really big value, such as Helm release secrets
    • Running kubecolor logs on a pod that had a really big log line

    In addition, if kubecolor tries to read a line that's still too long (more than 1.5 MB now), it will now error out instead of freezing.

    The size limit was chosen based on the maximum Secret and ConfigMap value size, rounded up a bit to account for the size increase of base64 encoding and any other formatting like indentation and key names.

  • Always use the custom version printer by @​applejag in #​298

    Before After
    Screenshot_20260412_162732 Screenshot_20260412_16; kubectl must be installed to use kubecolor3114

    This did not work before becase kubecolor runs kubectl behind the scenes, reads its output, parses it, and adds in the coloring. And with the kubectl version subcommand it also injects kubecolor's own version into the output.

    But when kubecolor's output is not a terminal, such as when piping it through cat, then as an optimization kubecolor just handed its stdout over to kubectl, so kubecolor has no way of seeing or modifying the output.

    The fix was to still wrap kubectl's output when being piped, if (and only if) the subcommand used is kubectl version.

    You could always also get the kubecolor version using kubecolor --kubecolor-version. But now it behaves more predictable when piping.

Other
Dependencies

New Contributors

Full Changelog: kubecolor/kubecolor@v0.5.3...v0.6.0

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "every weekend"
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the type/minor label Aug 29, 2026
@chrtol-konflate

chrtol-konflate Bot commented Aug 29, 2026 •
edited
Loading

Copy link
Copy Markdown

konflate — summary

Note

✅ No rendered changes.

View the full rendered diff →

konflate · rendered 65bbf0a · advisory, not a gate

@renovate
renovate Bot force-pushed the renovate/aqua-kubecolor-kubecolor-0.x branch from 704ba1a to 65bbf0a Compare September 4, 2026 13:09
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

type/minor

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants