Skip to content

Bump Umbraco.Cms.DevelopmentMode.Backoffice from 17.3.4 to 17.4.0#176

Merged
alexsee merged 1 commit into
mainfrom
dependabot/nuget/UmbracoContainer/Umbraco.Cms.DevelopmentMode.Backoffice-17.4.0
May 21, 2026
Merged

Bump Umbraco.Cms.DevelopmentMode.Backoffice from 17.3.4 to 17.4.0#176
alexsee merged 1 commit into
mainfrom
dependabot/nuget/UmbracoContainer/Umbraco.Cms.DevelopmentMode.Backoffice-17.4.0

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 19, 2026

Updated Umbraco.Cms.DevelopmentMode.Backoffice from 17.3.4 to 17.4.0.

Release notes

Sourced from Umbraco.Cms.DevelopmentMode.Backoffice's releases.

17.4.0

Upgrade Notes

Be aware of a change to behaviour for detecting the Umbraco application URL. Previously, ApplicationMainUrl was automatically set from the Host header of incoming HTTP requests. In environments where Umbraco is not behind a reverse proxy that validates the Host header, this could allow a forged Host header to overwrite the URL used in password reset links, user invitations, and other email notifications. While this is normally mitigated by proper hosting configuration and setting UmbracoApplicationUrl explicitly, we felt that the auto-detection behaviour should be hardened up and become an opt-in rather than the default. You can read more about this under "Breaking Changes" below, the linked PR and the documentation.

There are a few updates related to performance in this release that are worth investigating for larger sites. Using output cache in your projects, with intelligent and customisable detection of page invalidation, is now a configuration option for templated websites, with extension points also applied for the Delivery API. We have optimised content cache rebuild after schema updates, with an option for deferred rebuild in the background. If considering a project with significant expected concurrency for member login and registration, and you prefer to use an external service for member management, the new option for lightweight external members will be worth reviewing.

If working with AI tools such as Umbraco MCP, additions to management API endpoints that expose JSON schema for data types and allow for patch updates of specific properties, should improve accuracy and reliability.

As usual please find the full list of PRs that have contributed to Umbraco 17.4 as follows.

What's Changed Since 17.4.0-rc3

Full Changelog: umbraco/Umbraco-CMS@release-17.4.0-rc3...release-17.4.0

What's Changed Since 17.4.0-r2

📦 Dependencies

🔒 Security

🐛 Bug Fixes

Full Changelog: umbraco/Umbraco-CMS@release-17.4.0-rc2...release-17.4.0-rc3

What's Changed Since 17.4.0-rc

🐛 Bug Fixes

Full Changelog: umbraco/Umbraco-CMS@release-17.4.0-rc...release-17.4.0-rc2

What's Changed Since the Previous Version (17.3.5)

🙌 Notable Changes

17.4.0-rc3

Upgrade Notes

Be aware of a change to behaviour for detecting the Umbraco application URL. Previously, ApplicationMainUrl was automatically set from the Host header of incoming HTTP requests. In environments where Umbraco is not behind a reverse proxy that validates the Host header, this could allow a forged Host header to overwrite the URL used in password reset links, user invitations, and other email notifications. While this is normally mitigated by proper hosting configuration and setting UmbracoApplicationUrl explicitly, we felt that the auto-detection behaviour should be hardened up and become an opt-in rather than the default. You can read more about this under "Breaking Changes" below, the linked PR and the documentation.

There are a few updates related to performance in this release that are worth investigating for larger sites. Using output cache in your projects, with intelligent and customisable detection of page invalidation, is now a configuration option for templated websites, with extension points also applied for the Delivery API. We have optimised content cache rebuild after schema updates, with an option for deferred rebuild in the background. If considering a project with significant expected concurrency for member login and registration, and you prefer to use an external service for member management, the new option for lightweight external members will be worth reviewing.

If working with AI tools such as Umbraco MCP, additions to management API endpoints that expose JSON schema for data types and allow for patch updates of specific properties, should improve accuracy and reliability.

As usual please find the full list of PRs that have contributed to Umbraco 17.4 as follows.

What's Changed Since 17.4.0-r2

📦 Dependencies

🔒 Security

🐛 Bug Fixes

Full Changelog: umbraco/Umbraco-CMS@release-17.4.0-rc2...release-17.4.0-rc3

What's Changed Since 17.4.0-rc

🐛 Bug Fixes

Full Changelog: umbraco/Umbraco-CMS@release-17.4.0-rc...release-17.4.0-rc2

What's Changed Since the Previous Version (17.3.5)

🙌 Notable Changes

... (truncated)

17.4.0-rc2

Upgrade Notes

Be aware of a change to behaviour for detecting the Umbraco application URL. Previously, ApplicationMainUrl was automatically set from the Host header of incoming HTTP requests. In environments where Umbraco is not behind a reverse proxy that validates the Host header, this could allow a forged Host header to overwrite the URL used in password reset links, user invitations, and other email notifications. While this is normally mitigated by proper hosting configuration and setting UmbracoApplicationUrl explicitly, we felt that the auto-detection behaviour should be hardened up and become an opt-in rather than the default. You can read more about this under "Breaking Changes" below, the linked PR and the documentation.

There are a few updates related to performance in this release that are worth investigating for larger sites. Using output cache in your projects, with intelligent and customisable detection of page invalidation, is now a configuration option for templated websites, with extension points also applied for the Delivery API. We have optimised content cache rebuild after schema updates, with an option for deferred rebuild in the background. If considering a project with significant expected concurrency for member login and registration, and you prefer to use an external service for member management, the new option for lightweight external members will be worth reviewing.

If working with AI tools such as Umbraco MCP, additions to management API endpoints that expose JSON schema for data types and allow for patch updates of specific properties, should improve accuracy and reliability.

As usual please find the full list of PRs that have contributed to Umbraco 17.4 as follows.

What's Changed Since 17.4.0-rc

🐛 Bug Fixes

Full Changelog: umbraco/Umbraco-CMS@release-17.4.0-rc...release-17.4.0-rc2

What's Changed Since the Previous Version (17.3.5)

🙌 Notable Changes

💥 Breaking Changes

📦 Dependencies

🚤 Performance

17.4.0-rc

Upgrade Notes

Be aware of a change to behaviour for detecting the Umbraco application URL. Previously, ApplicationMainUrl was automatically set from the Host header of incoming HTTP requests. In environments where Umbraco is not behind a reverse proxy that validates the Host header, this could allow a forged Host header to overwrite the URL used in password reset links, user invitations, and other email notifications. While this is normally mitigated by proper hosting configuration and setting UmbracoApplicationUrl explicitly, we felt that the auto-detection behaviour should be hardened up and become an opt-in rather than the default. You can read more about this under "Breaking Changes" below, the linked PR and the documentation.

There are a few updates related to performance in this release that are worth investigating for larger sites. Using output cache in your projects, with intelligent and customisable detection of page invalidation, is now a configuration option for templated websites, with extension points also applied for the Delivery API. We have optimised content cache rebuild after schema updates, with an option for deferred rebuild in the background. If considering a project with significant expected concurrency for member login and registration, and you prefer to use an external service for member management, the new option for lightweight external members will be worth reviewing.

If working with AI tools such as Umbraco MCP, additions to management API endpoints that expose JSON schema for data types and allow for patch updates of specific properties, should improve accuracy and reliability.

As usual please find the full list of PRs that have contributed to Umbraco 17.4 as follows.

What's Changed

🙌 Notable Changes

💥 Breaking Changes

📦 Dependencies

🚤 Performance

🌈 Accessibility Improvements

17.3.5

What's Changed

🐛 Bug Fixes

Full Changelog: umbraco/Umbraco-CMS@release-17.3.4...release-17.3.5

Commits viewable in compare view.

@dependabot dependabot Bot added .NET Pull requests that update .net code dependencies Pull requests that update a dependency file labels May 19, 2026
@alexsee
Copy link
Copy Markdown
Owner

alexsee commented May 21, 2026

@dependabot rebase

---
updated-dependencies:
- dependency-name: Umbraco.Cms.DevelopmentMode.Backoffice
  dependency-version: 17.4.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/nuget/UmbracoContainer/Umbraco.Cms.DevelopmentMode.Backoffice-17.4.0 branch from 98963c5 to ca5ce9b Compare May 21, 2026 20:23
@alexsee alexsee merged commit aafb1ef into main May 21, 2026
1 check passed
@alexsee alexsee deleted the dependabot/nuget/UmbracoContainer/Umbraco.Cms.DevelopmentMode.Backoffice-17.4.0 branch May 21, 2026 20:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file .NET Pull requests that update .net code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant