{"version":"2.1.235","anchor":"cloud-session-bundling-head-behind-remote-is-now-its-own-ve","canonical_anchor":"cloud-session-bundling-head-behind-remote-is-now-its-own-ve","heading":"Cloud session bundling: HEAD-behind-remote is now its own verdict","tier":"notice","area":"Cloud Sessions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235\/e\/cloud-session-bundling-head-behind-remote-is-now-its-own-ve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.235","markdown":"### Cloud session bundling: HEAD-behind-remote is now its own verdict\n\nCloud session bundling now distinguishes a local HEAD that is behind the remote from one that has simply diverged\n\nThe git divergence check used for cloud session bundling now tells `head_behind_remote` apart from `head_not_at_remote` using a merge-base exit code, and warns when ancestry can't be determined. When HEAD is merely behind the remote, the caller can now start bundling from the local HEAD commit instead of treating it as diverged. A new reason-phrase map covers bundling unavailability, the size limit, and lack of Windows pull support, and the message shown when a bundle fails to arm is now composed from that map rather than a single fixed sentence.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}