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

# Versions

Where to find Farmer Registry chart and image versions, and what changed in each.

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

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

## What is published

The Farmer Registry publishes its own Docker images and Helm chart. Every image and the chart built from a commit carry the same version. A chart version tells you exactly which images it deploys.

| Artifact                             | Where                                                                                                                                    |
| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| Helm chart `openg2p-farmer-registry` | [`openg2p-helm`](https://openg2p.github.io/openg2p-helm)                                                                                 |
| Docker images                        | Docker Hub `openg2p/openg2p-farmer-registry-<name>`: `staff-api`, `partner-api`, `celery`, `db-seed`, `sanity-tests`, `agent-portal-api` |

## The two version lines

This registry's chart and images share one version. The platform version it extends moves separately, only when it is bumped ([Domain registry charts](/products/registry/registry/deployment-and-extension/packaging-and-reference-registry.md#domain-registry-charts)). Platform changes: [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).

## Earlier versions

The changelog lists every release. Develop builds and release candidates from earlier periods are listed in the older catalogues:

| Earlier catalogue                                                                                  | What it holds                                                |
| -------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ |
| [GitLab catalogue](https://openg2p.gitlab.io/versions/registry-farmer-registry/CHANGELOG.html)     | develop builds and release candidates from the GitLab period |
| [previous GitHub catalogue](https://openg2p.github.io/openg2p-packaging/farmer-registry/CHANGELOG) | develop builds and release candidates from before that       |


---

# 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/farmer-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.