{"version":"2.1.242","anchor":"pre-warmed-cloud-sessions-accept-two-named-branches-instead-","canonical_anchor":"pre-warmed-cloud-sessions-accept-two-named-branches-instead-","heading":"Pre-warmed cloud sessions accept two named branches instead of rejecting all revisions","tier":"internal","area":"Cloud Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/pre-warmed-cloud-sessions-accept-two-named-branches-instead-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Pre-warmed cloud sessions accept two named branches instead of rejecting all revisions\n\nPre-warmed cloud sessions map a pinned revision to a staging or warm branch instead of refusing it.\n\n**What**\n\nA session that pins a specific revision used to be refused outright. The revision is now mapped to a branch, defaulting to `staging` when none is given and `warm` for the warm branch, and anything else is refused with the offending reference echoed back, cut off at 80 characters.\n\n**Evidence**\n\n`session named a revision the standby does not prefetch`\n\n- Area: Cloud Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5"}