Currently (in v0.2.1), the version must be updated prior and after releasing (by creating a PR). This is painful and error prone
The git tag is created only when the GitHub release is published.
I suggest we do something like for the bpmn-visualization TypeScript library.
We provide a GitHub workflow that will do everything for us:
- It takes as an input the version to release.
- it updates the files with the new version and commit
- then it creates the related tag
- then it updates the files with the development version and commit
- finally, it push the changes and the tag
If possible, the development version should be automatically computed by the workflow to avoid human error
Tasks to do
Add a Github workflow triggered by workflow_dispatch (manual run)
Documentation
Notes
- remember that the GH_TOKEN has readonly permissions by default
- check how we proceed in the bpmn-visualization-js repo
- don't forget to use the playground repository for testing
Currently (in v0.2.1), the version must be updated prior and after releasing (by creating a PR). This is painful and error prone
The git tag is created only when the GitHub release is published.
I suggest we do something like for the bpmn-visualization TypeScript library.
We provide a GitHub workflow that will do everything for us:
If possible, the development version should be automatically computed by the workflow to avoid human error
Tasks to do
Add a Github workflow triggered by
workflow_dispatch(manual run)Documentation
Notes