[BUG](ci) Changelog fragment check false-fails on PRs that touch no package

[sethfitz]

The Require changelog on package change job (.github/workflows/require-changelog-fragment.yaml) aborts with a bare exit 1 on any PR whose diff touches no file under packages/ — a workflow-only, docs-only, or root-only change.

Root cause: the job computes the changed packages with

touched=$(echo "$changed" | grep -oE "^packages/[^/]+/" | sort -u | while read -r prefix; do ... done)

When $changed contains no packages/ path, grep -oE matches nothing and exits 1. Under set -euo pipefail the pipeline inherits that non-zero status, and the command substitution in an assignment makes set -e abort the whole script before any output. The failure is indistinguishable from a genuine missing-fragment failure: no ::error::, no package list, just exit 1.

The sibling has_fragment / has_changelog substitutions already guard their grep -c with || true; the touched pipeline was missed.

Impact: every no-package PR falsely fails the required check and is forced to add a spurious fragment to get green. Observed on #626 (a workflow-only publish fix).

Fix: tolerate the no-match exit on the touched pipeline (append || true), matching the existing pattern. Detection of real missing fragments is unaffected.

[danabauer]

Seth Fitzsimmons (@sethfitz) is this a blocker for v.2.0.0?

[sethfitz]

No, and I think John McCall (@lowlydba) may have fixed this in a different way than the PR I proposed.

[lowlydba]

Yup, this should be resolved. It needed a little extra ❤️

schema/.github/workflows/require-changelog-fragment.yaml

Lines 109 to 114 in 2a6170c

	# check-fragment skips for bot-labeled PRs and PRs that don't touch
	# packages/, and branch protection can't require a job that sometimes
	# doesn't run. This gate always runs and passes on either a real success
	# or an accepted skip, so it's the check to require in branch protection
	# instead of check-fragment directly.
	changelog-fragment-status:

The wrapper job at the end makes sure we always return the check as pass/fail, since skipped will never satisfy a required status check. This allows us to cleanly accept skipped == success, filling in the gap in GitHub native functionality.