3 Commits

Include renames

Author	SHA1	Message	Date
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	3e1652ca98	ci: drop the inert GitHub workflows ... Gitea ignores `.github/workflows/` entirely once `.gitea/workflows/` is non-empty, so these two files have had no effect since the release workflow landed — and the GitHub repo they targeted is gone (404, suspended account), so they cannot run there either. They were not merely dead: warm-cache.yml's Monday cron kept firing on the Gitea side before `.gitea/` existed, queueing jobs against GitHub-hosted labels (`macos-14`, `windows-2022`, `ubuntu-24.04-arm`) that no self-hosted runner advertises. Those sat queued forever, and its one dispatchable leg failed on `rustup: command not found` — the same bare-image gap the Gitea workflow now provisions around. `.gitea/workflows/release.yml` is the only pipeline; docs/RELEASE.md already documents it as such. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-10 22:11:28 -04:00
ZacharyZhang-NY	13ccab980c	ci: warm a main-branch build cache so release tag builds aren't cold ... GitHub Actions cache isolation lets a run restore caches only from its own ref or the default branch. Releases run on tag refs and nothing ever ran on main, so release.yml's rust-cache never restored anything — every release compiled all 62 crates cold on five targets (~50 min, gated by Windows at ~49.5 min). warm-cache.yml builds the same release-dist profile with the same rust-cache key on main (dep-affecting pushes — including each release's version-bump commit — plus a weekly refresh against 7-day eviction and manual dispatch). Tag builds then restore a warm default-branch cache; the remaining cost is workspace-crate compilation + the codegen-units=1 thin-LTO link, which is the deliberate release-hardening tradeoff.	2026-07-22 19:59:00 -04:00