{"version":"2.1.275","anchor":"self-hosted-runner-some-context-source-repos-may-now-be-exe","canonical_anchor":"self-hosted-runner-some-context-source-repos-may-now-be-exe","heading":"Self-hosted runner: some context-source repos may now be exempt from silent skip-on-not-found","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/self-hosted-runner-some-context-source-repos-may-now-be-exe","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Self-hosted runner: some context-source repos may now be exempt from silent skip-on-not-found\n\nSelf-hosted runners now check a per-source \"required\" setting before silently skipping missing context repos\n\n**What**\n\nWhen the self-hosted runner encounters a problem with a context-source repository, such as a missing branch reference, a failed checkout hook, or an access-denied error, it decides whether to silently skip that source or treat it as an error. Previously this decision was based only on whether the source had a matching entry in `push_targets`. Now it also checks whether that source is explicitly marked as `required`; sources marked this way are no longer silently skipped.\n\n**Why**\n\nThis means a repo that's genuinely needed for the run will now surface a problem instead of being quietly ignored, while other context sources can still be skipped as before.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}