Blend Developer Guide

Upgrade Checklist

  • Page Owner: Not Set
  • Last Reviewed: 2025-10-09
  • Make sure CMS is updated to latest minor version
  • Check installed Nuget packages for any vulnerabilities or deprecations. If a critical vulnerability is found, let the dev and PM teams know so other projects can be checked.
  • Make sure Sentry integration is using the latest Blend package.
  • Follow the instructions in the Readme. Make sure you're using the latest minor version in Nuget.
  • Remove Blend.Sentry if installed.
  • Add BlendInterative.Sentry for CMS 12, or just use Sentry directly for full framework sites.
  • Make sure the Slackbot integration is doing the following:
  • Report on build success/failure, who requested the build
  • Report when release deployment is complete
  • Ask for help if not comfortable editing deployment pipelines
  • Check the Sentry project for any weird errors that may need investigation. Look for errors that are occurring a lot and are not accounted for. If there's nuisance error that can be safely ignore, add it to the Sentry config to prevent it from filling up our error logs.
  • Make sure Terser is not including sourcemaps inline:
  • Do not include the toplevel: true bit of code.
  • Check for any hard-coded secrets in source code.
  • Search the entire project for keywords like "key", "secret", and "auth", and glance through the search results looking for anything that looks like a secret or API key.
  • Move those secrets to a configuration file.
  • For sensitive secrets on systems that support it, remove the key entirely from any committed configuration, and store the key in secure mechanism on the server instead (such as the App Settings tab in the PAAS Portal for Optimizely sites)
  • If a secret has been removed from a project, let the rest of the team know that they'll need to update their personal, non-committed configuration files going forward.
  • Remove x-xss-protection header if exists
  • Opti CMS 12:
  • In 2024, update Azure pipeline to dotnet 8, update project to dotnet 8
  • Do not install 1.6.0 of EPiServer.CloudPlatform.Cms or EPiServer.Cms.Warmup. The warmup package has a bug that has the potential to bring down the site on PROD
  • Upgrade Redirect Manager to latest version
  • Upgrade Azure.Extensions.AspNetCore.DataProtection.Blobs and Azure.Extensions.AspNetCore.DataProtection.Keys packages to the latest versions.
  • Upgrade controllers to Async as necessary for S&N update (within the allotted time)
  • Umbraco 13:
  • In 2024, update Azure pipeline to dotnet 8, update project to dotnet 8
  • Verify Developer specific configs are enabled in Umbraco and CMS12
  • Opti
  • Umbraco
  • Ignore from git