Note that the release tag must match the shipped source
This commit is contained in:
@@ -127,6 +127,12 @@ Two scripts per repo: `build-app.sh <version>` and `release.sh <version>`.
|
|||||||
--repo TZGyn/<repo> --login gitea.tzgyn.dev
|
--repo TZGyn/<repo> --login gitea.tzgyn.dev
|
||||||
```
|
```
|
||||||
|
|
||||||
|
Push `main` **before** this: `tea` tags the remote default branch, so an
|
||||||
|
unpushed commit means the tag points at source that is not what shipped
|
||||||
|
(the binary would contain changes absent from the tag). If it already
|
||||||
|
happened, re-point the tag: `git push origin :refs/tags/v<version>` then
|
||||||
|
`git tag -f v<version> <commit> && git push origin v<version>`.
|
||||||
|
|
||||||
4. **Bump the cask** (`version` + `sha256`), push the tap, pull Homebrew's
|
4. **Bump the cask** (`version` + `sha256`), push the tap, pull Homebrew's
|
||||||
clone, `brew audit`. Verify by downloading the asset back and comparing the
|
clone, `brew audit`. Verify by downloading the asset back and comparing the
|
||||||
sha256, and `spctl -a -vv <App>.app` → `accepted` /
|
sha256, and `spctl -a -vv <App>.app` → `accepted` /
|
||||||
|
|||||||
Reference in New Issue
Block a user