@catladder/cli 0.0.0-next-dc12de13 → 0.0.0-next-3675a1db

package/dist/packages/pipeline/src/backends/gitlab/releaseGateJobs.js

@@ -0,0 +1,32 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.getReleaseGateJobNames = void 0;
+/**
+ * the jobs the queued-release executor must `needs:` so that it runs
+ * exactly when the whole main-branch pipeline succeeded.
+ *
+ * `needs:` is transitive: a job that another automatic job needs is
+ * already awaited through that job, and a failed ancestor skips its
+ * descendants (and with them the executor) either way. The executor
+ * therefore only needs the SINKS of the auto-job graph — the jobs no
+ * other automatic job depends on (deploy/verify tips, terminal
+ * test/lint/audit). This keeps the needs list far below gitlab's
+ * 50-entry cap even on pipelines with many components.
+ *
+ * INVARIANT (do not weaken): every automatic job is an ancestor of the
+ * returned set. This holds for ANY graph shape, because the sinks are
+ * recomputed from the actual needs edges on every generation — if e.g.
+ * deploys ever stop needing the test jobs, the test jobs become sinks
+ * and re-enter the executor's needs by themselves. Only needs FROM
+ * automatic jobs count: a job consumed solely by manual jobs is a sink
+ * too, and keeps gating the release directly.
+ */
+const getReleaseGateJobNames = (autoJobs) => {
+    const neededByAnAutoJob = new Set(autoJobs.flatMap(({ gitlabJob }) => {
+        var _a;
+        return ((_a = gitlabJob.needs) !== null && _a !== void 0 ? _a : []).map((need) => typeof need === "string" ? need : need.job);
+    }));
+    return [...new Set(autoJobs.map(({ name }) => name))].filter((name) => !neededByAnAutoJob.has(name));
+};
+exports.getReleaseGateJobNames = getReleaseGateJobNames;
+//# sourceMappingURL=releaseGateJobs.js.map

package/dist/packages/pipeline/src/backends/gitlab/releaseGateJobs.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"releaseGateJobs.js","sourceRoot":"","sources":["../../../../../../../../packages/pipeline/src/backends/gitlab/releaseGateJobs.ts"],"names":[],"mappings":";;;AAEA;;;;;;;;;;;;;;;;;;;GAmBG;AACI,MAAM,sBAAsB,GAAG,CACpC,QAAyE,EAC/D,EAAE;IACZ,MAAM,iBAAiB,GAAG,IAAI,GAAG,CAC/B,QAAQ,CAAC,OAAO,CAAC,CAAC,EAAE,SAAS,EAAE,EAAE,EAAE;;QACjC,OAAA,CAAC,MAAA,SAAS,CAAC,KAAK,mCAAI,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC,IAAI,EAAE,EAAE,CACnC,OAAO,IAAI,KAAK,QAAQ,CAAC,CAAC,CAAC,IAAI,CAAC,CAAC,CAAC,IAAI,CAAC,GAAG,CAC3C,CAAA;KAAA,CACF,CACF,CAAC;IACF,OAAO,CAAC,GAAG,IAAI,GAAG,CAAC,QAAQ,CAAC,GAAG,CAAC,CAAC,EAAE,IAAI,EAAE,EAAE,EAAE,CAAC,IAAI,CAAC,CAAC,CAAC,CAAC,MAAM,CAC1D,CAAC,IAAI,EAAE,EAAE,CAAC,CAAC,iBAAiB,CAAC,GAAG,CAAC,IAAI,CAAC,CACvC,CAAC;AACJ,CAAC,CAAC;AAbW,QAAA,sBAAsB,0BAajC"}

package/dist/skills/catladder-migrate-ci-backend/SKILL.md

@@ -255,6 +255,21 @@ now-wrong `gitRemote`, regenerate once more, and finish with
 
 ## After the cut-over
 
+- **Set up merge gating — GitHub has none by default.** On GitLab,
+  "merge when pipeline succeeds" is built in; on a fresh GitHub repo a
+  PR is mergeable the moment it opens, checks still running, and the
+  auto-merge button does not even appear. Two one-time settings fix it:
+  1. Settings → General → Pull Requests → enable **"Allow auto-merge"**
+     (and "Automatically delete head branches" while there)
+  2. a branch protection rule on the default branch requiring the
+     **`catladder ✅`** status check — the aggregate job catladder
+     generates into the review workflow precisely for this. Require
+     only this one context, never individual job names: those change
+     with every component add/rename, and a stale required name blocks
+     the renaming PR forever ("Expected — waiting for status").
+  Consider leaving "enforce for administrators" off: this repo's CI is
+  generated, so if generation itself ever breaks, the admin bypass is
+  what lets the fix merge.
 - Tell the team where the pipeline lives now and how manual actions
   work there (on GitHub, manual jobs are dispatch workflows in the
   Actions sidebar — `🚀 catladder create release`, `▶️ catladder deploy`,