Conversation
|
We should also add the dependabot integration to this repo, it'll create a new PR to every new release of the dependencies used in the The coolest thing is that we're able to add reviewers to avoid breaking changes when merging these updates, and other kinds of stuff, like labels. |
| - name: Install dependencies | ||
| run: yarn install | ||
|
|
||
| - name: Build |
There was a problem hiding this comment.
Aren't we missing a bump step?
There was a problem hiding this comment.
Indeed, I'll add it
47e7be8 to
102fb36
Compare
|
Flux:
|
Isn't it better to publish to NPM when there is a new release? So we have better control over our publish and over our versions. For example if we have 2 MRs ready to be merged, we don't need to send 2 new versions to NPM, we may want to release them together. |
| - name: Set up Node.js | ||
| uses: actions/setup-node@master | ||
| with: | ||
| node-version: 10.0.0 |
The workflow that will publish the package will only run after a We also would need to have a branch for staging, in order to merge the pull requests of |


This PR adds a github actions workflow to publish the package to NPM on every new release.
We would just need to worry about bumping the version and then creating a new release. The workflow will run the steps to make sure that the build is working as expected and publish it to NPM.