Conversation
The publish job runs
zsh -f scripts/verify-release-tag.zsh
on ubuntu-latest, which ships no Zsh, so the step exits 127 before any
verification happens and publication fails for every tag:
/home/runner/work/_temp/....sh: line 1: zsh: command not found
Every other workflow here installs Zsh before running it, promotion-readiness
and zsh-n among them. This job was the only one that did not.
Latent since #470, because the workflow reached main only with the #494
promotion. Pushing v2.0.1 was its first execution and it failed on that run.
v2.0.1 was published manually after running verify-release-tag.zsh locally
against the exact tag, which passed, so the authorization logic was exercised
and only its broken environment was bypassed.
Swept the other workflows for the same shape; this was the only occurrence.
Closes #496
This was referenced Sep 3, 2026
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.
Adds the missing Zsh install to the publish job. One step.
The defect
release.ymlruns the authorization verifier under Zsh:ubuntu-latestships no Zsh, so the step exits 127 before any verification happens and publication fails for every tag:Every other workflow that runs Zsh installs it first (
promotion-readiness.yml:27,zsh-n.yml:84). The publish job was the only one that did not. I swept the remaining workflows for the same shape and found no other occurrence.Why it went unnoticed
The workflow reached
mainonly with #494, since #470 added it onnextbefore v2.0.0 shipped. Pushingv2.0.1was its first ever execution, and it failed on that run. Latent since #470.What happened to v2.0.1
Published manually, because the alternative was worse.
verify-release-tag.zshrequires the tag target to equal the currentorigin/main, so landing this fix movesmainand invalidates any tag already pushed. Recovering through the workflow would have meant either moving a public tag or burning a version number.Before publishing I ran the verifier locally against the exact tag:
so the authorization logic was exercised in full and only its broken execution environment was bypassed.
Follow-up worth considering, not in this PR
That same tag-equals-
mainprecondition is what made this failure expensive to recover from: any fix to the release path invalidates the pending tag. Loosening it to "tag target is an ancestor oforigin/main" would preserve the intent, that a release comes from reviewed stable history, while allowing a straightforward retry. Raised in #496 and left for a separate decision.Closes #496