Commit Graph

4 Commits

Author SHA1 Message Date
ozan 80a358e8da fix(ci): route runs-on: deploy jobs through Spot, not the deleted executor
The dispatcher routed `deploy`-labelled jobs (deploy-arikigame, release) to
invokeLambdaExec → the tinqs-ci-exec Lambda. That Lambda was deleted on
26 May 2026, and EXECUTOR_FUNCTION_NAME was never set, so every deploy job
silently hit the `[DRY RUN] Would invoke executor` no-op and never ran.

DEVOPS.md already states "deploy jobs go through Spot now" — the code just
never followed. Drop the dead `case "deploy"` so `deploy` falls through to
the default Spot path (labelToSpot already maps deploy → t3.micro). Remove
the now-unused invokeLambdaExec, ExecFnName, and awslambda import.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-07 19:50:47 +01:00
ozan 46bef04a7d fix: remove dead git.tinqs.com rewrite — subdomain never existed
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-26 05:29:22 +01:00
ozan 6bf4ed8314 chore: replace git.tinqs.com with tinqs.com — subdomain retired
Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-26 05:26:48 +01:00
ozan 501953c636 tinqs/ci — composite actions + Lambda dispatcher for Spot CI runners
Actions: checkout, setup-go, setup-node, setup-aws
Dispatcher: Lambda → EC2 Spot (ephemeral, self-terminating)
Images: base, go, node, docker, deploy, godot

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-05-26 01:37:55 +01:00