> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/cloud/web-interface/help-and-tools/release-news.md). # Release news Consult Devolutions Cloud release notes, latest update summaries, and product insights, and configure when release news notifications appear. In ***Help & tools***, consult ***Release notes***, see a summary of ***What's new*** in the latest Devolutions Cloud versions, and consult practical ***Product insights***. ### Release notes In the ***Release notes*** page, see new relevant features, improvements, and fixes added to Devolutions Cloud in the latest versions. ### What's new In the ***What's new*** page, read a summary of the latest features, improvements, and fixes added to Devolutions Cloud in the most recent release. ### Product insights In the ***Product insights*** page, consult practical articles that explain key concepts, highlight new capabilities, and show how to get real-world results with Devolutions products. ### Settings Clicking on ***Dismiss release news*** at the bottom of the page makes the page close and the Release News icon disappear from the top bar. If you click on the settings icon, you can choose to show the ***Release news*** each time a new version of Devolutions Cloud is released, or to not show them at all. This setting is applied to both ***Release notes*** and ***What's new*** pages. You can also set the same option via your ***Preferences*** in the account menu. --- # 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.devolutions.net/cloud/web-interface/help-and-tools/release-news.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.