Gitea | v1.26.1

Gitea v1.26.1 released on 24-04-2026


Gitea v1.26.1 is out now. It adds an event.schedule context and switches scheduled-run API responses to use TriggerEvent, fixes actions concurrency-group leaks across branches, and delivers a set of authentication, packaging, repository and UI bug fixes to improve scheduled workflows, concurrency correctness and action resolution.

See the release notes on Gitea’s GitHub for full details.

What’s in this release

  • Adds event.schedule context for scheduled actions and uses TriggerEvent for scheduled-run API responses to improve scheduled workflow handling.
  • Fixes actions concurrency-group leaks across branches and enhances GetActionWorkflow to support fallback references for more robust workflow lookups.
  • Authentication, container and packaging fixes: fixes OAuth2 URL-escaping, corrects container registry authentication for public instances, and falls back to noarch when a requested RPM arch is missing.

Upgrade notes

  • No breaking changes are listed in the release notes; review the GitHub release page for any compatibility details specific to your setup.
  • If you need to roll back, restore previous package versions or backups according to your existing deployment procedures.

Share comments or report issues on Gitea’s issue tracker or community channels to let the maintainers know how this release performs in real environments.

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...