> For the complete documentation index, see [llms.txt](https://coldbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coldbox.ortusbooks.com/release-history.md).

# Release History

All the major information about ColdBox Releases

## Versioning Schema

ColdBox is maintained under the [Semantic Versioning](http://semver.org) guidelines as much as possible. Releases will be numbered in the following format:

```
<major>.<minor>.<patch>
```

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

## LTS - Support Policy

For all ColdBox releases, updates are provided for 12 months, and security fixes are provided for 2 years after the next major release.

| Version | Release | Updates | Security Fixes |
| ------- | ------- | ------- | -------------- |
| 9.x     | 2027    | 2029    | 2030           |
| **8.x** | 2025    | 2027    | 2028           |
| 7.x     | 2023    | 2024    | 2026           |
| 6.x     | 2022    | 2023    | 2025           |

If you need professional support, please contact [Ortus Solutions](https://www.ortussolutions.com/services/support).

## Releases

In this section, you will find the release notes and links for each version's documentation. If you are looking for the release notes of previous major versions, use the version switcher at the top left of this documentation book.

* [Version 8.3.0](/release-history/whats-new-with-8.3.0.md): browser testing with `@browser`, `Router.registerMiddleware()`, group route `meta`, route middleware in integration tests, thread-safe WireBox scope wiring, and implicit views disabled by default
* [Version 8.2.0 - September 2026](/release-history/whats-new-with-8.2.0.md): route-scoped middleware, HTTP caching primitives, Server-Sent Events and AI gateway routing
* [Version 8.1.0 - April 2026](/release-history/whats-new-with-8.1.0.md): AI and MCP routing with `toAi()` and `toMCP()`
* [Version 8.0.0 - October 2025](/release-history/whats-new-with-8.0.0.md): major release with BX-ColdBox and ColdBox BoxLang PRIME, new application templates and virtual thread executors
* [Version 7.0 - May 2023](https://coldbox.ortusbooks.com/v/v7.x/intro/release-history/whats-new-with-7.0.0)
* [Version 6.0 - August 2020](https://coldbox.ortusbooks.com/v/v6.x/intro/release-history/whats-new-with-6.0.0)
* [Version 5.0 - July 2018](https://coldbox.ortusbooks.com/v/v5.x/intro/introduction/whats-new-with-5.0.0)
* [Version 4.0 - January 2015](https://coldbox.ortusbooks.com/v/v4.x/intro/introduction/whats-new-with-4.0.0)
* Version 3.0 - March 2011
* Version 2.0 - April 2007
* Version 1.0 - June 2006


---

# 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://coldbox.ortusbooks.com/release-history.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.