> For the complete documentation index, see [llms.txt](https://docs.goldenedi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.goldenedi.com/releases/versions.md). # Releases Release notes for Golden EDI This page describes changes in the public releases of Golden EDI. We aim to keep this up-to-date with every release made to AppSource. Private releases or releases made to OnPrem environments do not necessarily reflect what is described here but in most cases it is the sames features and changes. #### New Versioning Scheme: AL-Go Standard (Effective from Version 23.0.5.0) Starting from version 23.0.5.0, we've adopted the AL-Go standard for our versioning scheme. This new standard means that the version number you see will solely refer to our Golden EDI version and will no longer indicate the compatible Business Central version. In the AL-Go system, the first two numbers represent major and minor changes, while the last two are for automatic revisions. **Old Versioning Scheme (Before 23.0.5.0)** Before transitioning to the AL-Go standard, our versioning had a different methodology. In this old scheme, we only referred to the "Golden EDI version," which consisted of the three last numbers in the version number as visible in the application. {% hint style="info" %} For example, an app with version 20.4.7.5 meant it was version 4.0.0 validated against Business Central 20 and forward. The Business Central version in the version number was considered the minimal supported version. Older versions of Business Central might have been compatible, but they were not tested. {% endhint %} ### Numbering The numbering of our versions aims for clarity. The first two numbers indicate major and minor changes respectively, while the last two numbers are for automatic revisions based on various factors such as bug fixes and small adjustments. * **Major Changes**: These are changes that may not necessarily alter how you interact with Golden EDI on a daily basis but can include significant internal upgrades. Such upgrades are aimed at improving system performance, ensuring long-term compatibility, and other foundational improvements that better the overall quality and stability of the product. * **Minor Changes**: These are more targeted improvements that enhance functionality without significantly altering your daily operations with Golden EDI. ### Backwards Compatibility We are committed to ensuring that our releases, both big and small, remain backward compatible with older setups and configurations. So go ahead, make that version leap; your configurations should function just as smoothly as before! --- # 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://docs.goldenedi.com/releases/versions.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.