4 Commits

Include renames

Author	SHA1	Message	Date
bvandeusenandClaude Opus 5	fa0827f668	ci: pin the download mirror to v6, not v5 — match on @actions/artifact ... The previous pin matched the two actions by their own version numbers, which is meaningless: upload-artifact and download-artifact release on unrelated cadences. upload v5 bundles @actions/artifact ^4.0.0; download v5 bundles ^2.3.2. "v5 and v5" was in fact a mismatched pair. download v6 is the tag that puts ^4.0.0 on both sides — and ^4.0.0 is the library major just proven against this instance by the upload side (thoughtsync run 3094: two artifacts listed, downloaded and extracted intact). ^2.3.2 has never been exercised here. Not v7: that major is a runner requirement rather than a feature change. It moves to runs.using: node24 and upstream requires runner >= 2.327.1 for it, which act_runner does not claim to satisfy. Everything pinned stays node20. ci-requirements.md now carries the version/runtime table and the reasoning, so the next person matches on the library instead of the tag number. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-30 15:37:43 -04:00
bvandeusenandClaude Opus 5	52d53e0044	ci: swap artifact upload+download to the mirrored actions (issue 2270) ... android.yml and release.yml uploaded via actions/upload-artifact@v3, which reports success while Gitea stores the result in a format its v4-only artifact API will never serve back — 72 artifacts on this repo are on disk, have valid DB rows, and are invisible to every retrieval path. Green jobs producing nothing retrievable. release.yml is a producer/consumer pair: android-release uploads minstrel-apk and image-release downloads it to bundle into the container. Swapping only the upload would have left download-artifact@v3 reading the v1/v3 listing and finding nothing, so mirror the download side too — bvandeusen/download-artifact, pull mirror of forgejo/download-artifact, pinned at its v5 tag to match the upload pin's major. Not actions/{upload,download}-artifact@v4: isGhes() throws on the hostname before opening a connection, so no server-side change reaches it. Upload steps also set if-no-files-found: error — image-release hard-depends on minstrel-apk existing, so an empty upload must fail where it happens. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-07-30 15:28:10 -04:00
bvandeusen	3cf829752b	chore(ci): migrate workflows to gitea + consolidate keystore secret ... - rename .forgejo/workflows/ to .gitea/workflows/ (git mv preserves history); Gitea Actions reads either path, but the directory now matches the active platform - collapse ANDROID_STORE_PASSWORD + ANDROID_KEY_PASSWORD into a single ANDROID_KEYSTORE_PASSWORD secret (PKCS12 keystores require the two passwords to be identical, so the duplication carried no information); build.gradle.kts still reads two env vars to stay format-agnostic, both now sourced from the same secret in CI - ignore android/*.keystore, android/*.keystore.*, android/*.jks, android/keystore.properties so the regenerated signing material never reaches a remote on accident - update prose references from Forgejo to Gitea in CLAUDE.md and the docs; the historical "migrated from Forgejo" note in CLAUDE.md is kept intentionally; forgejo/upload-artifact@v3 action refs are left untouched (canonical artifact action, resolves cleanly under Gitea Actions) Operator side: ANDROID_KEY_ALIAS, ANDROID_KEYSTORE_PASSWORD, and ANDROID_KEYSTORE_B64 secrets registered in Gitea before this lands.	2026-05-31 23:05:03 -04:00
bvandeusenandClaude Opus 4.7	c1fb2355c4	ci: migrate to ci-runners.md (container.image consumption) ... Adopts the FabledRulebook ci-runners.md policy: workflows select toolchains via container.image, not via runs-on labels. `runs-on` stays as the scheduling handle only. Workflows updated: - test-go.yml: ci-go:1.26 on both `test` and `integration` jobs. - test-web.yml: ci-go:1.26 (bundles Node + npm); the actions/setup-node@v4 step is removed. - flutter.yml: ci-flutter:3.44 (Flutter 3.44 + Android + Java 25). - release.yml: ci-go:1.26 (ships docker CLI + buildx). Side effect: this unblocks the Go server deps bump (commit 6a62120) which auto-bumped go.mod to `go 1.25.0` via x/crypto v0.51.0's minimum — ci-go:1.26 satisfies it with headroom. Adds ci-requirements.md at repo root per the ci-runners.md "every project ships a requirements sheet" rule. Documents: runtime images consumed, image deps used per workflow, per-job installs (none), and a Notes section covering the integration docker-socket dependency, the toolchain pin rationale, and the in-app-update channel polling. Tracked in local task #70. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-20 14:24:38 -04:00