R3
This commit is contained in:
+6
-2
@@ -25,11 +25,15 @@ references it as `${{ secrets.RELEASE_TOKEN }}`; the value is never committed.
|
||||
Each push to `main` runs tests and packaging. The publish script:
|
||||
|
||||
1. Deletes the existing release associated with `rolling`, if present.
|
||||
2. Moves or creates the `rolling` tag at the pushed commit.
|
||||
2. Deletes and recreates the `rolling` tag at the pushed commit using Gitea's
|
||||
repository tag API.
|
||||
3. Creates a prerelease named with the commit prefix.
|
||||
4. Uploads the `.deb`, extension ZIP, and `SHA256SUMS`.
|
||||
|
||||
The moving tag is intentionally mutable. Permanent releases should use reviewed
|
||||
The moving tag is intentionally mutable. This server's Swagger API exposes tag
|
||||
replacement as `DELETE /repos/{owner}/{repo}/tags/{tag}` followed by
|
||||
`POST /repos/{owner}/{repo}/tags`; the publisher uses that contract rather than
|
||||
the unsupported Git refs patch route. Permanent releases should use reviewed
|
||||
immutable tags after validating a rolling artifact.
|
||||
|
||||
## Local rehearsal
|
||||
|
||||
Reference in New Issue
Block a user