Gitea | v1.26.1

Gitea v1.26.1 released on 24-04-2026


Gitea v1.26.1 is out now. Self-hosters and CI users receive a collection of reliability and correctness fixes for Actions and workflows, along with fixes across authentication, package/container handling, Git index and archive handling, and UI/permissions edge cases.

See the release on the Gitea GitHub for the full changelog and detailed notes.

What’s in this release

  • Actions & workflows: add event.schedule context for scheduled workflow tasks, fix actions concurrency-group cross-branch leaks, and return TriggerEvent (not Event) for scheduled workflow runs in the API; GetActionWorkflow now supports fallback references.
  • Authentication, container and packages: correct URL escaping for OAuth2 flows, fix container registry authentication on public instances, and fall back to the noarch RPM when the requested architecture package is missing.
  • Git, archives and UI: use modern git update-index –cacheinfo syntax to support more file names, fix dumps producing uncompressed zip archives by default, resolve Mermaid diagram rendering when node labels contain line breaks, and several fixes for org/team permissions, badges, AppFullLink and editor layout.

Upgrade notes

  • The workflow runs API now returns TriggerEvent for scheduled runs; update integrations that expect an Event field to consume TriggerEvent instead.
  • Standard rollback applies: if needed, reinstall the previous release available from the Gitea GitHub releases page.

Tell us how the upgrade goes and share any issues or feedback on the project’s GitHub or community channels.

Related posts

Agentic AI still needs domain judgement

Agentic AI can write the thing, but it still cannot tell you whether the thing is right. That is where domain expertise matters, because a clean config or neat bit of glue logic can still be wrong in...

Weekly Tech Digest | 06 Jul 2026

Stay updated with the latest in tech! This digest covers AI ethics, auto industry shifts, and the impact of politics on technology, exploring today's pressing issues.

wolfCOSE zero-allocation parsing in embedded C

wolfCOSE looks sensible only if you care about what your firmware actually has to carry. I like that, because on small targets the wrong crypto feature can cost more than the message itself, and there...