Elijah/Decky
1
0
Fork 0
Code Issues Pull requests Projects Releases 3 Packages Wiki Activity Actions

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

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

12
app/UPDATES.md
View file

@ -73,7 +73,6 @@ current PowerShell process and run:
$env:FORGEJO_PAT = 'paste-token-for-this-session'
powershell -ExecutionPolicy Bypass -File .\scripts\Publish-ForgejoRelease.ps1 -Version 0.3.0 -Notes "Board and stack management"
Remove-Item Env:FORGEJO_PAT
git pull --ff-only
```
For an interactive, double-clickable option, run:
@ -86,11 +85,12 @@ It bypasses PowerShell's script policy only for the publisher process, prompts
for the version and a hidden personal access token, and leaves the window open
so any error can be read. The token is not saved.
The publisher creates the `v0.3.0` Forgejo release/tag at `main`, uploads the
installer, signature, and metadata, then commits the tracked
`releases/latest.json` through the Forgejo API. The final pull synchronizes that
small metadata commit locally. Existing Decky installations then discover the
release through Settings.
The publisher first verifies that the working tree is clean and local `main`
exactly matches `origin/main`. It then creates the `v0.3.0` Forgejo release/tag,
uploads the installer, signature, and metadata, and commits the tracked
`releases/latest.json` through the Forgejo API. Finally, it automatically
fast-forwards local `main` to that metadata commit. Existing Decky installations
then discover the release through Settings.
## Forgejo Actions