Microsoft has quietly reshuffled its SharePoint Framework release calendar, moving the SPFx 1.24 general availability milestone from June to September 2026—the same window that, until recently, was reserved for version 1.25. The revision, published in the official SPFx roadmap in July, means that the upcoming September update will now be the release that essentially ends support for the Gulp-based build toolchain, forcing organizations to prioritize migrations of their most critical custom SharePoint solutions to the Heft build system.
What the Roadmap Revision Changes
The May 2026 roadmap laid out a clear sequence: SPFx 1.23 (released May 13), 1.23.1 in June, 1.24 in June with a public preview of an undisclosed feature, and 1.25 in September bringing navigation customizers, SPFx CLI general availability, and the culmination of the Heft transition. Teams naturally anchored their planning around the September deadline being tied to version 1.25.
That timeline is now obsolete. The July 2026 roadmap update places SPFx 1.24 GA squarely in September. The release now bundles SharePoint Copilot Apps GA, SPFx CLI GA, navigation customizers, updated open-source templates, and continued npm dependency-security work—plus the formal end of Gulp as a supported build system. Microsoft’s published toolchain guidance is unambiguous: Gulp-based projects will still compile, but future fixes, security patches, and tooling improvements will target Heft exclusively.
For teams that counted on a full development cycle between the June preview and a September 1.25 release, the revised schedule collapses that buffer. The practical support boundary is now SPFx 1.24 GA, not some later version, and it lands in September 2026.
Who Needs to Act Now, and Who Can Wait
Not every SPFx solution demands a frantic migration sprint. The most dangerous error would be treating this as a uniform “upgrade everything” mandate. Instead, categorize every deployed project into three tiers:
- Urgent migration candidates: Web parts, extensions, or command sets with custom Gulp tasks, webpack overrides, bespoke build logic, or critical CI integrations that call Gulp directly. These pipelines cannot simply be lifted to Heft; they require redesign. Business-critical solutions—supporting finance, HR, operations, or intranet publishing—that belong here must jump to the front of the queue.
- Cautious, but not immediate: Standard web parts with no custom Gulp tasks, straightforward project structures, and a reproducible build. If these solutions are not mission-critical and have a low release cadence, they can be scheduled behind the urgent tier, but teams should still run a Heft pilot to gauge effort.
- Low risk / deferrable: Small, seldom-updated components that have never been customized and lack complex CI dependencies. For these, a documented ownership and a planned retirement or migration date may suffice in the short term, but leaving them on Gulp indefinitely is not sustainable.
The acid test: If a toolchain issue forces an emergency rebuild two years from now, and the original developers are no longer available, can the team reproduce the build and trust the output? If the answer is even slightly uncertain, that project belongs in the urgent bucket.
What a Heft Migration Actually Involves
A conventional SPFx version upgrade is largely about aligning package versions and handling any application-level breaking changes. A Gulp-to-Heft migration is a different beast—it replaces the machinery that turns source code into a deployable package. Custom gulpfile logic, build tasks, webpack modifications, old config.json patterns, and CI scripts that assume Gulp-generated artifacts all need to be reimagined for Heft’s architecture.
A solid migration test must answer four operational questions:
- Can a clean workstation produce a production-quality build without undocumented local fixes?
- Does the new build generate the exact package and assets the organization’s deployment path expects?
- Does the CI system execute the Heft toolchain without relapsing into direct Gulp calls or legacy artifact assumptions?
- Can the team diagnose a failed production build when the original Gulp authors are gone?
A “yes” to each question is the only safe sign-off. Otherwise, the migration is not a one-sprint maintenance task; it’s a modernization project that deserves dedicated time and testing.
This transition is also an opportunity to prune unnecessary build complexity. A ten-year-old asset copy task or webpack override might be obsolete. Retaining every historical behavior without scrutiny just converts legacy technical debt into a newer format.
How We Got to This Point: The Slow Sunset of Gulp in SPFx
SharePoint Framework launched in February 2017 with Gulp as the default build engine, paired with the Yeoman generator for project scaffolding. That combination served millions of web parts through years of incremental SPFx releases. Over time, however, the toolchain landscape shifted. Heft—a more scalable, integrated build system—emerged as the modern standard for the Microsoft 365 stack.
Microsoft first introduced Heft for SPFx projects in version 1.22 (early 2026), making it the default for newly generated solutions while allowing existing Gulp projects to continue during a transition period. The May roadmap explicitly called out that from SPFx 1.25 onward, Gulp would no longer be a supported build toolchain. The July revision simply reassigns that milestone to version 1.24, compressing the timeline.
This isn’t an isolated change. The broader SPFx roadmap is maturing rapidly: SPFx CLI is replacing Yeoman, open-source templates are being tightened, and work continues on React 18 support. The end of Gulp support is part of a deliberate modernization push.
Steps to Prepare Before September 2026
Development leads and SharePoint administrators should use the remaining weeks as a discovery phase, not a production rollout window.
- Inventory everything: List every deployed SPFx solution—web parts, extensions, command sets, and any legacy customizations. Record the SPFx version, whether it uses Gulp, and the level of build customization.
- Triage by risk: Apply the urgency tiers above. Document custom Gulp tasks, webpack changes, and CI script dependencies.
- Pilot Heft on a non-critical project: Build a proof of concept in an isolated branch. Validate local dev, production build, packaging, and deployment. Use this to create a reusable migration checklist.
- Plan dedicated migration sprints for urgent projects: Treat these as small modernization efforts, not routine maintenance. Allocate time for redesign, testing, and documentation.
- Update CI/CD pipelines: Ensure no job calls Gulp directly. Replace scripts that assume Gulp-generated artifact paths.
- Set a policy: All new SPFx work must use Heft. Any legacy Gulp project that hasn’t been migrated must have an explicit exception with a named owner and a deadline.
SharePoint administrators should note that there is no tenant-side switch to disable Gulp-built packages. The risk is operational: when a future security advisory or dependency update arrives, unsupported toolchains increase the cost and uncertainty of response.
If You Do Nothing: The Support Risk
Leaving a Gulp project untouched past September 2026 will not immediately break it. Existing web parts will continue to function in SharePoint Online. The danger is cumulative. Over time, npm packages will update, Node.js runtimes will evolve, and security vulnerabilities will surface. Without a supported build toolchain, patching a web part could become an ad-hoc archaeology project.
Unsupported does not mean insecure in the classic vulnerability sense, but it does mean exposed. When the clock runs out on a critical fix, having a Heft-ready build pipeline is the difference between a one-hour deployment and a multi-week engineering scramble.
Outlook: Beyond the September Release
The Heft migration is not an endpoint—it’s a gateway to larger SPFx advancements. SPFx CLI GA, arriving in the same September release, will replace the venerable Yeoman generator and enable organization-specific scaffolding. Navigation customizers will allow developers to override navigation nodes and experiences. And the long-awaited React 18 support, while not yet dated, depends on the broader toolchain modernization now underway.
By September, the organizations best positioned won’t be the ones that rushed every project through a migration. They’ll be the ones that can clearly show—with evidence—which Gulp solutions are simple enough to defer, which are already validated on Heft, and which are critical enough to have been transitioned before Microsoft’s support focus moves on.