{"version":"2.1.293","anchor":"new-container-restart-on-version-change-feature-tag","canonical_anchor":"new-container-restart-on-version-change-feature-tag","heading":"New container entry related to restarting on a version change","tier":"internal","area":"Container Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/new-container-restart-on-version-change-feature-tag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### New container entry related to restarting on a version change\n\nA new entry about container sessions restarting on a version change was added to the list of container-related names\n\n**Unclear.** It is not clear what this list is used for or whether anything turns this behaviour on.\n\n**What**\n\nA new entry, ccs_container_version_restart, was added to a list of names alongside other entries about container sessions (sessions that run inside an isolated container). The name points to container sessions restarting when a version changes.\n\n**Why**\n\nNothing in this release shows such a restart actually happening, so for now this is a name in a list rather than a behaviour you will notice.\n\n- Area: Container Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}