Describe the bug
Logs with color output are scrambled with the color-codes, making them unreadable without piping them into another process to either strip or display them properly.
Affected version
gh version 2.92.0 (2026-04-28)
https://github.com/cli/cli/releases/tag/v2.92.0
Steps to reproduce the behavior
Compare e.g. this run in browser vs cli:
gh run view --log --job 73375451399 --repo cli/cli
Expected vs actual behavior
I am not sure when this broke, but I was able to see colors in the logs last month, so I presume something related to fixing this exploit prevents processing the colors.
I wouldn't mind it so much if the colors were just stripped out entirely, but as it currently is the logs are entirely unreadable, and I have to either parse them separately or switch to the browser to view them.
Logs
browser:
CLI:
linux UNKNOWN STEP 2026-04-28T11:28:31.3204244Z goreleaser release -f .goreleaser.generated.yml --clean --skip validate,publish,announce --release-notes=$TMPDIR/tmp.INkam3fMd4
linux UNKNOWN STEP 2026-04-28T11:28:31.3461443Z ^[[1;93m •^[[m ^[[1;93mskipping announce, publish, and validate...^[[m
linux UNKNOWN STEP 2026-04-28T11:28:31.3474990Z ^[[1;94m •^[[m ^[[1mcleaning distribution directory^[[m
linux UNKNOWN STEP 2026-04-28T11:28:31.3476125Z ^[[1;94m •^[[m ^[[1mloading environment variables^[[m
linux UNKNOWN STEP 2026-04-28T11:28:31.3476857Z ^[[1;94m •^[[m ^[[1mgetting and validating git state^[[m
linux UNKNOWN STEP 2026-04-28T11:28:31.4504578Z ^[[1;93m •^[[m couldn't find any tags before "v2.92.0"
linux UNKNOWN STEP 2026-04-28T11:28:31.4600023Z ^[[1;94m •^[[m git state ^[[1;94mcommit^[[m=6c470f60803784e1558b626022677c53dccb6016 ^[[1;94mbranch^[[m=trunk ^[[1;94mcurrent_tag^[[m=v2.92.0 ^[[1;94mprevious_tag^[[m=<unknown> ^[[1;94mdirty^[[m=false
linux UNKNOWN STEP 2026-04-28T11:28:31.4601609Z ^[[1;93m •^[[m pipe skipped or partially skipped ^[[1;93mreason^[[m=validation is disabled
linux UNKNOWN STEP 2026-04-28T11:28:31.4602801Z ^[[1;94m •^[[m ^[[1mparsing tag^[[m
linux UNKNOWN STEP 2026-04-28T11:28:31.4603211Z ^[[1;94m •^[[m ^[[1msetting defaults^[[m
linux UNKNOWN STEP 2026-04-28T11:28:31.4659569Z ^[[1;94m •^[[m ^[[1mrunning before hooks^[[m
linux UNKNOWN STEP 2026-04-28T11:28:31.4660532Z ^[[1;94m •^[[m running ^[[1;94mhook^[[m= make manpages GH_VERSION=2.92.0
linux UNKNOWN STEP 2026-04-28T11:29:08.1828155Z ^[[1;94m •^[[m ^[[3;2mtook: 37s^[[m
linux UNKNOWN STEP 2026-04-28T11:29:08.1829407Z ^[[1;94m •^[[m running ^[[1;94mhook^[[m= make completions
linux UNKNOWN STEP 2026-04-28T11:29:55.2667728Z ^[[1;94m •^[[m ^[[3;2mtook: 47s^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2669277Z ^[[1;94m •^[[m running ^[[1;94mhook^[[m=echo pwsh '.\script\gen-winres.ps1' '2.92.0 (2026-04-28)' '2.92.0' '.\script\versioninfo.template.json' '.\cmd\gh\'
linux UNKNOWN STEP 2026-04-28T11:29:55.2689955Z ^[[1;94m •^[[m ^[[3;2mtook: 1m24s^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2690743Z ^[[1;94m •^[[m ^[[1mensuring distribution directory^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2694582Z ^[[1;94m •^[[m ^[[1msetting up metadata^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2695260Z ^[[1;94m •^[[m ^[[1mwriting release metadata^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2695909Z ^[[1;94m •^[[m ^[[1mloading go mod information^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2738141Z ^[[1;94m •^[[m ^[[1mbuild prerequisites^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2745495Z ^[[1;94m •^[[m ^[[1mbuilding binaries^[[m
linux UNKNOWN STEP 2026-04-28T11:29:55.2747899Z ^[[1;94m •^[[m building ^[[1;94mbinary^[[m=dist/linux_linux_arm_6/bin/gh
linux UNKNOWN STEP 2026-04-28T11:29:55.2748947Z ^[[1;94m •^[[m building ^[[1;94mbinary^[[m=dist/linux_linux_amd64_v1/bin/gh
linux UNKNOWN STEP 2026-04-28T11:29:55.2751040Z ^[[1;94m •^[[m running hook ^[[1;94mhook^[[m=bash ./script/licenses linux arm
linux UNKNOWN STEP 2026-04-28T11:29:55.2752526Z ^[[1;94m •^[[m running hook ^[[1;94mhook^[[m=bash ./script/licenses linux amd64
linux UNKNOWN STEP 2026-04-28T11:29:55.2760058Z ^[[1;94m •^[[m building ^[[1;94mbinary^[[m=dist/linux_linux_386_sse2/bin/gh
linux UNKNOWN STEP 2026-04-28T11:29:55.2785408Z ^[[1;94m •^[[m running hook ^[[1;94mhook^[[m=bash ./script/licenses linux 386
linux UNKNOWN STEP 2026-04-28T11:29:55.2788059Z ^[[1;94m •^[[m building ^[[1;94mbinary^[[m=dist/linux_linux_arm64_v8.0/bin/gh
linux UNKNOWN STEP 2026-04-28T11:29:55.2789481Z ^[[1;94m •^[[m running hook ^[[1;94mhook^[[m=bash ./script/licenses linux arm64
linux UNKNOWN STEP 2026-04-28T11:29:55.3316140Z go: downloading github.com/google/go-licenses/v2 v2.0.1
linux UNKNOWN STEP 2026-04-28T11:29:55.3332757Z go: downloading github.com/google/go-licenses/v2 v2.0.1
linux UNKNOWN STEP 2026-04-28T11:29:55.3373081Z go: downloading github.com/google/go-licenses/v2 v2.0.1
linux UNKNOWN STEP 2026-04-28T11:29:55.3399205Z go: downloading github.com/google/go-licenses/v2 v2.0.1
Describe the bug
Logs with color output are scrambled with the color-codes, making them unreadable without piping them into another process to either strip or display them properly.
Affected version
Steps to reproduce the behavior
Compare e.g. this run in browser vs cli:
Expected vs actual behavior
I am not sure when this broke, but I was able to see colors in the logs last month, so I presume something related to fixing this exploit prevents processing the colors.
I wouldn't mind it so much if the colors were just stripped out entirely, but as it currently is the logs are entirely unreadable, and I have to either parse them separately or switch to the browser to view them.
Logs
browser:
CLI: