Auto bump mobile version after release#2013
Conversation
|
|
||
| ((CURR_VER++)) | ||
| NEW_VER=$CURR_MAJOR$CURR_VER | ||
|
|
There was a problem hiding this comment.
Is it possible for to trigger the version bump workflow with the needed inputs? Similar to how we do it in build-browser.yml?
https://github.com/bitwarden/clients/blob/12bca0a597dada622e23a37830da0c266b0c8048/.github/workflows/build-browser.yml#L348
There was a problem hiding this comment.
That's a great idea to trigger the version bump workflow from the new auto bump workflow.
Co-authored-by: Micaiah Martin <77340197+mimartin12@users.noreply.github.com>
…om/bitwarden/mobile into feature/DEVOPS-849_autobump_mobile
mimartin12
left a comment
There was a problem hiding this comment.
It's a bummer that we can't test with workflow_dispatch without merging into master. 😞
We can merge a stub of this file into |
|
Added PR for the suggested stub: #2015 |
|
Workflow tested. Ready for the review :) |
Type of change
Objective
Add workflow to auto bump mobile version after release. Not tested because Github doesn't detect new workflows from other branches than the default branch.
Code changes
Screenshots
Before you submit
dotnet tool run dotnet-format --check) (required)