GitHub API parsing sometimes fails due to minified JSON response

[luminosity-design]

Creating a bug report/issue

• I have searched the existing open and closed issues

Required Information

• DietPi version
  G_DIETPI_VERSION_CORE=10
  G_DIETPI_VERSION_SUB=1
  G_DIETPI_VERSION_RC=2
  G_GITBRANCH='master'
  G_GITOWNER='MichaIng'
• Distro version | trixie
• Kernel version | Linux RockPi 6.18.13-current-rockchip64 #1 SMP PREEMPT Thu Feb 19 15:31:37 UTC 2026 aarch64 GNU/Linux
• SBC model | ROCK 4 (aarch64)
• Power supply used | Standard
• SD card used | Samsung EVO

Additional Information (if applicable)

• Software title | Uptime Kuma
• Was the software title installed freshly or updated/migrated? Updated

Steps to reproduce

1. Run dietpi-software reinstall 176

Expected behaviour

• Latest version of 2.2.1 installed.

Actual behaviour

• Version 2.1.3 is installed

Extra details

[FAILED] DietPi-Software | Automatic latest Uptime Kuma version detection failed. Version "2.1.3" will be installed as fallback, but a newer version might be available. Please report this at: https://github.com/MichaIng/DietPi/issues

[Joulinar]

We are currently aware of some difficulties in finding out the current versions via GitHub API. For whatever reason, this is not working reliably at the moment.

[MichaIng]

In our CI tonight it worked: https://github.com/MichaIng/DietPi/actions/runs/22887994904/job/66404946379#step:4:220

But yeah, we found this to happen in some cases, and it depends from where and when you access, probably some minification that happens (unexpectedly or intentionally for console tool requests) at some edge servers or so.

Does this request return a single huge line or a well ordered JSON on the console?

curl -sSfL 'https://api.github.com/repos/louislam/uptime-kuma/releases/latest'

Opposed to that, when you open it in browser, (with browser-side beautification disabled), you will most likely see a well ordered JSON: https://api.github.com/repos/louislam/uptime-kuma/releases/latest

I need to check with GitHub community whether this is intended and API responses will come minified (when using certain user-agents or so), or whether it is not intentional.

[luminosity-design]

The reinstall worked this time.

Before reinstalling I did run the curl command and it returned a single line.

[MichaIng]

Maybe someone knows more: https://github.com/orgs/community/discussions/189605
Anyway, #8013 provides a very small change to support both: single-line and multi-line output, without requiring additional tools like jq or a lengthy awk loop. Just needs to be applied throughout the whole script as well as the CI which updates the fallback URLs.

[MichaIng]

Okay, so this behavior is intended, so we need to apply the change throughout all GitHub API calls.