{"version":"2.1.271","anchor":"settingspermissions-ui-pure-renaming-no-behaviour-change","canonical_anchor":"settingspermissions-ui-pure-renaming-no-behaviour-change","heading":"Settings\/permissions UI - pure renaming, no behaviour change","tier":"internal","area":"Settings UI","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/settingspermissions-ui-pure-renaming-no-behaviour-change","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Settings\/permissions UI - pure renaming, no behaviour change\n\nInternal renaming only in the settings\/permissions UI, no visible change\n\n**What**\n\nThe code that renders settings list items, including the lock display for `autoUpdatesChannel` (the setting that follows a stable release channel instead of latest), was internally renumbered by Claude Code's build tooling. The actual logic, including which settings show as locked and how the update channel default is checked, did not change.\n\n**Why**\n\nThis is a behind-the-scenes cleanup with no effect on what you see or how settings behave.\n\n- Area: Settings UI\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}