Nothing to try yet
No documentation found
A new stable-address scheme for session IDs is gated behind tengu_session_stable_address
What
A new internal check reads the tengu_session_stable_address setting and uses it in several places that determine session IDs and derived secrets, such as choosing whether to hash a value or generate random bytes, and whether a 'derived' source should still be treated as valid.
Why
This lays groundwork for an alternate, more stable way of deriving session identifiers, without yet describing what changes for users when it's active.
Names in the bundletengu_session_stable_address
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding doesn't say what a stable address scheme changes about session behavior for users, and the tengu_session_stable_address gate is…
The name it cites is new in this build
New in this build: tengu_session_stable_address