Skip to content
PR Automation

feat(types,triggers,service-automation,runtime,cli,spec,lint)!: package-authored scheduled work is a deployment decision, off by default #24999

Sign in to view logs

feat(types,triggers,service-automation,runtime,cli,spec,lint)!: package-authored scheduled work is a deployment decision, off by default

feat(types,triggers,service-automation,runtime,cli,spec,lint)!: package-authored scheduled work is a deployment decision, off by default #24999

Triggered via pull request September 14, 2026 14:51
@os-warrenos-warren
synchronize #18198
claude/issue-17396-schedule-flow-deployment-switch
Status Failure
Total duration 47s
Artifacts –

pr-automation.yml

on: pull_request
Check PR Size
17s
Check PR Size
Check Changeset
43s
Check Changeset
Auto Label
16s
Auto Label
Fit to window
Zoom out
Zoom in

Annotations

2 errors
Check Changeset
Process completed with exit code 1.
Check Changeset: .changeset/schedule-trigger-acting-organization.md#L0
.changeset/schedule-trigger-acting-organization.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.