-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
I suggest the following workflow when a VCMI release is published:
- find the pre-release that was used to create VCMI release (as it may not necessarily be the latest one)
- rename the pre-release from
<date>
tox.y.z (<date>)
- convert it to the latest release
- change attached tag to
x.y.z
(it won't delete existing tag)
This way it'd be clear which dependencies to use for a given release.
Point 1 should be done in a VCMI repo workflow and then notify this repo of release passing the pre-release name, we already have such process for our Homebrew repo: https://github.com/vcmi/vcmi/blob/develop/.github/workflows/on-release.yml
Metadata
Metadata
Assignees
Labels
No labels