@mutmutco/codex-plugin 4.3.16 → 4.3.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "mmi",
3
- "version": "4.3.16",
3
+ "version": "4.3.17",
4
4
  "mmiCompat": "4.x",
5
5
  "description": "MMI workflow skills and org gates delivery.",
6
6
  "author": {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@mutmutco/codex-plugin",
3
- "version": "4.3.16",
3
+ "version": "4.3.17",
4
4
  "description": "MMI workflow skills and org gates delivery.",
5
5
  "author": {
6
6
  "name": "MMI Future",
@@ -381,6 +381,13 @@ collaborator list + the per-branch allowlist are the record — no separate rost
381
381
  $OWNER/$REPO` remains the supported fallback; confirm `product required-check ruleset enforcement active`
382
382
  with `bootstrap verify` before reporting bootstrap complete. MMI-Hub keeps its own three-job gate
383
383
  (`cli`/`infra`/`docs`) — never apply the product ruleset there.
384
+ - **The ruleset requires an up-to-date head (#6263)** — the seeded reference sets
385
+ `strict_required_status_checks_policy: true` ("require branches to be up to date before merging"), so the
386
+ last of several parallel landings re-tests on the real combination instead of a base that lacked the
387
+ others (Jerv-JervCode#4289). `bootstrap apply --execute` and `ci reconcile --apply` re-PUT an existing
388
+ non-strict ruleset; `bootstrap verify` reports it as `product required-check ruleset requires an up-to-date
389
+ branch`. `pr merge` / `pr land` update a BEHIND head from the base with a merge commit and re-wait once —
390
+ see `docs/Guides/train-troubleshooting.md#head-behind-base`.
384
391
  - **A brand-new repo cannot pass the gate you just installed — its first commit must carry a real project
385
392
  (#2928).** The seeded `gate.yml` runs `GATE_INSTALL_CMD` + `GATE_CMD` (`npm ci` + `npm run check` by
386
393
  default) **unconditionally**. An empty repo has no `package.json`, so the gate **fails on the seed PR
@@ -1,5 +1,5 @@
1
1
  {
2
- "_comment": "Repository-level ruleset requiring the product gate job (#1333). Apply via GitHub repo rulesets (master-admin) after bootstrap seeds gate.yml — the job name gate must match this context.",
2
+ "_comment": "Repository-level ruleset requiring the product gate job (#1333). Apply via GitHub repo rulesets (master-admin) after bootstrap seeds gate.yml — the job name gate must match this context. strict_required_status_checks_policy=true (#6263): the head must be up to date with the base before merging, so the last of several parallel landings re-tests on the real combination.",
3
3
  "name": "mmi-product-required-checks",
4
4
  "target": "branch",
5
5
  "enforcement": "active",
@@ -13,7 +13,7 @@
13
13
  {
14
14
  "type": "required_status_checks",
15
15
  "parameters": {
16
- "strict_required_status_checks_policy": false,
16
+ "strict_required_status_checks_policy": true,
17
17
  "required_status_checks": [
18
18
  { "context": "gate" }
19
19
  ]