More caches, from the PR poller to the model catalog, became resettable objects.
What's wrong with this entry?
A large sweep replaced module-level variables holding caches and one-shot flags with objects and classes exposing named accessors, across config file reading, the Chrome install prompt, the GitHub PR poller, sandbox startup, plugin hook hot-reload, iTerm teammate panes, artifact live subscriptions and the model catalog. Behaviour is largely unchanged; these caches are now per-instance and can be reset.
AA.installUpsellBypassSuppressionCounted
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