Synchronize local branch after publishing
Some checks failed
Validate Decky / web-client (push) Has been cancelled

This commit is contained in:
Elijah 2026-07-20 09:35:51 -07:00
parent a0b46497c1
commit e7b2326521
3 changed files with 51 additions and 15 deletions

View file

@ -40,10 +40,11 @@ runner only validates the web client via `.forgejo/workflows/validate.yml`.
`artifacts/release/vX.Y.Z/` and stay out of Git.
- Publish by double-clicking `scripts/Publish-DeckyRelease.cmd` or by invoking
`scripts/Publish-ForgejoRelease.ps1`. The publisher creates the tag/release,
uploads the installer/signature, and commits `releases/latest.json` to `main`.
- Publishing creates a new remote metadata commit. Fetch/rebase or pull before
the next push; a non-fast-forward rejection usually means this commit is
missing locally. LF-to-CRLF messages on Windows are warnings, not failures.
uploads the installer/signature, commits `releases/latest.json` to `main`, and
automatically fast-forwards the local checkout to that metadata commit.
- The publisher requires a clean `main` that exactly matches `origin/main`, so
commit and push source first. LF-to-CRLF messages on Windows are warnings,
not failures.
- Forgejo: `https://git.elijahkuntz.com/Elijah/Decky`. A publishing PAT needs
`write:repository`; never commit or print it.
- The permanent Tauri updater key is outside the repository at