> For the complete documentation index, see [llms.txt](https://docs.umbraco.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.umbraco.com/sustainability-best-practices/backend/upgrades-and-patches.md). # Upgrades and patches Implementing upgrades and patches, such as migrating to Umbraco 10+, is highly advantageous from the standpoint of sustainable system design. Staying up-to-date with the latest software versions ensures that the system benefits from enhanced performance, security, and efficiency. Regular updates often include optimizations that reduce resource consumption and streamline processes, aligning with the principles of sustainable design by maximizing resource efficiency. Additionally, newer versions typically integrate eco-friendly features and improved coding practices, contributing to reduced energy consumption and minimized environmental impact. By proactively embracing upgrades and patches, organizations not only secure their systems against vulnerabilities. They also foster a more resilient, energy-efficient, and ecologically conscious technology landscape, which ultimately supports the long-term sustainability of their operations. --- # 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.umbraco.com/sustainability-best-practices/backend/upgrades-and-patches.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.