> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/sdk/versioning-policy.md).

# Versioning Policy

UOF SDK versioning supports the evolution of our services without impacting our current clients' integrations.

The packages are available via standard package repositories ([Maven Central](https://central.sonatype.com/namespace/com.sportradar.unifiedodds.sdk) and [nuget.org](https://www.nuget.org/packages/Sportradar.OddsFeed.SDKCore/))

#### Release Schedule <a href="#uofsdkversioningpolicy-releaseschedule" id="uofsdkversioningpolicy-releaseschedule"></a>

*Once a year new major release is planned.*

The major release may include:

* updated libraries
* removed obsolete methods or properties
* may include breaking interface changes

{% hint style="warning" %}
**NOTE**

To adapt to the constantly evolving threat landscape, we reserve the right to update dependencies in the minor versions in case the vulnerabilities are found.
{% endhint %}

{% hint style="warning" %}
**NOTE**

The old version is supported for another year and will only receive critical bug fixes.&#x20;

All new product features will ONLY be available in the latest major release.
{% endhint %}

{% hint style="success" %}
**TIP**

We recommend upgrading to the latest version in order to take advantage of new functionality and optimize for the best user experience.
{% endhint %}

#### **Version Number** <a href="#uofsdkversioningpolicy-versionnumber" id="uofsdkversioningpolicy-versionnumber"></a>

major.minor.patch (i.e. 3.1.0)

We consider the following to classify the changes

* Major release - includes breaking changes and new product features
* Minor release critical bug fixes and/or new product features
* Patch release - other bug fixes


---

# 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.sportradar.com/uof/sdk/versioning-policy.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.
