Skip to content

Release Summary

This section contains information related to Appcircle releases.

Release flow

Appcircle follows a two-phase release flow:

  1. Cloud (SaaS) release is performed first.
  2. Self-hosted release follows after the Cloud rollout is validated.

Release checklist

For the step-by-step actions, prerequisites, and verification tasks, refer to the Release Checklist page.

What you can find under this section

Each release may include changes that require operational coordination. Under the Release section you will find:

  • Environment variable updates required for the release
  • External configuration changes (provider or platform-specific)
  • Container image changes (new images, tag updates, migrations, deprecations)
  • Backend service release flow for individual ac-server-* / ac-service-* services. See Backend Service Release.
  • Component release rules for workflow and publish components. See Component Release.

If a release requires changes in more than one environment (e.g., dev, prep, prod), the release notes or the related pages should explicitly list the affected environments and the rollout order.

Self-hosted release impact (Single-zone mode vs DMZ mode)

Self-hosted changes may vary depending on the installation’s network posture:

  • DMZ mode: A deployment mode that uses network segmentation. In this mode, public-facing web servers are deployed in the DMZ zone. Backend services are deployed in the internal LAN and communicate according to predefined ingress/egress rules.
  • Single-Zone mode: A deployment mode where public-facing web servers and backend services are deployed within the same zone (no DMZ segmentation).

Because of this, some releases may require variant-specific updates (DNS/TLS, proxy/egress rules, IdP redirect URLs, registry and storage endpoints).

Self-hosted release notes may be documented per deployment type:

  • Docker: Single-Zone / DMZ
  • Podman: Single-Zone / DMZ
  • Helm (Kubernetes): Single-Zone / DMZ
  • OpenShift: Single-Zone / DMZ

If a release affects only certain variants, the related release pages must explicitly state which variants are impacted and what needs to change.