Session stores can copy one field to a new instance, the shape of surviving an identity change.
A continueFrom method on five session stores exists with no callers in this build.
What's wrong with this entry?
Five internal per-session stores (conversation counters, MCP wiring, an emitted-date record, user presence, and connected clients) gained a method that copies one field from another instance, the shape of carrying a little state across a session identity change while the rest resets. Nothing in this build calls it.
- The bundle contains exactly five occurrences of the name, all of them definitions.
continueFrom(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