ci: Add bump version workflow for release tags #138
Conversation
* Add tbump based bump version workflow for managing release tags from
GitHub Actions workflow dispatch. The workflow adds support for:
- bumping versions, creating tags, pushing the tags back to GitHub
- release candidates as viable options
- automated checks that the SemVer type of bump (major, minor, patch),
and if it was or wan't a release candidate, makes sense given the
latest tags available on GitHub and the new tag number entered
- dry runs (the default) to test that your options all look good
|
@eduardo-rodrigues to unblock conda-forge/staged-recipes#19135 how do you feel about releasing a |
| @@ -0,0 +1,244 @@ | |||
| name: Bump version | |||
There was a problem hiding this comment.
This is the workflow pyhf uses to bump the version in CI so that we don't accidentally ever commit something wrong.
That sounds great to me! Just a detail: we were working in parallel and I created minutes ago #139 to supersede PR #132 that is messy. At this point we could get PR # 139 merged in and 132 closed. Then tag :-). |
Codecov ReportBase: 68.75% // Head: 68.75% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #138 +/- ##
=======================================
Coverage 68.75% 68.75%
=======================================
Files 2 2
Lines 208 208
Branches 56 56
=======================================
Hits 143 143
Misses 58 58
Partials 7 7
Flags with carried forward coverage won't be shown. Click here to find out more. Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
and if it was or wan't a release candidate, makes sense given the
latest tags available on GitHub and the new tag number entered