Salesforce
Salesforce Release Cycle: Dates, Sandbox Preview and QA

Rishabh Kumar
Published On

Table of contents
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
Lorem ipsum
What is the Salesforce Release Cycle?
Salesforce upgrades every customer org three times a year, in releases named Spring, Summer and Winter. Each release reaches preview sandboxes first, then rolls out to production instances over several weekends spread across about six weeks. You can't skip a release or stay on an old one. Every org moves forward together.
For QA teams, that makes the release cycle the single most predictable source of risk in Salesforce. The dates are published, the changes are documented, and the testing window is fixed. The teams that cope well treat each release as a scheduled project with a start, a test plan, a sign-off and evidence at the end. The teams that struggle treat it as weather.
This guide explains how the cycle works, what a release actually changes, and how to build a testing rhythm around it.
When Are Salesforce's Spring, Summer and Winter Releases?
Salesforce names each release after the season it's planned for, and labels it with the year that season falls in. That's why Winter '27 arrived in the autumn of 2026. Winter starts before the calendar year turns.
Release | Sandbox Preview Usually Starts | Production Usually Lands | Most Recent Example |
|---|---|---|---|
Spring | Early January | January to February, over several weekends | Spring '26 had preview from 9 January 2026, and production on 16 January, 13 February and 20 February 2026 |
Summer | Early May | May to June | Summer '26 had preview from 8 May 2026, and production on 15 May, 5 June, 12 June and 13 June 2026 |
Winter | Late August | September to October | Winter '27 had preview from 28 August 2026, and production on 4 September, 2 October and 9 October 2026 |
Two details matter more than the headline dates.
First, your org's upgrade date depends on its instance, so two orgs in the same company can move on different weekends. Your instance's date is on the Salesforce Trust status site.
Second, your real testing window runs from the start of preview to your own instance's production weekend. Look at the dates again.
The first production wave lands about a week after preview begins, and the last about six weeks after. An org on an early instance gets one week. An org on a late instance gets six. Know which one you are before you plan anything.

What Happens During a Salesforce Release?
Every Salesforce release follows the same sequence of milestones. Learn it once, and every future release becomes easier to plan.
Release Notes Publish
Salesforce posts preview release notes a few weeks before sandboxes upgrade. They're long, organised by cloud and feature area, and they keep changing until the release is live. Read them as a draft.
Pre-Release Orgs Open
Salesforce spins up fresh trial orgs on the new release before the sandbox preview. They're useful for exploring new features, but they hold none of your configuration, so they tell you nothing about your own org.
The Sandbox Preview Decision
Every sandbox sits on either a preview instance or a non-preview instance. Salesforce's Sandbox Preview Guide tells you which, and what to do to change it. In practice, that means refreshing a sandbox before a cut-off, usually early evening Pacific Time on the day before preview begins.
Sandbox Preview Begins
Sandboxes on preview instances upgrade to the new release. This is the moment your regression suite should run against your own metadata, data and integrations.
Production Weekends
Production instances upgrade in waves over several weekends. Your instance's date is on the Trust status site.
Release Updates Enforce
Alongside the release, Salesforce turns on release updates that were optional until now. Each has its own enforcement date, published in Setup on the Release Updates page.
Steps three and four are where most teams lose time. Miss the refresh cut-off and you may have no sandbox on the new release at all, which means testing in production by default.
Running a full regression on the first day of preview is only realistic if it's automated, and our guide to test automation for Salesforce covers how to get there.
What Does a Salesforce Release Change?
Most of a Salesforce release is new capability that stays switched off until an admin turns it on. That part rarely breaks anything. The changes that break journeys and tests fall into six groups.
Change Type | What Happens | Why It Matters for Testing |
|---|---|---|
Behaviour changes to existing features | Something you already use works differently after the upgrade | Journeys can fail with no change on your side |
Release updates | Changes Salesforce first offers as optional, then enforces on a published date | Many support a test run, so you can switch them on in a sandbox before they become mandatory |
User interface and theme changes | Layout, styling or component internals shift, with SLDS 2 and the Cosmos theme as the current example | UI tests that depend on page structure can fail even when the journey still works |
Lightning Web Components framework changes | The platform moves components between synthetic shadow, native shadow and light DOM | How a test reaches an element can change between releases |
Security and session changes | Stricter defaults on authentication, redirects, content security or permissions | Sign-in, single sign-on, embedded content and integrations are the usual casualties |
Agentforce and AI changes | New agent capabilities, models or default behaviours | Agent responses can shift even when topics and actions are unchanged |
The Lightning Web Components row is the one that catches most automated suites out, and our guide to LWC testing explains how to test components that move between shadow DOM modes.

Two sources of change sit outside the Salesforce release entirely. AppExchange packages update on their vendors' own schedules. Connected systems, from your ERP to your e-signature provider, change on theirs. A release test that only looks at the org misses both.
Why is the Salesforce Release Cadence Hard for QA Teams?
Three releases a year sounds manageable. The difficulty isn't the number. It's what happens during each window.
You Run Two Versions of Salesforce at Once
From the start of preview until your production weekend, your preview sandboxes run the next release while production runs the current one.
A fix built and tested in a preview sandbox is tested on a version production doesn't have yet. A bug reported in production may not reproduce in a sandbox that has already moved on.
Most teams keep at least one sandbox on the non-preview track for exactly this reason.
Your Own Work Doesn't Stop
Sprints keep shipping through the preview window. Every deployment during that period has to be tested against both versions, or held back.
The Window is Short and Fixed
If your instance upgrades on the first wave, you may have a week. Manual regression of a customised org rarely fits in a week, and a test suite that needs days of repair after every release doesn't fit either.
Nobody Signs Off a Dashboard
When something goes wrong after a release, the first question is what was tested. Teams that can only answer with a pass rate have no answer at all. This is the gap Release Evidence names. Release Evidence is the standard of proof for software releases, showing what was tested, why, and who decided.
Part of that answer comes from the business, not QA, which is why a short round of Salesforce user acceptance testing belongs in every release window.
What Does This Mean for Your Regression Suite?
The release cycle sets the rhythm your regression suite has to keep. Plan backwards from your own production weekend, not from the preview date, and treat every release as a scheduled project with a start, a test run and a sign-off.
Know your instance's production weekend before release notes publish, because early instances leave about one week.
Put a production-like sandbox on the preview track before the refresh cut-off, and keep one off it for hotfixes.
Run the full end-to-end suite on the first day of preview, not only the journeys the release notes mention.
Test release updates with their test runs switched on, while enforcement is still optional.
Record what was tested, on which version, and who signed off, every release.
Those five habits sit within a wider set of Salesforce testing best practices that keep a suite healthy between releases too. What to rerun, and in what order, once preview opens is covered in our guide to regression testing in Salesforce.
Virtuoso QA's Salesforce test automation runs your full Lightning regression in plain English on day one of preview, proposes fixes your team approves when the release changes a component, and records what each release was tested against and who signed it off.
Frequently Asked Questions
How many releases does Salesforce have a year?
Why is Winter '27 released in 2026?
When is the Salesforce Spring '27 release?
Can I skip or delay a Salesforce release?
How long is the Salesforce sandbox preview?
Where do I find my org's release date?
Written by

Rishabh Kumar
AI Testing & Quality Engineering Contributor
Rishabh leads business development and marketing at Virtuoso QA. He writes about AI-powered test automation, end-to-end testing, self-healing tests, and quality engineering, exploring how these capabilities can improve test coverage, reduce test maintenance, and support reliable software releases.







