# Versioning practices

### Semver is used

ODPI uses [SemVer](https://semver.org/)—semantic versioning—on our components. The three types of versions are:

* **Major** versions contain [breaking changes.](https://governance.opendataproducts.org/v1/specification/breaking-changes)
* **Minor** versions add new features or deprecate existing features without [breaking changes.](https://governance.opendataproducts.org/v1/specification/breaking-changes)
* **Patch** versions fix defects or optimize existing features without breaking changes.

Version numbers are presented `Major.Minor.Patch`, for example, `3.2.1`.

Once a versioned package has been released, the contents of that version must not be modified. Any modifications must be released as a new version.

The major version must be incremented for all breaking changes.

The minor version must be incremented if:

* New, backward-compatible functionality is introduced to the public specification.
* Any public specification functionality is marked as deprecated

The patch version must be reset to `0` when minor version is incremented


---

# Agent Instructions: 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:

```
GET https://governance.opendataproducts.org/v1/specification/versioning-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.