chore: build release only on tags starting with eOS-
Description
AdvancedPrivacy caused a few problems with the /e/OS RC this year, mainly caused by misunderstanding of which version should be embeded or not.
With this MR, the release build is only built if a eOS- (like eOS-1.13) tag is present on the commit. This way we can easily continue to merge new feature while the validation of a new /e/OS version, without accidentaly having a fresh feature in a late /e/OS RC.
To sumup, for AdvancedPrivacy releasing,
- the versions to include in prebuilds apk and release are the one from the pipeline of the Tags "eOS-..."
- in case of fixes during Beta/RC , a branch will be used (strategy 1 in the workflow ), and the Tag will be on this branch to flag the version to embed in /e/OS.
Edited by Guillaume Jacquart