Skip to content

release: a module tag that is not there is told by gh's status, not its output - #115

Merged
aledbf merged 1 commit into
mainfrom
release-module-tag-404
Nov 18, 2026
Merged

aledbf merged 1 commit into
mainfrom
release-module-tag-404

Conversation

@aledbf

@aledbf aledbf commented Nov 18, 2026

Copy link
Copy Markdown
Member

gh api prints a 404's body on stdout and exits 1, so the release of
1974d6e read the error's JSON as the commit v0.20261118.2 names and refused
to tag it (release run of 2026-11-18 19:23). The status says whether the tag
is there; the output is read only when it is.

Tried against GitHub: a tag that is not there answers "none (would create)", one that is answers its commit.

🤖 Generated with Claude Code

…ts output

gh api prints a 404's body on stdout and exits 1, so the release of
1974d6e read the error's JSON as the commit v0.20261118.2 names and refused
to tag it (release run of 2026-11-18 19:23). The status says whether the tag
is there; the output is read only when it is.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@aledbf
aledbf merged commit 2501764 into main Nov 18, 2026
3 checks passed
@aledbf
aledbf deleted the release-module-tag-404 branch November 18, 2026 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant