@patronage/software-factory 1.0.0-alpha.36 → 1.0.0-alpha.37
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.
- package/README.md +1 -1
- package/dist/index.d.ts +198 -19
- package/dist/index.js +3844 -3267
- package/dist/oxlint-jev/index.d.ts +3991 -1
- package/dist/schemas.d.ts +7 -5
- package/dist/schemas.js +13 -3
- package/package.json +2 -2
package/dist/schemas.d.ts
CHANGED
|
@@ -860,11 +860,13 @@ interface PrReadyProof {
|
|
|
860
860
|
schemaVersion: 3;
|
|
861
861
|
/**
|
|
862
862
|
* What GitHub actually did when this run armed native auto-merge (#477).
|
|
863
|
-
* Present exactly when a ready
|
|
864
|
-
*
|
|
865
|
-
*
|
|
866
|
-
*
|
|
867
|
-
*
|
|
863
|
+
* Present exactly when a ready run called the arming module (#1299): not
|
|
864
|
+
* for an `autoMerge: false` wave, and not when a notice names why the run
|
|
865
|
+
* did not arm. Read back from the PR rather than inferred from the
|
|
866
|
+
* invocation, because `gh pr merge --auto` arms, merges, or does nothing
|
|
867
|
+
* with the same exit code and the same empty output. `not-armed` means the
|
|
868
|
+
* candidate is admitted but nothing will merge it, and `followUp` carries
|
|
869
|
+
* the re-dispatch.
|
|
868
870
|
*/
|
|
869
871
|
arming?: {
|
|
870
872
|
detail?: string;
|
package/dist/schemas.js
CHANGED
|
@@ -14,9 +14,10 @@ Object.fromEntries(EVIDENCE_REVIEW_RUNGS.map((rung, index) => [rung, index]));
|
|
|
14
14
|
const DEMAND_KEYS = {
|
|
15
15
|
/**
|
|
16
16
|
* The boundary wave that authorizes this candidate's merge schedule (#477).
|
|
17
|
-
* In force exactly when GitHub already has auto-merge enabled
|
|
18
|
-
*
|
|
19
|
-
*
|
|
17
|
+
* In force exactly when GitHub already has auto-merge enabled on a candidate
|
|
18
|
+
* that the standalone default does not authorize (#1299): a live schedule on
|
|
19
|
+
* an epic member with no wave demand resolved is an unauthorized merge
|
|
20
|
+
* waiting to happen.
|
|
20
21
|
*/
|
|
21
22
|
boundaryWave: "boundary-wave",
|
|
22
23
|
/**
|
|
@@ -55,6 +56,15 @@ const DEMAND_KEYS = {
|
|
|
55
56
|
prVerify: "pr-verify",
|
|
56
57
|
/** The profile-resolved review ladder policy. */
|
|
57
58
|
reviewLadder: "review-ladder",
|
|
59
|
+
/**
|
|
60
|
+
* A review round past the second on one pull request (#1280). A round is
|
|
61
|
+
* every review recorded at one patch, so a pair of clean sessions at one
|
|
62
|
+
* head is one round. Only an operator waiver clears it: `pr:review
|
|
63
|
+
* --assemble` refuses to start a third round without one, and `pr:ready`
|
|
64
|
+
* refuses a ladder that holds more than two. The waiver rationale carries
|
|
65
|
+
* the operator's disposition.
|
|
66
|
+
*/
|
|
67
|
+
reviewRoundLimit: "review-round-limit",
|
|
58
68
|
/** Unresolved GitHub review threads. */
|
|
59
69
|
reviewThreads: "review-threads"
|
|
60
70
|
};
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@patronage/software-factory",
|
|
3
|
-
"version": "1.0.0-alpha.
|
|
3
|
+
"version": "1.0.0-alpha.37",
|
|
4
4
|
"description": "Shared Patronage software factory CLI and project-profile validation tools",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -42,7 +42,7 @@
|
|
|
42
42
|
"picomatch": "^4.0.5",
|
|
43
43
|
"yaml": "^2.9.0",
|
|
44
44
|
"zod": "4.4.3",
|
|
45
|
-
"@patronage/factory-ci": "1.0.0-alpha.
|
|
45
|
+
"@patronage/factory-ci": "1.0.0-alpha.37"
|
|
46
46
|
},
|
|
47
47
|
"devDependencies": {
|
|
48
48
|
"@oxlint/plugins": "1.76.0",
|