3 Commits

Include renames

Author	SHA1	Message	Date
ZacharyZhang-NYandClaude Opus 5.5	ddecaea075	Return the forge to Gitea: releases, self-update, links, CI ... The GitHub account is gone again, so git.zacharyzhang.com/ZacharyZhang-NY/Kigi-CLI is the canonical repo. Reverse f7a4cb6: - .gitea/workflows/release.yml: restore the Gitea edition retired in f7a4cb6 (draft release, per-target upload, SHA256SUMS, then publish). The Windows leg runs on the windows-amd64 label the current runner advertises. - .github/workflows/{release,warm-cache}.yml: drop them; they target hosted GitHub runners and softprops, and Gitea ignores them once .gitea exists. - kigi-env: update_base_url defaults to the Gitea Releases API again. - install.sh / install.ps1: resolve releases from git.zacharyzhang.com. - feedback, /docs, SECURITY.md, frontend worker + site: repo, issues and raw-file links point at git.zacharyzhang.com. - docs/RELEASE.md: Gitea edition of the checklist with the current runners. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-10 02:25:59 -04:00
ZacharyZhang-NY	f7a4cb64ab	Return the forge to GitHub: releases, self-update, links, CI ... The GitHub account is restored, so github.com/ZacharyZhang-NY/Kigi-CLI is the canonical repo again. Reverse the 2026-08 Gitea migration: - .github/workflows/{release,warm-cache}.yml: restore the GitHub-hosted pipeline dropped in 3e1652c, unchanged — hosted runners, rust-cache, softprops release with every asset attached atomically. - .gitea/workflows/release.yml: retire the Gitea edition (the runners are being deregistered; git.zacharyzhang.com keeps the v0.1.12/v0.1.13 releases for old clients). - kigi-env: update_base_url now defaults to the GitHub Releases API. The updater already speaks GitHub wire format and sends a User-Agent; v0.1.14 is published to BOTH forges with identical assets so pre-0.1.14 installs polling Gitea self-update onto the GitHub channel. - install.sh / install.ps1: resolve releases from api.github.com. - feedback, /docs, SECURITY.md, frontend worker + site: repo, issues and raw-file links point at github.com / raw.githubusercontent.com. - docs/RELEASE.md: GitHub edition of the checklist; Gitea runner sections retired. - version: 0.1.13 -> 0.1.14 (the cross-forge transition release). Claude-Session: https://claude.ai/code/session_01A6RcwHhhsFYYrNdQB4ASuP	2026-09-01 01:05:22 -04:00
ZacharyZhang-NYandClaude Opus 5	8864b9ecc5	ci(gitea): add the release workflow and point it at our real runners ... Gitea has no hosted runners, so every `runs-on` has to name a machine we registered ourselves — and the labels in the first draft of this file did not match what our machines advertise. The only online Linux runner (`dokploy-runner-01`) offers `ubuntu-latest`/`ubuntu-24.04`/`ubuntu-22.04`, never `linux-x86_64`, and Gitea's API cannot relabel a runner remotely, so a `v*` tag would have queued forever against a label nothing served. The three Linux jobs therefore run on `ubuntu-latest`. That runner is in container mode against a bare runner-image, so those legs now provision what they need per run: build-essential, pkg-config, unzip (protoc), tar and jq, plus rustup when absent — installed with `--default-toolchain none` so `rust-toolchain.toml` still decides the channel and `rustup show` materialises it. `prepare` installs jq/curl the same way. macOS stays on `macos-arm64` and Windows on `windows-x86_64`, both host mode with their toolchains preinstalled, so the new provisioning step is gated on a `linux:` matrix key rather than on `ext == 'tar.gz'`, which covers Darwin too. docs/RELEASE.md picks up the corrected label table, the fact that `register --labels` is ignored once config.yaml supplies them, the registration-token call being a POST (a GET parses as runner id 0 and 404s), and how each host-mode runner is supervised so it survives reboots and crashes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-10 20:21:22 -04:00