> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/sb-ed-releases/release-sb-7.5.md). # Release - SB 7.5 Sunbird Release 7.5 is live as of January 2025 The release tag for Sunbird 7.5 is now available on GitHub:\ \
The highlight of this release is the Sunbird ED Easy Installer - which allows for a 'single-click' installation of Sunbird Ed, bringing togehter all the dependent components that need to be installed under a single script. Going forward, future releases of Sunbird will support only the easy installer, and the older way of installing Sunbird will be deprecated. Jira links to related issues: [SB Ed Ease of Installation](https://project-sunbird.atlassian.net/jira/software/c/projects/SBCOSS/issues/?filter=allissues\&jql=project%20%3D%20%22SBCOSS%22%20AND%20parent%20%3D%20SBCOSS-41%20AND%20status%20%3D%20Done%20ORDER%20BY%20created%20DESC) [SB Ed Ease of Configuration](https://project-sunbird.atlassian.net/jira/software/c/projects/SBCOSS/issues/?filter=allissues\&jql=project%20%3D%20%22SBCOSS%22%20AND%20parent%20%3D%20SBCOSS-209%20AND%20status%20%3D%20Done%20ORDER%20BY%20created%20DESC) Form and configuration-related documentation is available [here](https://www.postman.com/sunbird-building-blocks/sunbird-ed-coss/collection/yo5s61t/sunbird-ed-forms) \
--- # 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://ed.sunbird.org/sb-ed-releases/release-sb-7.5.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.