The Salesforce Release Cycle, Explained
Three releases a year arrive on a fixed rhythm — here’s how the schedule works and the short list of things worth watching in every one.
The Salesforce release cycle delivers three major releases a year — Spring (February), Summer (June), and Winter (October) — each rolled out to your org automatically over a set of release weekends. For every release, admins and developers should watch four things: Release Updates that auto-enforce, deprecations and retirements, new features worth enabling, and the sandbox preview window for testing before go-live.
How the Salesforce Release Cycle Works
Salesforce delivers three major seasonal releases every year: Spring, Summer, and Winter. They land in a predictable rhythm — Spring around February, Summer around June, and Winter around October — so the platform you administer is never more than a few months from its next upgrade. On top of the seasonal releases, some products now ship smaller updates on a monthly cadence.
Releases are named for the calendar year they carry you into, not the year they ship. Winter ’27 rolls out in October 2026; Spring ’27 follows in February 2027. If a release name looks a year ahead of the calendar, that’s why.
You don’t choose when the upgrade happens, and you can’t skip it — the platform refresh is automatic and applies to every org. What you can do is find out exactly when. Each release rolls out in phases across several release weekends, and your specific upgrade window depends on which instance your org runs on. The authoritative source is Salesforce Trust Status: open the Maintenances tab, look up your instance, and you’ll see your sandbox-preview and production upgrade dates, published months in advance.
The Preview Window: Test Before Go-Live
The single most valuable habit in the release cycle is testing the new version before it reaches production. Salesforce gives you two ways in, in order of how early they open:
- Pre-release org. A pre-release Developer Edition org is your earliest hands-on look at the new release — available before sandboxes are even upgraded. It’s ideal for exploring features and forming a plan.
- Sandbox preview. A few weeks before production, Salesforce upgrades preview-instance sandboxes to the new release. The gap between sandbox preview and production go-live is typically four to five weeks — your window to test customizations, integrations, and automations against real metadata.
One catch worth knowing: only sandboxes on a preview instance get the early upgrade, and that generally means sandboxes created or refreshed before the preview cutoff date. Miss the cutoff and your sandbox upgrades on the standard schedule — too late to preview the new release before it hits production.
Keep at least one preview-instance sandbox ready ahead of every cutoff. It’s the only way to confirm that release changes won’t break your org before they reach your users — and it’s far cheaper than firefighting in production on release weekend.
What to Watch Every Release
Each release brings hundreds of changes, but only a handful demand action. Four categories recur in every cycle — scan the release notes for these first:
| What to Watch | Why It Matters | Where to Find It |
|---|---|---|
| Release Updates | Behavior changes Salesforce auto-enforces by a target release. Ignore one and a customization can silently break on enforcement day. | Setup → Release Updates |
| Deprecations & retirements | Features reaching end of life or end of support, usually with a migration deadline attached. | Release notes + the feature’s Help article |
| New features (often off by default) | Many enhancements ship disabled and require you to opt in. Real value is left on the table if you never enable them. | Release notes, by product |
| Security enforcements | Increasingly shipped with hard deadlines, sometimes outside the normal seasonal cadence. | Release notes + security advisories |
Release Updates deserve the most attention. Salesforce flags them in advance — usually in the prior release’s notes — with a date when they flip from optional to enforced. Test each one in your preview sandbox before that date; once enforced, the new behavior applies whether you’re ready or not. For a release-by-release prep checklist and tips on reading the release notes efficiently, see the full Salesforce release readiness playbook.
The clearest current example: Workflow Rules and Process Builder reached end of support on December 31, 2025. They still run, but Salesforce no longer ships bug fixes or support for them, and the recommended path is migrating to Flow Builder with the Migrate to Flow tool. End of support isn’t end of operation — but it’s a clear signal to plan the move. (Salesforce Help: end of support.)
Admins and Developers Watch Different Things
The cycle is shared, but the watch-list splits by role.
For admins
Focus on Release Updates that touch declarative features, new clicks-not-code capabilities worth enabling, Setup and UI changes that affect end users, and any setting that flips from optional to default. The job is to enable the good and neutralize the disruptive before users notice either one.
For developers
Focus on retiring API versions — legacy SOAP, REST, and Bulk versions get sunset on a published schedule — plus Apex and Lightning Web Component behavior changes, governor or security-model adjustments, and managed-package compatibility. Run your test classes and integrations against the preview sandbox early: a behavior change that passes silently in one version can fail in the next.
Whichever lens applies to you, the discipline is the same — read the release notes for the four categories above, test in preview, and act before the enforcement dates rather than after them.
Test Your Knowledge
Drill release readiness, automation, and platform fundamentals with exam-style practice questions.
Going deeper? Salesforce publishes the cadence and prep guidance in the release schedule FAQ, the Trailhead Release Readiness Strategies module, and the Salesforce Admins release-countdown series.
Verified against official Salesforce Summer ’26 release resources and Help documentation. Release timing is instance-specific — confirm your dates on Salesforce Trust Status. Study smarter at CertifySF.com.