Session state is built by a factory so caches clear as a unit instead of individually.
What's wrong with this entry?
Session state is now built by a factory with a nested project group, and many long-lived caches (git availability, plugin agents, ripgrep availability and file counts, footer-link regexes, team-artifact scanning, temp directory resolution, marketplace loads, messaging socket state) became classes with an explicit reset. Per-session state is cleared as a unit rather than cache by cache; behaviour is meant to be unchanged.
project: { originalCwd: e, projectRoot: e, cwd: e },
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.235
Process-wide caches are now scoped per host
Both mention state
-
v2.1.235
Per-session state replaces process-wide globals, and the render root takes explicit dependencies
Both mention state
-
v2.1.235
More file-scope variables replaced by accessor-backed containers
Both mention state