setting up an action to publish bpmn-js whenever there is a release.
This commit is contained in:
parent
82c0824c60
commit
5946b50c7c
|
@ -0,0 +1,25 @@
|
|||
name: Tests
|
||||
|
||||
# On release, run tests and deploy to NPM
|
||||
on:
|
||||
release:
|
||||
|
||||
# Job Setup
|
||||
jobs:
|
||||
publish:
|
||||
runs-on: ubuntu-latest
|
||||
steps:
|
||||
|
||||
- uses: actions/checkout@v2 #Checkout Repo
|
||||
- uses: actions/setup-node@v1 #Setup Node
|
||||
with:
|
||||
node-version: 18
|
||||
- run: npm install
|
||||
- run: npm test
|
||||
- uses: JS-DevTools/npm-publish@v1
|
||||
with:
|
||||
token: ${{ secrets.NPM_TOKEN }}
|
||||
access: public
|
||||
- if: steps.publish.outputs.type != 'none'
|
||||
run: |
|
||||
echo "Version changed: ${{ steps.publish.outputs.old-version }} => ${{ steps.publish.outputs.version }}"
|
|
@ -27,3 +27,4 @@ jobs:
|
|||
run: |
|
||||
npm ci
|
||||
npm run test
|
||||
|
||||
|
|
|
@ -66,6 +66,7 @@ To build the example into the `public` folder execute
|
|||
npm run all
|
||||
```
|
||||
|
||||
|
||||
## License
|
||||
MIT
|
||||
|
||||
|
||||
|
|
|
@ -0,0 +1,11 @@
|
|||
## Releases
|
||||
|
||||
Be sure to edit the package.json, and update the version. Releases won't create
|
||||
a new NPM package unless the version was updated. Be sure to create a new version
|
||||
that matches
|
||||
And also edit setup.py and assure that has the same release tag.
|
||||
New versions of SpiffWorkflow are automatically published to PyPi whenever
|
||||
a maintainer of our GitHub repository creates a new release on GitHub. This
|
||||
is managed through GitHub's actions. The configuration of which can be
|
||||
found in .github/workflows/....
|
||||
Just create a release in GitHub that mathches the release number in doc/conf.py
|
Loading…
Reference in New Issue