CI gates
See a broken config get caught on the pull request, before it ever reaches a customer's infrastructure.
Schema, dependency-existence and semver-range checks against a fixture registry. Toggle when the gate runs to see the same failure escape to a deploy log instead.
“Moved failure detection from publish time to pull request for Dell Automation Platform's catalog publishing team, building GitHub Actions gates that validate blueprint offers' configuration, dependencies, and version references before they are published; publish failures dropped from ~35% to near zero and 3–4 weekly escalations ended.”Dell Technologies — Dell Automation Platform · Engineering Productivity
How it works
The registry on the right is a fixture — four components, each with the versions that have actually been “published” — but the checks against it are real: a schema check, a dependency-existence check, and a semver-range resolver that supports exact pins, ^-ranges, and comparator clauses like >=1.2.0 <2.0.0.
Switch “when the gate runs” to publish-time and re-run a broken preset: the same failure is caught, but only after merge, so it shows up in a simulated deploy log instead of blocking the pull request. That's the actual shape of the change on the résumé — the check didn't get smarter, it just moved earlier.