> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/configurations/hotfix-configurations/track-hotfixes-via-patch-version-pattern.md).

# Track hotfixes via patch version pattern

Any merged Pull Requests (PRs) with a PR title, Source branch, or PR tags containing a version number in the format **a.b.c...z** (where **z > 0**) can be identified as a hotfix.

#### Example

* `1.2.3 →` last number = 3 → hotfix
* `2.0.0.0 →` last number = 0 → not a hotfix
* `5.4.1.0.6 →` last number = 6 → hotfix

### **Steps to Enable the Hotfix Flag** <a href="#h_01hywpdm3j2gk2m1v3k6scx17a" id="h_01hywpdm3j2gk2m1v3k6scx17a"></a>

To start using this new hotfix pattern, you need to enable the corresponding flag in your organization's configuration settings. Follow these steps:

1. Navigate to the Configurations page within your Hivel dashboard.
2. Find the flag related to the new hotfix pattern. It will be listed among the available configuration options.
3. Switch the flag to "On" to enable the new hotfix pattern.

<div data-with-frame="true"><figure><img src="/files/Zd5KScBiiCpdzPeEl2Jj" alt="" width="563"><figcaption></figcaption></figure></div>

Once the flag is enabled, the system will automatically recognize any merged PRs with a version number in the format as hotfixes.

All current hotfix patterns will continue to function without interruption. Both the new and existing hotfix patterns will be recognized for calculation of "Hotfifx Rate" and "Hotfix Resolution Rate" metrics.

For any further assistance or if you encounter issues, please contact our support team at [<mark style="color:purple;">support@hivel.ai</mark>](mailto:support@hivel.ai).


---

# 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.hivel.ai/configurations/hotfix-configurations/track-hotfixes-via-patch-version-pattern.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.