Release Updates is managed from a single Setup page. The goal of the workflow is to review every update that applies to your org, validate it in a preview sandbox, and address anything that fails before the enforcement date. Do this once per major release.
- Open the Release Updates page
From Setup, enter Release Updates in the Quick Find box and select it. The page lists updates relevant to your org with a status, an impact summary, and an enforcement release for each item.
- Sort by enforcement date
Work the items with the nearest enforcement dates first. Open each card to read the full description and the steps Salesforce recommends so you understand what the change touches.
- Test Run in a preview sandbox
Use the Test Run or Test Now action in a sandbox upgraded with the upcoming release. Click through affected flows, run your Apex tests, and confirm integrations behave under the changed rules.
- Fix what fails, then re-test
Treat a failed Test Run as a finding. Adjust the configuration or code, deploy the fix to the sandbox, and run the test again until it passes cleanly.
- Apply or let it enforce
Once testing passes, apply the update on your own schedule so the change lands while your team is watching, or let the platform enforce it on the published date.
Shows whether an update is ready to test, in progress, or already applied or enforced, so the page works as a release checklist.
The release in which the change becomes mandatory. Plan your testing backward from this date for each item.
Activates the updated behavior so you can observe its effect before committing, ideally in a preview sandbox.
Explains what is changing and why, plus the steps Salesforce recommends to prepare. Read this before deciding the item applies to you.
- Run Test Now in a sandbox upgraded with the upcoming release, not in production, so you are testing the real new behavior against a safe copy.
- Do not skip the page for several releases. Untested updates can stack up and all enforce at once, which is the pile up the page exists to prevent.
- Enforcement dates can be instance specific, so confirm your timeline against your instance Trust status rather than assuming a single global date.
- Release Updates cover behavior changes that can break existing work. They are not the same as opt in new features in the release notes, so review them with more care.