Release `v0.71.1` (and `v0.71.0`, `v0.71.2`, `v0.71.3`) deleted — breaks pinned consumers

[IEvangelist]

Hi 👋 — we have CI pinned to v0.71.1 of gh-aw (via github/gh-aw-actions/setup-cli@…) and it started failing recently with Could not find a release of github/gh-aw for v0.71.1 and curl: (22) ... 404 for https://github.com/github/gh-aw/releases/download/v0.71.1/linux-amd64.

Confirmed via the GitHub API:

• Git tag v0.71.1 still exists.
• GET /repos/github/gh-aw/releases/tags/v0.71.1 returns 404.
• Same for v0.71.0, v0.71.2, and v0.71.3. The earliest surviving v0.71.x release is v0.71.4.

A previously-green build that succeeded with v0.71.1 started failing without any change on our side, so the release was deleted after publication.

Failing run: https://github.com/microsoft/aspire.dev/actions/runs/25472117492/job/74844702611?pr=530

Excerpt from the failing job:

[INFO] Using specified version: v0.71.1
[INFO] Attempting to install gh-aw using 'gh extension install'...
X Could not find a release of github/gh-aw for v0.71.1
[WARNING] gh extension install failed, falling back to manual installation...
X Could not find a release of github/gh-aw for v0.71.1
[INFO] Download URL: https://github.com/github/gh-aw/releases/download/v0.71.1/linux-amd64
...
curl: (22) The requested URL returned error: 404
[ERROR] Failed to download binary from https://github.com/github/gh-aw/releases/download/v0.71.1/linux-amd64 after 3 attempts

Questions

1. Was the deletion of v0.71.0–v0.71.3 intentional (e.g., yanked due to a critical bug)? If so, could the rationale please be documented somewhere consumers can find it (release notes, README, security advisory) so we know whether to upgrade or skip ahead?
2. Could deleted releases be republished — even as pre-releases — so existing pins continue to resolve? SHA-pinning a setup action with a specific version: input is the recommended supply-chain practice, and silently yanking the corresponding release artifacts breaks that contract for downstream consumers.
3. What is the recommended replacement for v0.71.1 — v0.71.4, v0.71.5, or something newer?

Thanks!

[pelikhan]

We discovered a billing issue with these versions that overbill users. This is not something we could patch or fix at the server level and we decided that breaking workflows was preferable that overbilling. We understand that this is a major inconvenience. We are looking into integrating controls and mitigations if this kind of issues occurs in the future. Meanwhile, you will want to upgrade to v0.71.4+, or back to 0.68.3.