Skip to content

Commit

Permalink
[release process] Robustify the version-bump PR
Browse files Browse the repository at this point in the history
This just adds a little info about what will happen after a
version bump PR is merged.
  • Loading branch information
jagthedrummer committed Aug 17, 2023
1 parent 9625e71 commit 6ac506e
Showing 1 changed file with 7 additions and 1 deletion.
8 changes: 7 additions & 1 deletion .github/workflows/version-bump.yml
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,13 @@ jobs:
Tag v${{ steps.bump-all.outputs.NEW_VERSION_NUMBER }}
- Auto-generated by [create-pull-request][1]
Note: Merging this PR with trigger the following actions:
* The `main` branch will be tagged with `v${{ steps.bump-all.outputs.NEW_VERSION_NUMBER }}`
* A GitHub Release will be created for `v${{ steps.bump-all.outputs.NEW_VERSION_NUMBER }}`
* Version `${{ steps.bump-all.outputs.NEW_VERSION_NUMBER }}` of the gems will be pushed to rubygems.org
* Version `${{ steps.bump-all.outputs.NEW_VERSION_NUMBER }}` of the npm packages will be pushed to npmjs.com
- Auto-generated by [create-pull-request][1] via `.github/workflows/version-bump.yml`
[1]: https://github.com/peter-evans/create-pull-request
labels: |
Expand Down

0 comments on commit 6ac506e

Please sign in to comment.