Provides new actions to help with generating and publishing releases.
The generate-release action is a manual dispatch action that takes the version number as an input, and depending on the major version, will checkout either main or main_1.x, then merge either develop or develop_1.x into it, bump all the version strings in the repo, and raise a PR against main or main_1.x.
The publish-release action runs on merge to main or main_1.x and reads the version from the version.txt file to determine the release tag it should publish, then publishes that release.
NOTE: both of these actions are broken in v2 of the repo until we bring it up to date with the Swift Package Manager support changes, as the version.txt file does not exist in develop currently.
Here is a screenshot of how the Action looks like once it is merged to the "Default" branch (has to be made available in the Default branch for it to appear):
First you would select the Action name and then select the "Run workflow" dropdown tab to parameterize the release (pick v1 or v2, and then input minor and patch versions).
Change Notes
Added generate-release action that creates a PR from main, merges develop into it, and bumps the version to the desired value.
Added publish-release action that creates a new release after a merge to main or main_1.x
Pre-submission Checklist
[x] I ran the unit tests locally before checking in.
[x] I made sure there were no compiler warnings before checking in.
[x] I have written useful documentation for all public code.
[ ] I have written unit tests for this new feature.
Description
Provides new actions to help with generating and publishing releases.
The generate-release action is a manual dispatch action that takes the version number as an input, and depending on the major version, will checkout either main or main_1.x, then merge either develop or develop_1.x into it, bump all the version strings in the repo, and raise a PR against main or main_1.x.
The publish-release action runs on merge to main or main_1.x and reads the version from the version.txt file to determine the release tag it should publish, then publishes that release.
NOTE: both of these actions are broken in v2 of the repo until we bring it up to date with the Swift Package Manager support changes, as the version.txt file does not exist in develop currently.
I validated all the behavior in a test repo here: https://github.com/theRealRobG/TestManualAction
Here is a screenshot of how the Action looks like once it is merged to the "Default" branch (has to be made available in the Default branch for it to appear):
First you would select the Action name and then select the "Run workflow" dropdown tab to parameterize the release (pick v1 or v2, and then input minor and patch versions).
Change Notes
generate-releaseaction that creates a PR from main, merges develop into it, and bumps the version to the desired value.publish-releaseaction that creates a new release after a merge tomainormain_1.xPre-submission Checklist