chore(release): archied v1.33.0
This commit is contained in:
1 parent
e339c101b9
commit
1db7cb98e3
4 files changed
+55
No files matched your search
@@ -1,5 +1,28 @@
|
||||
# archied changelog
|
||||
|
||||
## [1.33.0] - 2026-09-22
|
||||
|
||||
### EDA: playbook action arguments are compiled at load (J2)
|
||||
|
||||
- A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads.
|
||||
`args` and `when` share one compilation path and one evaluation context, so an expression written
|
||||
for one works in the other.
|
||||
- **Behaviour change:** an `args` expression that does not compile is a **load failure**, not a
|
||||
runtime miss — the same reject-at-load rule already applied to a binding collision and to an
|
||||
unknown `actions.<id>`. In practice, a daemon loading a playbook with a malformed `args` block
|
||||
fails at startup rather than part-way through a dispatch.
|
||||
- Compiling several arguments now reports the **first** bad key deterministically (keys are sorted).
|
||||
Previously it ranged a map, so the reported bad key could differ between runs and the failure was
|
||||
not reproducible.
|
||||
- `args` is deliberately **inert** for now: parsed, compiled and stored, but no shipped position
|
||||
consumes it yet. A consumer arrives with the first side-effecting position.
|
||||
|
||||
**Not yet decided:** how an `args` evaluation failure behaves at dispatch. The `when` predicate rule
|
||||
(error, skip, log) does not obviously transfer, because `args` is data rather than a predicate, and
|
||||
silently skipping an action whose arguments failed to evaluate would be a silent failure of exactly
|
||||
the kind this release train has been removing. It currently propagates the error to the caller, and
|
||||
that asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately.
|
||||
|
||||
## [1.32.1] - 2026-09-22
|
||||
|
||||
### Host packaging: `archie-messaging` now ships and updates
|
||||
|
||||
@@ -0,0 +1,24 @@
|
||||
# archied 1.33.0
|
||||
|
||||
Released 2026-09-22. [All news](../index.md)
|
||||
|
||||
### EDA: playbook action arguments are compiled at load (J2)
|
||||
|
||||
- A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads.
|
||||
`args` and `when` share one compilation path and one evaluation context, so an expression written
|
||||
for one works in the other.
|
||||
- **Behaviour change:** an `args` expression that does not compile is a **load failure**, not a
|
||||
runtime miss — the same reject-at-load rule already applied to a binding collision and to an
|
||||
unknown `actions.<id>`. In practice, a daemon loading a playbook with a malformed `args` block
|
||||
fails at startup rather than part-way through a dispatch.
|
||||
- Compiling several arguments now reports the **first** bad key deterministically (keys are sorted).
|
||||
Previously it ranged a map, so the reported bad key could differ between runs and the failure was
|
||||
not reproducible.
|
||||
- `args` is deliberately **inert** for now: parsed, compiled and stored, but no shipped position
|
||||
consumes it yet. A consumer arrives with the first side-effecting position.
|
||||
|
||||
**Not yet decided:** how an `args` evaluation failure behaves at dispatch. The `when` predicate rule
|
||||
(error, skip, log) does not obviously transfer, because `args` is data rather than a predicate, and
|
||||
silently skipping an action whose arguments failed to evaluate would be a silent failure of exactly
|
||||
the kind this release train has been removing. It currently propagates the error to the caller, and
|
||||
that asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately.
|
||||
@@ -4,6 +4,7 @@ Release notes for archied and archie-agent, newest first.
|
||||
|
||||
## 2026-09-22
|
||||
|
||||
- [archied 1.33.0](archied/1.33.0.md)
|
||||
- [archied 1.32.1](archied/1.32.1.md)
|
||||
- [archied 1.32.0](archied/1.32.0.md)
|
||||
- [archied 1.31.0](archied/1.31.0.md)
|
||||
|
||||
@@ -1,4 +1,11 @@
|
||||
[
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
"version": "1.33.0",
|
||||
"date": "2026-09-22",
|
||||
"body": "### EDA: playbook action arguments are compiled at load (J2)\n\n- A playbook action may now declare `args`, compiled as CEL expressions when the playbook loads.\n `args` and `when` share one compilation path and one evaluation context, so an expression written\n for one works in the other.\n- **Behaviour change:** an `args` expression that does not compile is a **load failure**, not a\n runtime miss — the same reject-at-load rule already applied to a binding collision and to an\n unknown `actions.<id>`. In practice, a daemon loading a playbook with a malformed `args` block\n fails at startup rather than part-way through a dispatch.\n- Compiling several arguments now reports the **first** bad key deterministically (keys are sorted).\n Previously it ranged a map, so the reported bad key could differ between runs and the failure was\n not reproducible.\n- `args` is deliberately **inert** for now: parsed, compiled and stored, but no shipped position\n consumes it yet. A consumer arrives with the first side-effecting position.\n\n**Not yet decided:** how an `args` evaluation failure behaves at dispatch. The `when` predicate rule\n(error, skip, log) does not obviously transfer, because `args` is data rather than a predicate, and\nsilently skipping an action whose arguments failed to evaluate would be a silent failure of exactly\nthe kind this release train has been removing. It currently propagates the error to the caller, and\nthat asymmetry is documented at the code. Ratifying it against a real consumer is tracked separately."
|
||||
},
|
||||
{
|
||||
"component": "archied",
|
||||
"name": "archied",
|
||||
|
||||
Reference in new issue
Block a user