# Release History
## Versioning Schema
BoxLang is maintained under the [Semantic Versioning](http://semver.org/) guidelines as much as possible. Releases will be numbered in the following format:
```
..
```
And constructed with the following guidelines:
* Breaking backward compatibility bumps the major (and resets the minor and patch)
* New additions without breaking backward compatibility bump the minor (and resets the patch)
* Bug fixes and misc changes bump the patch
## BoxLang Release & Support Lifecycle
Our release cadence follows a predictable yearly major-version schedule, with each release enjoying two years of Long-Term Support (LTS):
* **Active Support**: First 12 months after release – full feature updates, bug fixes & security patches.
* **LTS (Updates & Security)**: 2nd year – maintenance releases (minor improvements & security).
* **LTS (Security-Only)**: 3rd year – critical security fixes only, then archived.
This gives you a clear planning horizon and overlap between versions, so you can upgrade on your own schedule without ever being left unprotected.
### Support Lifecycle Chart
Here is our 5-year outlook.
Version
Active Support
LTS (updates & security)
LTS (security-only)
v1
2025 – 2026
2026 – 2027
2027 – 2028
v2
2026 – 2027
2027 – 2028
2028 – 2029
v3
2027 – 2028
2028 – 2029
2029 – 2030
v4
2028 – 2029
2029 – 2030
2030 – 2031
v5
2029 – 2030
2030 – 2031
2031 – 2032
* After the “security-only” phase, the version is **archived**: no further updates, but archives remain available for reference.
* Overlaps ensure there’s always at least one actively maintained release.
* All dates refer to calendar years; exact dates will align with our annual major-version launch each Q1.
---
# 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://boxlang.ortusbooks.com/readme/release-history.md?ask=
```
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.