Skip to content

feat(service-automation,lint,spec,verify)!: the single-brace resolver and the legacy condition path are deleted — every condition is CEL, a value-slot literal is handed on as written (#19939 pass 4, S7) #33271

feat(service-automation,lint,spec,verify)!: the single-brace resolver and the legacy condition path are deleted — every condition is CEL, a value-slot literal is handed on as written (#19939 pass 4, S7)

feat(service-automation,lint,spec,verify)!: the single-brace resolver and the legacy condition path are deleted — every condition is CEL, a value-slot literal is handed on as written (#19939 pass 4, S7) #33271

Triggered via pull request October 13, 2026 12:52
Status Failure
Total duration 1m 21s
Artifacts –

pr-automation.yml

on: pull_request
Check PR Size
Check PR Size
Check Changeset
1m 18s
Check Changeset
Auto Label
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 3 notices
Check Changeset: .changeset/pre/22110-flow-text-slot-double-brace.md#L0
.changeset/pre/22110-flow-text-slot-double-brace.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-value-slot-template-dialect-refused.md#L0
.changeset/pre/19939-flow-value-slot-template-dialect-refused.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-value-slot-run-user-refused.md#L0
.changeset/pre/19939-flow-value-slot-run-user-refused.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-value-slot-date-macros-refused.md#L0
.changeset/pre/19939-flow-value-slot-date-macros-refused.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-screen-value-slots.md#L0
.changeset/pre/19939-flow-screen-value-slots.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-notify-value-slots.md#L0
.changeset/pre/19939-flow-notify-value-slots.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-http-slots.md#L0
.changeset/pre/19939-flow-http-slots.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-crud-filter-operands.md#L0
.changeset/pre/19939-flow-crud-filter-operands.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-collection-value-slots.md#L0
.changeset/pre/19939-flow-collection-value-slots.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/pre/19939-flow-callee-input-value-slots.md#L0
.changeset/pre/19939-flow-callee-input-value-slots.md exists on the merge base and was not added by this PR, so changing or deleting it silently replaces somebody else's release note (#17712). Two things produce this refusal and their remedies are OPPOSITE, so read which one you are before you act. COLLISION -- you and another PR drew the same changeset filename, and yours overwrote theirs. Remedy: rename yours; restore theirs from base. DELIBERATE CORRECTION -- your change may have made this PENDING release note false, and you rewrote it in the same stroke. Remedy: do NOT restore it -- say so on the PR and get it confirmed; restoring it from the base would put the false sentence back.
Check Changeset: .changeset/19939-flow-single-brace-resolver-deleted.md#L0
major introduced by this diff in .changeset/19939-flow-single-brace-resolver-deleted.md: @objectstack/service-automation, @objectstack/lint
Check Changeset: .changeset/19939-flow-single-brace-resolver-deleted.md#L0
ADR-0087 exemption (already-registered): The two step-18 D3 entries, registered on this line before this change, record the retirement of the single-brace dialect from every value and text position; this change deletes the resolver behind those positions and the condition path no registered flow reached. No authorable flow surface changes: registerFlow and objectstack validate already refused a braced condition and a template or flow envelope at every condition slot (ADR-0032 §1a), and the residual calls the resolver kept saw literals only. No new D3 entry and no D2 conversion.
Check Changeset
"The ubuntu-latest label will migrate to Ubuntu 26 beginning October 19, 2026. For more information, see https://github.com/actions/runner-images/issues/14748"