Automatically release all merges to master on npm.
JavaScript
481
175 commits
updated Jun 12, 2023
GitHub Action for automated npm publishing.
This Action publishes a package to npm. It is meant to be used on every successful merge to master but
you'll need to configure that workflow yourself. You can look to the
.github/workflows/push.yml file in this project as an example.
"feat: new API" and "feature: new API".You can configure some aspects of merge-release action by passing some environmental variables.
package.json is to run npm publish. Defaults to the root dir.https://registry.npmjs.org/merge-release will use npm publish unless you've defined a publish script in your package.json.
- uses: mikeal/merge-release@master
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}
DEPLOY_DIR: my/deploy/dir
SRC_PACKAGE_DIR: my/src/package
1,483 followers · starred Mar 2019
456 followers · starred Jul 2019
272 followers · starred Sep 2019
477 followers · starred Feb 2020
Automatically release all merges to master on npm.
JavaScript
481
175 commits
updated Jun 12, 2023
GitHub Action for automated npm publishing.
This Action publishes a package to npm. It is meant to be used on every successful merge to master but
you'll need to configure that workflow yourself. You can look to the
.github/workflows/push.yml file in this project as an example.
"feat: new API" and "feature: new API".You can configure some aspects of merge-release action by passing some environmental variables.
package.json is to run npm publish. Defaults to the root dir.https://registry.npmjs.org/merge-release will use npm publish unless you've defined a publish script in your package.json.
- uses: mikeal/merge-release@master
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
NPM_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}
DEPLOY_DIR: my/deploy/dir
SRC_PACKAGE_DIR: my/src/package
1,483 followers · starred Mar 2019
456 followers · starred Jul 2019
272 followers · starred Sep 2019
477 followers · starred Feb 2020