lab/telegram-agent
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Fix CI: Forgejo Actions schema validation error #1

New issue
Closed
opened 2026-09-20 17:23:49 +00:00 by lab · 0 comments
lab commented 2026-09-20 17:23:49 +00:00
Owner
Copy link

Problem

The CI workflow (build-and-push) failed instantly on every push (runs 121–122).

Root cause: ${{ gitea.sha }} in the workflow file. Forgejo Actions aliases the github context to gitea/forgejo, but the expression parser only accepts ${{ github.* }} — gitea.sha fails YAML schema validation ("Unknown Variable Access gitea"), and the job never starts.

Fix (commit 4785db0)

  • gitea.sha → github.sha
  • Image builds switched to kaniko (gcr.io/kaniko-project/executor:debug), which builds daemon-less inside a plain container — the runner needs no Docker/buildkit capability
  • Dropped actions/checkout@v4 (needs node, not present in kaniko image); kaniko clones the repo itself via --context=git://...
  • Registry auth written to /kaniko/.docker/config.json from FORGEJO_REGISTRY_USER/PASSWORD repo secrets

Result

Run 124 success: build-and-push + deploy both green, telegram-agent running in cluster.

## Problem The CI workflow (`build-and-push`) failed instantly on every push (runs 121–122). Root cause: `${{ gitea.sha }}` in the workflow file. Forgejo Actions aliases the `github` context to `gitea`/`forgejo`, but the expression parser only accepts `${{ github.* }}` — `gitea.sha` fails YAML schema validation ("Unknown Variable Access gitea"), and the job never starts. ## Fix (commit `4785db0`) - `gitea.sha` → `github.sha` - Image builds switched to **kaniko** (`gcr.io/kaniko-project/executor:debug`), which builds daemon-less inside a plain container — the runner needs no Docker/buildkit capability - Dropped `actions/checkout@v4` (needs `node`, not present in kaniko image); kaniko clones the repo itself via `--context=git://...` - Registry auth written to `/kaniko/.docker/config.json` from `FORGEJO_REGISTRY_USER`/`PASSWORD` repo secrets ## Result Run 124 success: build-and-push + deploy both green, `telegram-agent` running in cluster.
lab closed this issue 2026-09-20 17:23:50 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
No results found.
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lab/telegram-agent#1
No description provided.