> 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/umbraco-cloud/release-notes/archive/overview-2025/2025-10-releasenotes.md).

# October 2025

## Key Takeaways

* **Daily Usage** - Gain daily insights into your project’s bandwidth trends over the last 31 days for a faster feedback loop and optimization.
* **CI/CD Improvements** - Deployments now complete faster when no changes are detected and include a verification step to ensure successful deployments.

## Daily Bandwidth Usage

A new **Daily Usage** graph is now available in the **Usage** section of Umbraco Cloud. It provides a rolling 31-day view of bandwidth usage, giving you faster feedback on the effects of site optimizations and improved predictability.

![Rolling Bandwidth Trend of last 31 days](https://3739769070-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPzKn70Piyd2fd5UkYZGf%2Fuploads%2Fgit-blob-980fa8044030a2334991c68ae7d5d5ca0fbf7f92%2FDaily-Usage-Bandwidth-Trend-October-2025.png?alt=media)

For instance, you can now see the impact of reducing image sizes, disabling autoplay videos, or improving caching strategies. This makes it easier to understand how adjustments influence bandwidth consumption day by day.

## CI/CD Improvements

Made updates to the CI/CD flow to improve speed, reliability, and transparency during deployments.

* **Faster completion for unchanged deployments**: If your uploaded package has no new changes affecting the Cloud Environment, the CI/CD job skips unnecessary steps. This makes deployments complete faster.
* **New verification step for deployment completion**: A new verification step ensures that changes pushed to the App Service have been successfully deployed through Kudu.

These improvements make the deployment flow faster, more predictable, and easier to troubleshoot. See the documentation for more details:

* [Deployment reports: No changes detected - cleaning up](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md#deployment-reports-no-changes-detected---cleaning-up)
* [Unable to verify Deployment has finished](/umbraco-cloud/build-and-customize-your-solution/handle-deployments-and-environments/umbraco-cicd/troubleshooting.md#unable-to-verify-deployment-has-finished)


---

# 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/umbraco-cloud/release-notes/archive/overview-2025/2025-10-releasenotes.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.
