Still in progress, here be 🐉
Until #70 is solved, the release workflow is gonna be wonky.
- Make a branch for the release
- Run
script/tag-releaseand choose the next tag - Run
script/build.sh TAG, add the results - Remove any older bin version from
dist - Commit, PR, Merge
- On the merge commit, run
script/tag-releaseagain
Note
If the current PR is known to create a new version, it's acceptable to commit the next bin as part of it.
To test the action from a branch, run script/build.sh and commit the results.
You can now use the branch name to test your code.
E.g.
- uses: nobe4/action-ln@branch-nameTip
There's no need to push the code, just pushing the dist is enough for testing.