{"version":"2.1.311","anchor":"native-auto-updater-reports-registry-session-refusal-separat","canonical_anchor":"native-auto-updater-reports-registry-session-refusal-separat","heading":"Auto-updater now reports a refused registry session as its own failure","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/native-auto-updater-reports-registry-session-refusal-separat","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Auto-updater now reports a refused registry session as its own failure\n\nWhen the native updater is refused a registry session, it now reports that specifically instead of a generic install failure\n\n**What**\n\nThe native auto-updater is the part of Claude Code that downloads and installs new versions. When it fails because the registry, the server it downloads from, refuses its session, the result is now marked as a refused session with an error code, and a hint saying the registry session was refused is stored. Before, this case was reported as a general install failure.\n\n**Why**\n\nA refused session can now be told apart from other install problems, which makes a failed update easier to understand.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}