Skip to main content

Changelog

Released product highlights, newest first. Loha services are versioned and released independently, so this page groups customer-visible changes by month rather than using one platform-wide version number. For work that has not been released, see the Roadmap.

September 2026​

  • A clearer first-build path. After connecting a repository, Loha can identify when .loha.yml is missing, explain the next step, and offer starter configuration. It rechecks the repository before saving, so an outdated or unreadable proposal is not committed.
  • More reliable build recovery. Build details now distinguish current cluster observations from stale information and provide clearer waiting reasons. Lifecycle handling also prevents duplicate active retries and recovers build-state races more safely.

August 2026​

  • Automatic webhook registration. Connecting a repository can register the push webhook with GitLab, GitHub, Gitea, or Forgejo, removing the need to copy a callback URL and secret by hand. See Repo hosts.
  • Release visibility. Browse recorded container-image releases and trace them back to the source build and commit.

July 2026​

  • Outbound webhooks. Configure scoped build-completion webhooks, inspect deliveries, retry a delivery, send a test ping, and rotate the signing secret. Availability is controlled per workspace. See Outbound webhooks.
  • MCP server. A hosted MCP server lets supported AI coding agents read build information and logs through workspace-authorised access. See MCP Server.

June 2026​

  • Independent service releases. Loha services now version and release independently instead of sharing one platform-wide version.
  • In-app notifications. The app can surface build-completion notifications as they arrive. See Notifications.
  • Trigger validation. Loha detects conflicts between trigger filters and the .loha.yml on: block before a build is run.
  • Pipeline configuration improvements. Pipelines support per-job resource_class and Git-provider webhook ingress. The app also supports light and dark themes.
Saved pipelines were retired

An earlier June release introduced reusable saved pipeline templates. The feature was retired in July in favour of defining pipelines directly on a trigger or in .loha.yml, keeping the source of truth in your repository.

Earlier releases​

  • Programmatic access. Versioned public API endpoints, personal access tokens, and workspace service accounts for automation.
  • Pipeline catalog and builder. A task catalog, a form-based pipeline builder, and CI configuration import/generation.
  • Core CI/CD workflow. Repository connections, trigger deliveries, build history, log viewing, retry/cancel controls, encrypted secrets, and workspace quotas.

How releases ship​

Each service is versioned independently through Changesets and released from a tagged monorepo commit. A change to a shared package can update several service versions together.