Mirrored_Repos/InvokeAI
1
0
Fork 0
mirror of https://github.com/invoke-ai/InvokeAI synced 2024-08-30 20:32:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

feat(installer): remove vX-latest from tag_release

Browse Source 
Also update RELEASE.md accordingly, and make the release.yml workflow match on `v*` tags.
This commit is contained in:
psychedelicious
2024-01-01 11:18:40 +11:00
committed by Kent Keirsey
parent 50e58ff323
commit 99ee8f9099
3 changed files with 3 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/RELEASE.md
View File

@ -15,7 +15,7 @@ While the release workflow does not include end-to-end tests, it does pause befo
The `release.yml` workflow runs a number of jobs to handle code checks, tests, build and publish on PyPI.
It is triggered on **tag push**, when the tag matches `v*.*.*`. It doesn't matter if you've prepped a release branch like `release/v3.5.0` or are releasing from `main` - it works the same.
It is triggered on **tag push**, when the tag matches `v*`. It doesn't matter if you've prepped a release branch like `release/v3.5.0` or are releasing from `main` - it works the same.
> Because commits are reference-counted, it is safe to create a release branch, tag it, let the workflow run, then delete the branch. So long as the tag exists, that commit will exist.
@ -23,10 +23,6 @@ It is triggered on **tag push**, when the tag matches `v*.*.*`. It doesn't matte
Run `make tag-release` to tag the current commit and kick off the workflow.
This script actually makes two tags - one for the specific version, and a `vX-latest` tag that changes with each release.
Because the release workflow only triggers on the pattern `v*.*.*`, the workflow will only run once when running this script.
The release may also be run [manually].
### Workflow Jobs and Process