Skip to content

Release workflow: publish right away instead of leaving a draft - #6

Merged
burnersen merged 1 commit into
mainfrom
claude/publish-directly
Oct 31, 2026
Merged

burnersen merged 1 commit into
mainfrom
claude/publish-directly

Conversation

@burnersen

Copy link
Copy Markdown
Owner

Like the other tools, a release is now published as soon as every step has passed. If any step fails, nothing is published.

  • A version with a suffix (e.g. 2.1.0-rc1) is published as a pre-release.
  • A leftover draft of the same version is replaced, so running the release for 2.0.1 again publishes it. A release that is already published is never overwritten; the run stops with an error instead.
  • Publishing now uses gh (preinstalled) instead of softprops/action-gh-release.

Generated by Claude Code

Like the other burnersen tools, a release is now published as soon as
every step passed; if any step fails, nothing is published. A version
with a suffix (2.1.0-rc1) becomes a pre-release. A leftover draft of the
same version is replaced, so the 2.0.1 draft gets published by running
the release once more. Publishing uses gh instead of
softprops/action-gh-release.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GvUq7HnA5ggbuHBogzS2rV
@burnersen
burnersen merged commit c49c6be into main Oct 31, 2026
5 checks passed
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.

2 participants