> For the complete documentation index, see [llms.txt](https://bxorm.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://bxorm.ortusbooks.com/bxorm-2.x/release-history.md). # Release History Release history for all bx-orm versions In this section, you will find the release notes for each version we release under this major version. If you are looking for the release notes of previous major versions, use the version switcher at the top left of this documentation book. Here is a breakdown of our major version releases. ## v2.x bx-orm 2 runs on Hibernate ORM 7.4. It adds fluent criteria queries, `orm.*` errors, a boot cache for fast production starts, entities as structs and much more. * [What's New in 2.0.0](/bxorm-2.x/release-history/whats-new-2.0.0.md): the tour of new features. * [Upgrading to 2.0.0](/bxorm-2.x/release-history/upgrading-to-2.0.0.md): the checklist to move a 1.x application. * [2.x release notes](/bxorm-2.x/release-history/2x.md): every change, release by release. ## v1.x The 1.x release notes live in the BXORM 1.x documentation space. --- # 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://bxorm.ortusbooks.com/bxorm-2.x/release-history.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.