@intentius/chant 0.124.93 → 0.124.94

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.
Files changed (62) hide show
  1. package/dist/ci-product.d.ts +17 -1
  2. package/dist/ci-product.d.ts.map +1 -1
  3. package/dist/ci-product.js +23 -7
  4. package/dist/cli/handlers/run-wave.js +17 -3
  5. package/dist/cli/main.d.ts.map +1 -1
  6. package/dist/cli/main.js +4 -1
  7. package/dist/floor-table.data.d.ts.map +1 -1
  8. package/dist/floor-table.data.js +13 -6
  9. package/dist/gate-resume-run.d.ts +7 -0
  10. package/dist/gate-resume-run.d.ts.map +1 -1
  11. package/dist/gate-resume-run.js +42 -3
  12. package/dist/lexicon.d.ts +47 -1
  13. package/dist/lexicon.d.ts.map +1 -1
  14. package/dist/lifecycle/gate-applied.d.ts +18 -0
  15. package/dist/lifecycle/gate-applied.d.ts.map +1 -1
  16. package/dist/op/gate-run-locator.d.ts +17 -0
  17. package/dist/op/gate-run-locator.d.ts.map +1 -1
  18. package/dist/op/index.d.ts +3 -1
  19. package/dist/op/index.d.ts.map +1 -1
  20. package/dist/op/index.js +2 -1
  21. package/dist/op/op-waves-names.d.ts +40 -0
  22. package/dist/op/op-waves-names.d.ts.map +1 -1
  23. package/dist/op/op-waves-names.js +79 -0
  24. package/dist/op/op-waves-remainder.d.ts +110 -0
  25. package/dist/op/op-waves-remainder.d.ts.map +1 -0
  26. package/dist/op/op-waves-remainder.js +120 -0
  27. package/dist/op/op-waves-render-spec.d.ts +63 -5
  28. package/dist/op/op-waves-render-spec.d.ts.map +1 -1
  29. package/dist/op/op-waves-render-spec.js +68 -10
  30. package/dist/op/op-waves-run.d.ts +27 -1
  31. package/dist/op/op-waves-run.d.ts.map +1 -1
  32. package/dist/op/op-waves-run.js +192 -4
  33. package/dist/op/op-waves-split-resume.d.ts +57 -0
  34. package/dist/op/op-waves-split-resume.d.ts.map +1 -0
  35. package/dist/op/op-waves-split-resume.js +94 -0
  36. package/dist/op/op-waves.d.ts +26 -1
  37. package/dist/op/op-waves.d.ts.map +1 -1
  38. package/dist/op/op-waves.js +11 -2
  39. package/dist/release-floors.d.ts +9 -1
  40. package/dist/release-floors.d.ts.map +1 -1
  41. package/dist/release-floors.js +9 -1
  42. package/dist/wave-runtime.mjs +360 -360
  43. package/package.json +1 -1
  44. package/src/ci-product.ts +26 -7
  45. package/src/cli/handlers/run-wave.ts +16 -3
  46. package/src/cli/main.ts +4 -1
  47. package/src/floor-table.data.ts +13 -6
  48. package/src/gate-resume-run.ts +38 -3
  49. package/src/lexicon.ts +47 -1
  50. package/src/lifecycle/gate-applied.ts +16 -0
  51. package/src/op/gate-run-locator.ts +14 -0
  52. package/src/op/index.ts +5 -0
  53. package/src/op/op-waves-names.ts +80 -0
  54. package/src/op/op-waves-remainder.test.ts +342 -0
  55. package/src/op/op-waves-remainder.ts +146 -0
  56. package/src/op/op-waves-render-spec.test.ts +107 -0
  57. package/src/op/op-waves-render-spec.ts +81 -10
  58. package/src/op/op-waves-run.ts +200 -5
  59. package/src/op/op-waves-split-resume.test.ts +149 -0
  60. package/src/op/op-waves-split-resume.ts +109 -0
  61. package/src/op/op-waves.ts +33 -2
  62. package/src/release-floors.ts +13 -1
@@ -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.93";
22
+ export const NEXT_RELEASE = "0.124.94";
23
23
  /** 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). */
24
24
  export const LOCAL_CHANT_FLOOR = "0.124.86";
25
25
  /** The first chant with `chant workspace ref-gate` (pre-receive, pre-push, check, status, attach, install) and `refs` in `.chant/trust.json`, the checks a ref update needs evidence for (#4867). */
@@ -166,6 +166,14 @@ export const BEFORE_MERGE_REF_GATE_FLOOR = "0.124.89";
166
166
  export const TARGET_SIGNED_CHECKS_FLOOR = "0.124.89";
167
167
  /** The first chant whose Op waves generators take `renderSpec` (the wave jobs run `chant run wave --render-spec`, and `CHANT_WAVES_SPEC_COMMAND` names the product command that prints the spec at the commit in `CHANT_WAVES_SPEC_AT`), so a product whose spec is built from its config at base renders its wave jobs, policy step, evidence job and cloud trade through chant (#4982). */
168
168
  export const RUNTIME_WAVES_SPEC_FLOOR = "0.124.89";
169
+ /** 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). */
170
+ export const RUNTIME_WAVES_SPEC_RUNS_AT_HEAD_FLOOR = NEXT_RELEASE;
171
+ /** 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. */
172
+ export const OP_WAVES_REMAINDER_FLOOR = NEXT_RELEASE;
173
+ /** 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. */
174
+ export const OP_WAVES_SPLIT_RESUME_FLOOR = NEXT_RELEASE;
175
+ /** 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. */
176
+ export const OP_WAVES_REMAINDER_PARITY_FLOOR = NEXT_RELEASE;
169
177
  /** 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). */
170
178
  export const GITLAB_WAVE_EVIDENCE_RETRY_FLOOR = "0.124.89";
171
179
  /** The first chant whose terraform lexicon's engine runs carry what a product's own command tracing read: `runBinary` and the engine runner's `exec` and `execSync` answer stderr apart (`Ran.stderr`) and a spawn failure's message (`Ran.error`), a hook's `after` gets a binary that could not be started as a null code with `error`, `commandTrace` ends that span with the message, and `composeCommandHooks` runs a product's own hook and `commandTrace` as one `onCommand` (#5007). */