Added semantic-release, which analyzes commit messages and determines if a new release should be deployed. New release versions are based off commit messages. If breaking changes are present, a new major will be released else if feat: is used, a new minor is released else if fix: is used a new patch will be released.
It is currently set to dry run and debug to verify that it's working. I've attempted to test it on other branches, even forked, but it seems it needs to be run on the master branch for a complete dry run. The results can be seen here https://github.com/pycom/pymakr-vsc/runs/3925443100?check_suite_focus=true
To get past this last obstacle, it seems we need to test the dry run on master
[10:38:15 AM] [semantic-release] › ℹ This test run was triggered on the branch semantic-release, while semantic-release is configured to only publish from master, therefore a new version won’t be published.
EDIT:
I also tried making automatic deployments dependent on tests succeeding, but on: workflow_run only works on the primary branch it seems.
Additionally, to handle betas, I've reached out to the maintainer of semantic-release-vsce to ask about the possibility for using other branches. While VSCE only supports major releases, we the minors would be published to Github releases as assets.
Added
semantic-release, which analyzes commit messages and determines if a new release should be deployed. New release versions are based off commit messages. If breaking changes are present, a new major will be released else iffeat:is used, a new minor is released else iffix:is used a new patch will be released.It is currently set to dry run and debug to verify that it's working. I've attempted to test it on other branches, even forked, but it seems it needs to be run on the master branch for a complete dry run. The results can be seen here https://github.com/pycom/pymakr-vsc/runs/3925443100?check_suite_focus=true
To get past this last obstacle, it seems we need to test the dry run on master
EDIT: I also tried making automatic deployments dependent on tests succeeding, but
on: workflow_runonly works on the primary branch it seems. Additionally, to handle betas, I've reached out to the maintainer ofsemantic-release-vsceto ask about the possibility for using other branches. While VSCE only supports major releases, we the minors would be published to Github releases as assets.