> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/governance/versioning-and-release-management.md).

# Versioning & Release

Ensure stability and control across your development and production environments with detailed guidance on Versioning & Release Management.

This documentation provides best practices and technical steps for maintaining multiple solution versions, managing change control, promoting applications and agents reliably across environments (Dev, QA, Prod), and minimizing downtime during updates.

This is key to enabling seamless, continuous deployment for your AI automations.

For account-wide governance and operational visibility, use the [Control Center](/start-here/control-center.md). Use [Observability](/governance/observability.md) to monitor adoption and agent outcomes after release.


---

# 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.uptiq.ai/governance/versioning-and-release-management.md?ask=<question>&goal=<endgoal>
```

`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.