L4 0.3.10

This release connects Gitea, and Forgejo, as a second Git provider next to GitHub. Agents can take a Task to a draft pull request in a Gitea repository. Landing, Shell, installer, Server, portable runtime and Docs share 0.3.10. It stays on the server-v2 lineage and adds no migrations. Customer Servers update only when their operator chooses an update.

Gitea

• Server settings → Git → Gitea connects a Gitea or Forgejo bot account by its access token. L4 checks the token with Gitea, then stores it encrypted on the Server. Agents and Compute Nodes never receive it. See Repositories and code work.
• Repository environments, Agent repository and pull request reads, code proposals, required checks and Factory publication work with Gitea repositories.
• Gitea cannot limit a token to chosen repositories, so the Server limits every request to one repository and one kind of operation. The bot account's collaborator access decides which repositories L4 can reach.
• A draft pull request in Gitea has a WIP: title. Required checks match commit statuses, which Gitea Actions reports per job.
• Agents cannot add executable files in Gitea, and Factory publication stops unless Gitea writes exactly the approved commit.
• Role repository scopes name Gitea repositories by their connection, so they never match a GitHub repository with the same number.

Compute Nodes

• A Docker Node fetches Gitea source through the Server, with a permission that ends with its job. This needs the 0.3.10 workspace image; older images refuse Gitea sources and keep working with GitHub.

Update to this release

A Cloudflare Server that keeps Cloudflare access updates from Server settings → Deployment → Updates by itself. A Docker Server updates by its image tag in Coolify or Docker Compose; the VPS installer uses llll upgrade. Update Docker Compute Nodes to the 0.3.10 workspace image before running Gitea Tasks on them.