I'm not sure why, but this step is failing nearly every time on at least one runner.

No idea what happened in the CI here, php cs fixer hallucinated?

Sigh. This is why I like to keep downloading and building completely separate. It's also one of the things I don't like about Go: it always requires a network connection to GitHub.

I think it's time to change this approach to getting releases. Issues with accessing the GitHub API are the most common download issues we encounter.

No idea what happened in the CI here, php cs fixer hallucinated?

Nope. The cs fixer just has another minor update that introduced new rules. I've updated in another branch.

Sigh. This is why I like to keep downloading and building completely separate. It's also one of the things I don't like about Go: it always requires a network connection to GitHub.

Technically we can pull everything in the download phase and use go build manually. It's just rather annoying to do - xcaddy doesn't fail with the download too often (not once in CI yet).

We can add frankenphp as a downloader source and store the version, though. What do you think?

We can add frankenphp as a downloader source and store the version, though. What do you think?

Initially I want this way, but it will be more redundant downloads for building non-frankenphp sapis. And I remember we discussed it before, the xcaddy seems no way to download without building.

Only for this PR related thing: I think we could fetch frankenphp version after go-xcaddy package installed.