Salesforce periodically provides release updates that improve the performance, logic, security, and usability of our products. The Release Updates page provides a list of updates that can be necessary for your organization to enable. Some release updates affect existing customizations.
Every time a release update is created, it gets scheduled to be enforced in a future release. We announce each update and its schedule here as soon as that schedule is known, but occasionally, updates are postponed or canceled. If that happens, we let you know in the section that describes that specific release update.
Often, release updates provide a Test Run option so you can enable an update and examine any changes to your org, including changes to customizations, before that update’s Complete Steps By date. You can view attachments in the Salesforce mobile app, but you can’t edit them.
To view release updates, from Setup, in the Quick Find box, enter Release Updates, and select Release Updates.
Enforced with This Release
These updates are scheduled to be enforced this release.
- Escape the Label Attribute of <apex:inputField> Elements to Prevent Cross-Site Scripting in Visualforce Pages (Release Update)
- To prevent malicious code from executing in cross-site scripting (XSS) attacks on your
Visualforce pages, this release update escapes the label attribute of your
<apex:inputField>tags. First available in Spring ’23, this update is enforced in Spring ’26. - Update References to Legacy Host Names (Release Update)
- Prevent disruption for your customers and end users when the temporary redirection of legacy (non-enhanced) Salesforce host names ends. With this release update, those redirections end in all orgs. First available in Spring ’25, this update is enforced in Spring ’26.
Scheduled to Be Enforced in Summer ’26
These updates are scheduled to be enforced in Summer ’26. The list can include new, previously announced, and previously postponed release updates.
- Enable Accessibility Enhancements for Date Pickers, Popovers, Bottom Utility Bars, Record Headers (Release Update)
- To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of date pickers, popovers, bottom utility bars, and record headers when viewed at high magnification. This release update is dependent on the Enable Accessibility Enhancements for Page Headers and Modal Windows When Zoom Is Greater Than 200% release update.
- Enable Accessibility Enhancements for Page Headers and Modal Windows When Zoom Is Greater Than 200% (Release Update)
- To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of page headers and modal windows when viewed at high magnification. This is the beginning of our effort to comply with WCAG 2.2 Resize and Reflow guidelines.
- Migrate to a Multiple-Configuration SAML Framework (Release Update)
- If you see this release update, your Salesforce instance is using our original single-configuration SAML framework, which supports single sign-on (SSO) with only one identity provider. We’re giving you a final reminder that with the Summer ’26 release, we’re no longer supporting the single-configuration SAML framework. To make sure that your SSO configurations don’t break, migrate to our newer multiple-configuration SAML framework, which supports SSO with multiple identity providers instead of just one. If you don't migrate, your SAML single sign-on configurations will stop working when this release update is enforced in Summer ’26.
- Salesforce-Managed X (Formerly Twitter) Authentication Provider Retirement (Release Update)
- The Salesforce-managed app for the X (formerly Twitter) authentication provider is being retired. This update breaks any single sign-on (SSO) configurations that use the Salesforce-managed X app. To avoid disruptions, create a custom X app and update your SSO configurations.
- Use Visualforce PDF Rendering Service with Apex Blob.toPdf() (Release Update)
- With this update enabled, the Apex
Blob.toPdf()method for PDF rendering uses the same rendering service as Visualforce. The Visualforce PDF rendering service offers improvements such as additional fonts and multibyte character support. This change makes PDF rendering more consistent on the Salesforce Platform.
Scheduled to Be Enforced in Winter ’27
These updates are scheduled to be enforced in Winter ’27. The list can include new, previously announced, and previously postponed release updates.
- Adopt Authorized Email Domains (Release Update)
- If you previously worked with Salesforce Customer Support to disable email change verifications, set up authorized email domains instead. Salesforce is retiring the existing exemption process for disabling this feature, and authorized email domains provide the same benefit.
- Enable Accessibility Enhancements for Cards, Docked Containers, Menu Lists, and Panels (Release Update)
- To help meet Web Content Accessibility Guidelines (WCAG) 2.2 for Resize and Reflow, enable Lightning Experience to adapt the behavior of cards, docked containers, menu lists, and panels when viewed at high magnification. This release update is dependent on the Enable Accessibility Enhancements for Page Headers and Modal Windows When Zoom Is Greater Than 200% release update.
- Retirement of OAuth 2.0 Username-Password Flow for Connected Apps (Release Update)
- In Winter ’27, we'll stop supporting the OAuth 2.0 username-password flow for connected apps. This update will break all connected app integrations that use this flow. For better security, update your integrations to use the OAuth 2.0 web-server flow or the OAuth 2.0 client credentials flow instead.
- Update Instanced URLs in API Traffic (Release Update)
- To prevent disruption when Salesforce ends support for API traffic that uses an incorrect instanced URL, make sure that API traffic to your org uses the org’s My Domain login URL. First available in Summer ’25, this release update was scheduled to be enforced in Spring ’26, but we postponed the enforcement to Winter ’27.
Scheduled to Be Enforced in Spring ’27
These updates are scheduled to be enforced in Spring ’27. The list can include new, previously announced, and previously postponed release updates.
- Salesforce to Salesforce Is Being Retired (Release Update)
- Salesforce to Salesforce is being retired in Spring ’27. Salesforce has more powerful and integrated solutions that align with modern business needs. To prevent disruption when Salesforce ends support for the Salesforce to Salesforce product, make sure that you migrate your integrations to one of these recommended solutions: Partner Cloud, Data Cloud One, MuleSoft Anypoint, or MuleSoft for Flow.
- Update Apex Code and Flows for Changed Sharing Recalculation Behavior (Release Update)
- To optimize performance after large-scale updates to groups or roles, Salesforce now performs some sharing recalculations asynchronously. If Apex code and flows require that share records be updated immediately, the code and flows can break when this release update is enforced. Update Apex classes, tests, and flows that update group membership or roles if they rely on synchronous sharing recalculation. This update is available starting in Spring ’26.
Scheduled to Be Enforced in Summer ’27
These updates are scheduled to be enforced in Summer ’27. The list can include new, previously announced, and previously postponed release updates.
- SOAP API login() Call in SOAP API Versions 31.0 Through 64.0 Is Being Retired (Release Update)
- In Summer ‘27, the SOAP API login() call in SOAP API versions 31.0 through 64.0 will no longer be supported and no longer be available.