{"version":"2.1.292","anchor":"ultrareview-launch-can-be-blocked-when-the-preflight-is-unav","canonical_anchor":"ultrareview-launch-can-be-blocked-when-the-preflight-is-unav","heading":"Ultrareview launch can be blocked when the preflight check is unavailable for a branch review","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/ultrareview-launch-can-be-blocked-when-the-preflight-is-unav","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Ultrareview launch can be blocked when the preflight check is unavailable for a branch review\n\nUltrareview now passes bundleFollows for branch reviews, and a missing preflight response can block the launch instead of letting it proceed\n\n**Unclear.** The condition that decides whether the launch is blocked is not identified.\n\n**What**\n\nUltrareview runs a preflight, a check made before a review is launched. That preflight now takes a new `bundleFollows` argument, which the launch sets to true when the review is in branch mode (`bundleFollows: a.mode === \"branch\"`).\n\n- Before, if the preflight response was missing, the launch always went ahead and was marked `preflightUnavailable: true`.\n\n- Now, a missing preflight response can return blocked with the reason `preflight_unavailable` instead. This only happens when a further helper check (`b8o()`) passes; what controls that helper was not traced.\n\n**Why**\n\nA review launch that used to go ahead without its preflight check may now be refused. This mostly affects branch reviews, where code is bundled and sent along with the review.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}