Skip to content

Allow the npm publish workflow to be run manually - #21

Merged
MikeAlhayek merged 1 commit into
mainfrom
ma/npm-publish-manual-trigger
Oct 4, 2026
Merged

MikeAlhayek merged 1 commit into
mainfrom
ma/npm-publish-manual-trigger

Conversation

@MikeAlhayek

Copy link
Copy Markdown
Member

Summary

Add a workflow_dispatch trigger to publish_npm_release.yml so a release can also be started from the Actions tab (Run workflow), alongside the existing tag trigger. This was meant to land with #20 but was pushed just after that PR merged.

  • The manual run takes a required version input (e.g. 1.2.6, no leading v). It is used instead of the tag name and published from the branch selected in the dialog.
  • The version, from either a tag or the input, must be MAJOR.MINOR.PATCH (a leading v is accepted).
  • Tag pushes behave as before. A manual run publishes to npm but does not create a git tag.

The Run workflow button only appears once this is on main.

🤖 Generated with Claude Code

@MikeAlhayek
MikeAlhayek merged commit 596b402 into main Oct 4, 2026
3 checks passed
@MikeAlhayek
MikeAlhayek deleted the ma/npm-publish-manual-trigger branch October 4, 2026 21:06
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