This PR intends to add a Release Github Action workflow to automate the process of releasing rubixgoplatform to Github.
This workflow is triggered whenever a tag is pushed. It expects the tag to be in either v{number}.{number}.{number} or v{number}.{number}.{number}-rc.{number} format.
Valid Tag Formats:
v0.1.2
v0.2.1rc-2
Invalid Tag Formats:
v0.1
0.1.3
v0.1.2-beta
Once the release action is successfully completed, the release is tagged as latest. Hence, if a release is meant to be a draft, that has to be changed manually after its published to Github. Changelog details are also added
Linux and Darwin (MacOs) based binaries are archived in tar.gz format, while Windows based binary is archived in zip format
For reference, check the dummy release page generated through this Release Workflow here
This PR intends to add a Release Github Action workflow to automate the process of releasing
rubixgoplatformto Github.This workflow is triggered whenever a tag is pushed. It expects the tag to be in either
v{number}.{number}.{number}orv{number}.{number}.{number}-rc.{number}format.Valid Tag Formats:
v0.1.2v0.2.1rc-2Invalid Tag Formats:
v0.10.1.3v0.1.2-betaOnce the
releaseaction is successfully completed, the release is tagged aslatest. Hence, if a release is meant to be adraft, that has to be changed manually after its published to Github. Changelog details are also addedLinux and Darwin (MacOs) based binaries are archived in
tar.gzformat, while Windows based binary is archived inzipformatFor reference, check the dummy release page generated through this Release Workflow here