Release: a version published by hand is there, not "NOT published" - #4
Merged
Merged
Conversation
The tag run for 0.1.0 reached its publish step two minutes after the
version had been published by hand. npm view still answered 404 - the
registry's read side lags a publish by minutes - so the step tried to
publish, the registry refused ("cannot publish over the previously
published versions: 0.1.0"), and the step fell through to its last
branch: a warning that 0.1.0 was NOT published because the package did
not exist yet. The run was green, and both claims were wrong.
A refusal to publish over an existing version means the version is on
the registry, so the step says that and ends. The other outcomes are
unchanged: published, a failed publish of a package that exists (an
error), and the bootstrap warning for one that does not. Checked with
the step's script against a stub npm for each of the four outcomes.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018bBcFp146qnMCmXWztQaH8
5 tasks
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
2 participants
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.
Summary
The tag run for
v0.1.0(run 36508769034) was green but ended with a wrong warning. This is what happened:npm viewstill answered 404, because the registry's read side lags a publish by minutes. So the step tried to publish.You cannot publish over the previously published versions: 0.1.0.The fix: a refusal to publish over an existing version means the version is already on the registry. The step now says so and ends. The other outcomes are unchanged:
The same fix goes into cap2UI5/cap2UI5's
release.yml, which this workflow was modelled on.Test plan
npmfor each outcome:::error::::warning::🤖 Generated with Claude Code
https://claude.ai/code/session_018bBcFp146qnMCmXWztQaH8
Generated by Claude Code