-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GitHub Action for publishing new releases #59
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not too fond of automatic publishing "on push". Since this isn't something that is done a lot, a manual trigger using workflow_dispatch
might be an alternative.
When triggering manually, it is possible to enter a variable which could be used to pass along a version number. Instead of parsing the number from the file, the action could use the provided version number and save it in the necessary files in the repo (even committing the changed file(s)).
I updated the action so that it can only be started from a workflow. The new version number will be asked upon invocation of the workflow dispatch and the |
…isualizations into feature/publish-action
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I seem to have forgotten to add my suggestion to github:
I think a lot of the regex stuff can be handled by npm version
This PR adds a new GitHub Action that automatically pushes a new version of this package on NPM, and that automatically creates a new release on GitHub (which we still need to manually annotate with release notes).