> For the complete documentation index, see [llms.txt](https://coldbox-orm.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-orm.ortusbooks.com/v5.x/intro/release-history/whats-new-with-4.10.0.md). # What's New With 4.10.0 What's new in CBOrm 4.10.0 CBOrm 4.10.0 focuses on Adobe ColdFusion 2025 support and enhanced BoxLang compatibility. ## Added ### Platform Support * **Adobe ColdFusion 2025 Certification**: Full support and testing for Adobe ColdFusion 2025 * **BoxLang BE Tests**: Enhanced test coverage for BoxLang Bleeding Edge builds ## Fixed ### Performance & Concurrency * **Restrictions Concurrency Fix**: Resolved a critical concurrency issue where restrictions could overlap under high-load scenarios, ensuring thread-safe operation in production environments ## Release Date June 3, 2025 --- # 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-orm.ortusbooks.com/v5.x/intro/release-history/whats-new-with-4.10.0.md?ask=&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.