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

# Release History

## Version 7.0

This major update has a bunch of performance updates, and more activity logs to keep track of all the actions you perform via CommandBox and the ForgeBox UI. We have made a big change to our search engine and introduced **Elastic Search** as the default search engine which provides better and more accurate results when searching on the site or using our search endpoint.

## Version 6.0

Version 6 has been a major undertaking spawning several months worth of work, a complete UI revamp for registered users, many bug fixes, multi-key API, and much more. We have also introduced our new **Business Accounts** (<https://forgebox.io/plans>) with the ability for organizations to have a simple and human way of managing their final package releases and their teams.


---

# 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://forgebox.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.