#49701: ci: fix patches changes detected in apply patches workflow
Merged
Description of Change
Fast follow-up to #49667, because "It leaves the changes staged rather than committing them since it's just for checking purposes." turned out to be famous last words.
I didn't account for the part of our CI workflow which tries to detect patch changes by re-exporting them after sync, which was flagging the staged changes as a change to a patch and failing out. This was not caught originally when testing #49667 as there was a cache match (expected) so the sync never took place. This PR has been tested with the cache disabled to ensure a more complete E2E test.
Checklist
- PR description included
Release Notes
Notes: none
Backports
39-x-y
MergedPR Number
#49709Merged At
Feb 6, 2026, 11:29:56 PM
Released In
v39.5.2Release Date
Feb 10, 2026, 10:03:57 AM
40-x-y
MergedPR Number
#49710Merged At
Feb 6, 2026, 11:29:53 PM
Released In
v40.3.0Release Date
Feb 10, 2026, 10:03:00 AM
41-x-y
MergedPR Number
#49708Merged At
Feb 6, 2026, 11:30:15 PM
Released In
v41.0.0-alpha.6Release Date
Feb 9, 2026, 7:31:39 AM
Semver Impact
Major
Breaking changes
Minor
New features
Patch
Bug fixes
None
Docs, tests, etc.
Semantic Versioning helps users understand the impact of updates:
- Major (X.y.z): Breaking changes that may require code modifications
- Minor (x.Y.z): New features that maintain backward compatibility
- Patch (x.y.Z): Bug fixes that don't change the API
- None: Changes that don't affect using facing parts of Electron