@intentius/chant 0.124.94 → 0.124.95
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/dist/ci-comment-commands.d.ts +12 -1
- package/dist/ci-comment-commands.d.ts.map +1 -1
- package/dist/ci-comment-commands.js +29 -0
- package/dist/ci-note-commands.d.ts +1 -1
- package/dist/ci-note-commands.d.ts.map +1 -1
- package/dist/ci-note-commands.js +11 -1
- package/dist/ci-product.d.ts +2 -0
- package/dist/ci-product.d.ts.map +1 -1
- package/dist/ci-product.js +5 -4
- package/dist/cli/handlers/pr-comment.d.ts.map +1 -1
- package/dist/cli/handlers/pr-comment.js +11 -4
- package/dist/components/product-pipeline.d.ts.map +1 -1
- package/dist/components/product-pipeline.js +4 -2
- package/dist/components/product-plan.d.ts +6 -0
- package/dist/components/product-plan.d.ts.map +1 -1
- package/dist/components/product-plan.js +9 -1
- package/dist/floor-table.data.d.ts.map +1 -1
- package/dist/floor-table.data.js +9 -7
- package/dist/op/before-merge-decide.d.ts +39 -2
- package/dist/op/before-merge-decide.d.ts.map +1 -1
- package/dist/op/before-merge-decide.js +59 -0
- package/dist/release-floors.d.ts +5 -1
- package/dist/release-floors.d.ts.map +1 -1
- package/dist/release-floors.js +9 -5
- package/dist/wave-runtime.mjs +182 -182
- package/package.json +1 -1
- package/src/ci-comment-commands.test.ts +147 -0
- package/src/ci-comment-commands.ts +29 -1
- package/src/ci-note-commands.ts +12 -2
- package/src/ci-product.ts +5 -4
- package/src/cli/handlers/pr-comment.ts +10 -4
- package/src/components/product-pipeline.ts +4 -2
- package/src/components/product-plan.ts +9 -2
- package/src/floor-table.data.ts +9 -7
- package/src/op/before-merge-decide.ts +74 -2
- package/src/op/op-waves-remainder.test.ts +2 -3
- package/src/op/op-waves-render-spec.test.ts +1 -2
- package/src/op/op-waves-split-resume.test.ts +2 -3
- package/src/release-floors.ts +11 -5
package/src/release-floors.ts
CHANGED
|
@@ -19,7 +19,7 @@
|
|
|
19
19
|
* this constant to the next patch (#4501). The check fails while a floor
|
|
20
20
|
* still names this constant after its version shipped.
|
|
21
21
|
*/
|
|
22
|
-
export const NEXT_RELEASE = "0.124.
|
|
22
|
+
export const NEXT_RELEASE = "0.124.95";
|
|
23
23
|
|
|
24
24
|
/** The first chant with `chant dev local` and `chant dev bundle-check`, `@intentius/chant/local-chant` and `@intentius/chant/bundle-check` (`chantRuntimeTarget`, `chantExternalPlugin`, `checkBundle`): a product built against a chant checkout, and its bundle checked, without its own scripts (#4787). */
|
|
25
25
|
export const LOCAL_CHANT_FLOOR = "0.124.86";
|
|
@@ -235,16 +235,22 @@ export const TARGET_SIGNED_CHECKS_FLOOR = "0.124.89";
|
|
|
235
235
|
export const RUNTIME_WAVES_SPEC_FLOOR = "0.124.89";
|
|
236
236
|
|
|
237
237
|
/** The first chant whose Op waves `renderSpec` takes `runsAtHead` (the jobs carry `CHANT_WAVES_SPEC_RUNS=head`): the job's own spec is rendered at the applied commit, with `CHANT_WAVES_SPEC_BASE` set to the base commit beside `CHANT_WAVES_SPEC_AT`, so the runs a change adds apply at its merge, while the gate policy, holds, hooks and evidence rules still come from the render at base (#5046). */
|
|
238
|
-
export const RUNTIME_WAVES_SPEC_RUNS_AT_HEAD_FLOOR =
|
|
238
|
+
export const RUNTIME_WAVES_SPEC_RUNS_AT_HEAD_FLOOR = "0.124.94";
|
|
239
239
|
|
|
240
240
|
/** The first chant whose Op waves keep the record of an apply under an approval themselves (#5047): with `approvals.spend`, `approvals.remainder` writes each change the approved plans make, the commit and the run on the applied line (a split wave's gate job writes it), the job that applies the whole wave or the record job writes how the apply ended, and a wave run again at that commit applies the rest under the same approval when its plans make only changes the stopped apply did not finish; a wave that plans no change closes a stopped apply, and `approvals.spendStanding` spends an approval of the digest a wave its gate let through applies. */
|
|
241
|
-
export const OP_WAVES_REMAINDER_FLOOR =
|
|
241
|
+
export const OP_WAVES_REMAINDER_FLOOR = "0.124.94";
|
|
242
242
|
|
|
243
243
|
/** The first chant whose `chant run resume` starts a killed split apply again on GitLab and Forgejo (#5052): under `approvals.remainder` the gate job's applied line names its run there too, GitLab's with the wave's applying and record jobs by name (`retry`), which the resume retries, and Forgejo's with the run's dispatch inputs (`inputs`), which the resume dispatches with, so the new run applies the rest at the same decided head or commit. */
|
|
244
|
-
export const OP_WAVES_SPLIT_RESUME_FLOOR =
|
|
244
|
+
export const OP_WAVES_SPLIT_RESUME_FLOOR = "0.124.94";
|
|
245
245
|
|
|
246
246
|
/** The first chant whose `approvals.remainder` resumes the waves terragucci's own records resume (#5056): the terraform step gives a live choudoufu root's plan (`live-plan-set`) its `resourceDigests`, so its applied line names the changes, and the cover leaves out the cost member `(monthly cost)`, whose digest follows from the plans, on both sides. */
|
|
247
|
-
export const OP_WAVES_REMAINDER_PARITY_FLOOR =
|
|
247
|
+
export const OP_WAVES_REMAINDER_PARITY_FLOOR = "0.124.94";
|
|
248
|
+
|
|
249
|
+
/** The first chant whose Op waves generators, in a product's workflow (`runIf`) with `beforeMerge` and a spec `control`, run the control job on the default branch's push, outside the product's `runIf` and after its `firstWaveNeeds` jobs, and tell the control repo the waves applied at the pushed commit without adding up outcomes, on GitHub, Forgejo and GitLab (#5060). */
|
|
250
|
+
export const OP_WAVES_CONTROL_BEFORE_MERGE_FLOOR = NEXT_RELEASE;
|
|
251
|
+
|
|
252
|
+
/** The first chant whose waves before merge lock and unlock on a comment by the product plan's reach line (#5061): with `wavesBeforeMerge` and `productPlan.reach`, and no `locks: "plan"`, the comment job (GitHub, Forgejo) and the note poll (GitLab, `chantNoteRuns`) answer `/<product> lock` on an open pull request by taking the locks of what the reach line prints at stage `apply` in `_locks/<reach.gate>.json` without applying (`decideLocksBeforeMerge`), refused with the holder named, and `/<product> unlock` by releasing the pull request's locks; and the product plan takes `reach` without `locks: "plan"` under `wavesBeforeMerge`, writing no reach lock job. */
|
|
253
|
+
export const WAVES_BEFORE_MERGE_LOCKS_FLOOR = NEXT_RELEASE;
|
|
248
254
|
|
|
249
255
|
/** The first chant whose `chant run resume` (`resumeGateRun`) on GitLab retries a wave job's `<wave job>-evidence` with the wave job when the evidence job already ran, and whose `ci evidence sign --from-job` waits for a job it reads to finish, so a resumed wave's evidence job signs from the new try (#4978). */
|
|
250
256
|
export const GITLAB_WAVE_EVIDENCE_RETRY_FLOOR = "0.124.89";
|