> 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/products/g2p-bridge/versions.md). # Versions {% hint style="info" %} **For the current versions, changelogs, and the exact Helm chart & Docker image links, go here:** ## 👉 [G2P Bridge — Versions & Changelog](https://openg2p.gitlab.io/versions/g2p-bridge-g2p-bridge/CHANGELOG.html) That page is **generated on every build and is always up to date**. The [historical tables](#historical-versions) further down are kept only as a record of the pre-GitLab builds. {% endhint %} ## How versioning & publishing work G2P Bridge is now built and published **entirely on GitLab** (previously GitHub + Docker Hub), using OpenG2P's shared Helm & Docker packaging pipeline. In brief: * **One immutable version per commit** — `0.0.0-develop.` on `develop` (by commit ordinal) and a frozen `N.N.N` on release (promote-on-release). A version is never rebuilt or overwritten. * **Helm charts** are published to the **shared OpenG2P Helm registry**, so one Rancher/Helm repo lists every OpenG2P chart (Bridge included): [gitlab.com/groups/openg2p/-/packages](https://gitlab.com/groups/openg2p/-/packages). * **Docker images** live in **each repo's own Container Registry** — the Bridge's are at `registry.gitlab.com/openg2p/g2p-bridge/g2p-bridge/` (`partner-api`, `bene-portal-api`, `celery`, `example-bank-*`). * **Changelogs** are generated from commit messages onto the changelog page linked above. This scheme is the same across all OpenG2P repos and is documented once — for the full details see [**Helm & Docker Versioning Strategy and CI**](https://docs.openg2p.org/operations/deployment/helm-docker-versioning-and-ci). *** ## Historical versions The tables below are a **read-only record of builds published before the GitLab move** — Docker Hub images and the GitHub `openg2p-helm` chart. They are **not** updated for GitLab builds; for those, always use the [changelog page](https://openg2p.gitlab.io/versions/g2p-bridge-g2p-bridge/CHANGELOG.html) above. {% hint style="warning" %} **Two similarly-named charts — don't confuse them.** The **current** chart is **`openg2p-bridge`** (images `openg2p-bridge-*`; Rancher: “OpenG2P Bridge”). The **legacy** line is **`openg2p-g2p-bridge`** (images `openg2p-g2p-bridge-*` — the extra `g2p`; Rancher: “OpenG2P G2P Bridge”). They differ by a single `g2p`, are easy to confuse in the Rancher list, and are **not compatible**. For any new install use **`openg2p-bridge`**. {% endhint %} ### Previous versions The last builds of the **current** `openg2p-bridge` chart under the old (Docker Hub + GitHub `openg2p-helm`) scheme, up to `1.0.0` and the final `0.0.0-develop.` dev build:
Helm Chart & VersionG2P Bridge RuntimesLast modifiedContents
openg2p-bridge
(Rancher: “OpenG2P Bridge”)

0.0.0-develop.41		openg2p-bridge-partner-api:develop

openg2p-bridge-bene-portal-api:develop

openg2p-bridge-celery:develop

openg2p-bridge-example-bank-{api,celery-beat-producers,celery-workers}:develop		01-Jul-2026

Rolling develop build. Major changes vs 1.0.0:

  1. Partner signatures verified via the Partner Manager (PM) service (openg2p-fastapi-common PartnerMgmtKeyStore) — no MOSIP Keymanager and no local key store; the Bridge fetches partner public keys from PM.
  2. Partner API signature validation enabled by default in the chart (secure-by-default; the app-config default is off): inbound verify + signed Bridge→SPAR resolve. Partners (incl. PARTNER_G2P_BRIDGE) are onboarded in Partner Manager — the trial's pm-seed Job does this automatically.
  3. Local .p12 signing key with demo / inline / existing-secret modes.
  4. Sanity smoke + e2e run as a post-install hook by default (can fail the deploy).
  5. Deployment hardening: pre-upgrade DB password-sync hook + fail-loud migrate.
openg2p-bridge
(Rancher: “OpenG2P Bridge”)

1.0.0		openg2p-bridge-partner-api:1.0.0

openg2p-bridge-bene-portal-api:1.0.0

openg2p-bridge-celery:1.0.0
(single image, run as beat and worker)

openg2p-bridge-example-bank-api:1.0.0

openg2p-bridge-example-bank-celery-beat-producers:1.0.0

openg2p-bridge-example-bank-celery-workers:1.0.0		26-Jun-2026

Intermediate Stable Version

  1. Single consolidated chart for the complete installation. Incompatible with previous Helm chart versions.
  2. Source consolidated into a single repository, g2p-bridge (previously seven repos).
  3. Added Keycloak client provisioning via the keycloak-init Learn more >>
  4. Digital cash transfer needs no PBMS or Registry. Learn more >>
  5. Single Celery Docker image, run as beat producer or worker by Helm configuration.
  6. Added an uninstall script that fully tears down the release cleanly
  7. Partner API authentication is disabled by default in this version — inbound signature validation is off; when enabled, 1.0.0 validates signatures via MOSIP Keymanager (the keycloak-init client authenticates to it). From develop this is replaced by in-process local JWS (no Keymanager).
*** ## Legacy Versions These versions predate the repository/chart consolidation. They were built from the older multi-repository layout (`openg2p-g2p-bridge-deployment`, `openg2p-g2p-bridge-example-bank-deployment`, etc.) with a separate chart per service. They are **not compatible** with the consolidated chart above. Their Docker images use the **`openg2p-g2p-bridge-*`** prefix (the extra `g2p`) — e.g. `openg2p-g2p-bridge-partner-api`, `openg2p-g2p-bridge-celery-workers` — which is what distinguishes them from the current chart's `openg2p-bridge-*` images.
Helm Chart & VersionG2P Bridge RuntimesVersion dateContents
openg2p-g2p-bridge
(Rancher: “OpenG2P G2P Bridge”)

3.0.0		openg2p-g2p-bridge-celery-beat-producers:v2.1.0
openg2p-g2p-bridge-celery-workers:v2.1.0
openg2p-g2p-bridge-partner-api:v2.1.0
openg2p-g2p-bridge-bene-portal-api:v2.1.0		17-Apr-2026
  1. Complete overhaul of Helm chart. Multiple charts combined into one. Incompatible with previous Helm chart versions.
  2. Embraced new headers from openg2p-fastapi-common
  3. Caters to cash-digital, cash-physical, commodities and services
  4. Interfaces to Warehouses and Agents for physical goods & services
  5. In line with PBMS Gen2 capabilities
  6. Introduced Adapter pattern for SPAR
openg2p-g2p-bridge
2.0.0
openg2p-g2p-bridge
1.1.0
openg2p-g2p-bridge
1.0.2		06 Dec 2024Release contents
--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.openg2p.org/products/g2p-bridge/versions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.