diff --git a/RELEASING.md b/RELEASING.md index 454c721..1dfd2ef 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -86,6 +86,11 @@ scratch vault/config — never against the real `~/.onyx-cli/config.yaml`. > **Windows gotcha**: the plain bash tool can't execute a freshly built > `.exe` directly (`command not found`) — always invoke it through > `cmd.exe /c "onyx.exe ..."`. +> +> **Linux scratch config**: run the smoke as a script file +> (`wsl -d Ubuntu-24.04 -- bash smoke.sh`), and save the binary path +> (`B=$HOME/onyx-build/dist/onyx`) before pointing `HOME` at a scratch +> directory, so the real config stays untouched. ## 5. Deploy locally (optional) @@ -129,33 +134,29 @@ git push origin vX.Y.Z ## 7. Create the Gitea release -`tea` hangs indefinitely under a plain non-interactive shell call, for -*any* subcommand, including fully local ones. Always launch it as a -supervised process (hub `start`/`wait`/`logs`), never via the bash tool -directly. +Use `gt` (gitea-cli 1.0+; `tea` is archived). `gt` never pushes, so step 6 +must be done first; `--verify-tag` refuses a tag the server doesn't have. +From the bash tool, invoke it through `cmd.exe /c` like the exe above. Write release notes to a scratch file, then create the release with both assets in one call: ``` -tea releases create --repo olivier/onyx-cli --tag vX.Y.Z --title vX.Y.Z \ - --note-file release-notes-vX.Y.Z.md -a dist/onyx.exe -a dist/onyx-linux +gt release create vX.Y.Z dist/onyx.exe dist/onyx-linux --title vX.Y.Z \ + --notes-file release-notes-vX.Y.Z.md --verify-tag --no-input ``` If the release already exists and you're adding a platform binary later -(e.g. the Linux build wasn't ready yet), attach it separately instead: +(e.g. the Linux build wasn't ready yet), attach it separately instead +(`--clobber` replaces an asset with the same name): ``` -tea releases assets create --repo olivier/onyx-cli vX.Y.Z dist/ +gt release upload vX.Y.Z dist/ ``` Delete the scratch release-notes file afterward — it's not a repo convention file. -> `tea repos create --owner olivier` fails with `GetOrgByName` — `--owner` -> targets an organization, not your personal account. Omit it entirely -> when creating a repo under your own user. - ## 8. Verify the release ```bash