> 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/spar/versions.md). # Versions {% hint style="info" %} **For the current versions, changelogs, and the exact Helm chart & Docker image links, go here:** ## 👉 [SPAR — Versions & Changelog](https://openg2p.gitlab.io/versions/spar-spar/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 SPAR 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 (SPAR included): [gitlab.com/groups/openg2p/-/packages](https://gitlab.com/groups/openg2p/-/packages). * **Docker images** live in **each repo's own Container Registry** — SPAR's are at `registry.gitlab.com/openg2p/spar/spar/` (`mapper-partner-api`, `bene-portal-api`). * **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/spar-spar/CHANGELOG.html) above. {% hint style="warning" %} **Two similarly-named charts — don't confuse them.** The **current** chart is **`openg2p-spar`** (Rancher: “OpenG2P SPAR”). The **legacy** line is the chart named **`spar`**. Both use the same `openg2p-spar-*` Docker images, so the **chart name** is what distinguishes them, and they are **not compatible**. For any new install use **`openg2p-spar`**. {% endhint %} ### Previous versions The last builds of the **current** `openg2p-spar` chart under the old (Docker Hub + GitHub) scheme, up to `1.0.0` and the final `0.0.0-develop.` dev build:
Helm Chart & VersionSPAR RuntimesLast modifiedContents
openg2p-spar
(Rancher: “OpenG2P SPAR”)

0.0.0-develop.26		openg2p-spar-mapper-partner-api:develop

openg2p-spar-bene-portal-api: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. SPAR only verifies (no signing key).
  2. Partner signature verification ON by default, against public keys fetched from the Partner Manager (PM) service (no local key store). Partners are onboarded in PM; the trial's G2P Bridge chart onboards PARTNER_G2P_BRIDGE there, so signed Bridge→SPAR resolve verifies out of the box.
  3. Branch-derived rolling Helm chart versioning (0.0.0-develop.<run>).
openg2p-spar
(Rancher: “OpenG2P SPAR”)

1.0.0		openg2p-spar-mapper-partner-api:1.0.0

openg2p-spar-bene-portal-api:1.0.0		27-Jun-2026

Stable version

  1. Signature verification via MOSIP Keymanager; added Keycloak client provisioning via the keycloak-init subchart (the openg2p-spar OIDC client in the staff realm authenticates the Mapper API to Keymanager). From develop this is replaced by in-process local verification.
  2. Aligned Keycloak/auth configuration with NSR conventions — shared settings moved under global to avoid duplication.
  3. Fixed Helm rendering errors (sparMapperAPI values key, ingress host, env-var handling) and bumped Istio VirtualServices to networking.istio.io/v1beta1.
  4. Added an uninstall script that fully removes the release and its Postgres database/role while keeping Keycloak client secrets intact.
*** ## Legacy Versions These versions predate the chart consolidation. They were built from the older `openg2p-spar-deployment` layout with the chart named **`spar`** (a separate chart per service). They are **not compatible** with the consolidated `openg2p-spar` chart above.
Helm Chart & VersionSPAR RuntimesVersion dateContents
spar

2.0.0		spar-bene-portal-api:v2.1.0

spar-mapper-partner-api:v2.1.0		17-Apr-2026
  1. Incompatible changes w.r.t previous versions. Learn more >>
  2. Moved to Common Headers of openg2p-fastapi-common
  3. Removed self-service-api and introduced spar-bene-portal-api — in line with OpenG2P Architecture
  4. Removed spar-mapper-api and introduced spar-partner-api — in line with OpenG2P Architecture
  5. Rationalized DFSP models (in bene portal, erstwhile self-service) to simplified — BANK, BRANCH and WALLET-PROVIDER models
spar
1.1.0		03-Nov-2025
spar
1.0.0		03-May-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/spar/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.