> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/platform/platform-services/approval-workflow-engine/versions.md).

# Versions

Version history of the OpenG2P Approval Workflow Engine (AWE).

Every version, with its changes: [AWE changelog](https://openg2p.github.io/versions/awe/CHANGELOG.html).

All OpenG2P components are indexed at [openg2p.github.io/versions](https://openg2p.github.io/versions/).

AWE source code, Docker images, and the Helm chart all live in the single repository [`awe`](https://github.com/OpenG2P/awe). The `openg2p-awe` chart and its images carry the same version. How versions are derived: [Helm & Docker Versioning Strategy and CI](/operations/deployment/helm-docker-versioning-and-ci.md).

Images publish to Docker Hub (`openg2p/openg2p-awe`, `openg2p/openg2p-awe-ui`) and the chart to [`openg2p-helm`](https://openg2p.github.io/openg2p-helm).

## Earlier versions

The changelog starts at 1.1.0 (17-Jul-2026). Earlier release:

| Source / Helm Version                                | Runtimes                                                                                                                                                                                  | Last Modified | Comments                                                                                                                                                                                                                                                                                                           |
| ---------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [v1.0.0](https://github.com/OpenG2P/awe/tree/v1.0.0) | <p><a href="https://hub.docker.com/r/openg2p/openg2p-awe/tags">openg2p-awe:v1.0.0</a><br><br><a href="https://hub.docker.com/r/openg2p/openg2p-awe-ui/tags">openg2p-awe-ui:v1.0.0</a></p> | 19-Jun-2026   | First tagged release. Multi-stage approval engine with versioned policies, Keycloak-native approver resolution, signed webhook callbacks, admin UI, and Helm chart. Registry is the first caller integration. See [v1.0.0 release notes](/platform/platform-services/approval-workflow-engine/releases/v1.0.0.md). |

***

## Caller deployments

AWE is deployed **per caller module** — e.g. `registry-awe` for the Registry, `pbms-awe` for PBMS. Each deployment gets its own database, Keycloak clients, and Helm release name.

For Registry integration design, see [Integration with Registry](/platform/platform-services/approval-workflow-engine/integration-with-registry.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openg2p.org/platform/platform-services/approval-workflow-engine/versions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.