The background-auth snapshot consumed at startup can now include a gatewayToken field alongside accessToken, read via the internal DCt consumer. If a snapshot read hits a transient failure (EBUSY, EPERM, or EACCES on Windows), the snapshot env var is no longer deleted or unset immediately; the failure is logged instead and a later read is allowed to retry.
Background-auth snapshot can now carry a gateway token, and retries on transient read failures
The startup auth snapshot can carry a gateway token, and a locked-file read failure now retries instead of discarding it.
You'll noticeTier: how much it should matter to you
3Useful: my rating, 1 to 5
3Signal: worth watching, 1 to 5
AuthArea: what it touches
Bug FixesKind: in v2.1.257,
Bug FixesSection of the release