> 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/registry/disability-registry/versions.md).

# Versions

Where Disability Registry releases and changelogs are published.

Every version, with its changes: [Disability Registry changelog](https://openg2p.github.io/versions/disability-registry/CHANGELOG.html).

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

The Disability Registry has no frozen release yet. Only `0.0.0-develop.N` versions are published.

Every image and the Helm chart built from a commit carry the same version. A chart version tells you exactly which images it deploys.

## Two version lines

This registry's version and the platform's move independently:

* **This registry's version** — the wrapper chart and its five images, locked together and stamped by CI on every commit.
* **Platform version** — the `openg2p-registry` chart and images it extends, pinned deliberately and changed as a pair. See the [Registry Platform changelog](https://openg2p.github.io/versions/registry-platform/CHANGELOG.html).

How versions are derived, frozen and promoted: [Helm & Docker Versioning Strategy and CI](/operations/deployment/helm-docker-versioning-and-ci.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/products/registry/disability-registry/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.