Skip to content

ci: skip npm publish when no new commits since last tag#180

Merged
JohnMcLear merged 1 commit intomainfrom
fix/skip-publish-on-empty-revs
May 3, 2026
Merged

ci: skip npm publish when no new commits since last tag#180
JohnMcLear merged 1 commit intomainfrom
fix/skip-publish-on-empty-revs

Conversation

@JohnMcLear
Copy link
Copy Markdown
Member

Template-wide fix for the publish-on-empty-revs bug. Same patch as ep_subscript_and_superscript#127 (pilot, currently in flight). The bump step early-exits when no new commits since the last tag, but npm publish then runs unconditionally and tries to republish the existing version. Gate the post-bump steps on a new bumped step output. Self-merges on green CI.

The bump step in npmpublish.yml early-exits when there are no new
commits since the latest tag, but the publish step then runs
unconditionally and tries to republish the existing version, failing
with 'cannot publish over previously published versions'.

Only fires for manual `gh workflow run` on a tag-current branch
(on:push always has ≥1 new commit), but leaves a spurious red on
CI. Gate the post-bump steps on a new `bumped` step output.

Template-wide fix: ep_subscript_and_superscript#127 was the pilot.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@qodo-code-review
Copy link
Copy Markdown

ⓘ You've reached your Qodo monthly free-tier limit. Reviews pause until next month — upgrade your plan to continue now, or link your paid account if you already have one.

@JohnMcLear JohnMcLear merged commit b5177fc into main May 3, 2026
2 checks passed
@JohnMcLear JohnMcLear deleted the fix/skip-publish-on-empty-revs branch May 3, 2026 11:29
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