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

# Versions

Where Crop Sown Registry releases and changelogs are published.

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

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

Every image and the Helm chart built from a commit carry the same version, set by the central CI pipeline. A chart version therefore tells you exactly which images it deploys.

## Release status

The Crop Sown Registry has **no frozen release yet**. Only moving `0.0.0-develop.N` versions are published. In Rancher, tick **Show pre-release versions** to see them.

## Two version lines

| Line                  | What                                                                                                                                     | Where to look                                                                                            |
| --------------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------- |
| **This registry**     | The `openg2p-crop-sown-registry` chart and its four images (`staff-api`, `partner-api`, `celery`, `db-seed`), always at the same version | The [Crop Sown Registry changelog](https://openg2p.github.io/versions/crop-sown-registry/CHANGELOG.html) |
| **Registry platform** | The `openg2p-registry` chart and images this registry extends, pinned in the chart and the Dockerfiles together                          | The [Registry Platform changelog](https://openg2p.github.io/versions/registry-platform/CHANGELOG.html)   |

The platform version is pinned in `Chart.yaml` and the Dockerfiles together, and moves only when it is bumped ([Domain registry charts](https://docs.openg2p.org/products/registry/registry/deployment-and-extension/packaging-and-reference-registry.md#domain-registry-charts)).

How versions are derived, frozen and promoted: [Helm & Docker Versioning Strategy and CI](https://docs.openg2p.org/operations/deployment/helm-docker-versioning-and-ci.md).

## Upgrading an early install

Installs from before the Cluster ID was generated are brought up to date on upgrade by `meta_data/zz-upgrades/`: it adds the **Programme Cluster Code** field, turns on ID generation and updates the Cluster screens and search. Existing clusters keep their typed codes as Cluster IDs, since activities refer to them, and the code is also copied into the Programme Cluster Code.


---

# 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/crop-sown-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.
