Build the Intel macOS target on a runner that still exists - #33
Merged
Conversation
The v0.1.0 release never published. Three of the four build jobs finished in about a minute; the x86_64-apple-darwin job sat unassigned for hours and the publish job, which needs the whole matrix, waited behind it. With no release, `install.sh` resolved `releases/latest/download/drop-x86_64-unknown-linux-musl.tar.gz` to a 404 even though that artifact had built successfully. The cause is the runner label. `macos-13` began deprecation in September 2025 and was fully unsupported in December 2025, so a job requesting it is never assigned a runner. It queues indefinitely rather than failing, and `timeout-minutes` does not bound queueing, only execution — so nothing ever forced the run to end. `macos-15-intel` is GitHub's Intel replacement. It is available until August 2027, when x86_64 macOS support ends and this target has to be dropped entirely; the comment records that deadline so the next stall is diagnosed faster than this one was. The existing tag can be rebuilt through the workflow's `workflow_dispatch` input once this is on the default branch, so no re-tag or version bump is needed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the
install.sh404:curl -fsSL https://drop.lifbom.com/install.sh | shfails with404ondrop-x86_64-unknown-linux-musl.tar.gzeven though that artifact built successfully.Why the install fails
There is no release.
gh release listis empty.releases/latest/download/…has nothing to serve.The tag is fine and the workflow did fire on it — it is stuck:
ubuntu-24.04ubuntu-24.04-armmacos-14macos-13publishisneeds: build, and withfail-fast: falseit waits for the whole matrix. Three artifacts are built and sitting in the run; the release cannot be created until the fourth finishes.Cause
macos-13began deprecation on 2025-09-22 and was fully unsupported by 2025-12-04. A job requesting a retired label is never assigned a runner.The failure mode is what made this hard to spot: it queues indefinitely rather than failing.
timeout-minutes: 30does not help, because that clock counts execution time, not time spent waiting for a runner. Nothing ever forces the run to end, so the release just silently never appears.macos-15-intelis the Intel replacement. It is available until August 2027, when GitHub drops x86_64 macOS entirely and this matrix entry has to go — the comment in the workflow records that deadline.Recovering v0.1.0
No re-tag or version bump needed. The workflow already has a
workflow_dispatchinput for exactly this. Once this is on the default branch:tag: v0.1.0.workflow_dispatchtakes the workflow definition from the default branch whileactions/checkoutusesref: ${{ inputs.tag }}, so it builds v0.1.0's source with the corrected runner labels.Verification
scripts/check-secrets.shpasses.contents: writepermission was already correct, so nothing else blocks it.Not fixed here: the build jobs emit Node 20 deprecation warnings for
actions/upload-artifact@v4. Worth a bump, but unrelated to the stall and better kept out of a release-path fix.🤖 Generated with Claude Code