Skip to content
← Back to activity

Solution skill

Latest release doesn't include binaries?

Version 2Sign in to save

Complete solution

Shows how to fix latest release doesn't include binaries?. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

[andrewsomething (maintainer)]: The v1.136.0 release was missing its prebuilt binaries because of a regression in the release pipeline, so the release was deleted. If your doctl install or the action-doctl GitHub Action breaks looking for 1.136.0 binaries, move to v1.137.0 or newer.

Steps

  1. [andrewsomething (maintainer)]: The v1.136.0 release was missing its prebuilt binaries because of a regression in the release pipeline, so the release was deleted. If your doctl install or the action-doctl GitHub Action breaks looking for 1.136.0 binaries, move to v1.137.0 or newer. The action side was also fixed to not break when binaries are missing.

When to use

You are seeing this: The latest release doesn't include the prebuilt binaries usually included which for me is breaking the doctl github action which seems to expect those binaries to exist - for ref this is the debug output from my github action: Use this skill when you run into "Latest release doesn't include binaries?".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: v1.136.0, 1.136.0, v1.137.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/digitalocean/doctl/releases/tag/v1.136.0

Evidence

In gh:digitalocean/doctl#1733 (https://github.com/digitalocean/doctl/issues/1733), the reporter ran into this: The latest release doesn't include the prebuilt binaries usually included which for me is breaking the doctl github action which seems to expect those binaries to exist - for ref this is the debug output from my github action: The verified resolution: [andrewsomething (maintainer)]: The v1.136.0 release was missing its prebuilt binaries because of a regression in the release pipeline, so the release was deleted. If your doctl install or the action-doctl GitHub Action breaks looking for 1.136.0 binaries, move to v1.137.0 or newer. The action side was also fixed to not break when binaries are missing.

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_qpdhT45GHJeNkCpqVpzqjA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Latest release doesn&#39;t include binaries? <span>— Vectle</span></a>