Skip to content

[Wrangler/Workflows] Add warning on deploy of workflows belonging to other workers #12513

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pombosilva merged 6 commits into from
Feb 11, 2026
Merged

[Wrangler/Workflows] Add warning on deploy of workflows belonging to other workers #12513

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
dad9c21
[Wrangler/Workflows] Add warning on deploy of workflows belonging to …
pombosilva Feb 10, 2026
315f748
fix: use deployConfirm for workflow conflict check and skip in non-in…
pombosilva Feb 10, 2026
14b7db6
fix: use workflow fetch directly
pombosilva Feb 10, 2026
5ab26b7
fix: address review comments
pombosilva Feb 11, 2026
fafddae
change version type to patch
pombosilva Feb 11, 2026
9501405
Address review comments
pombosilva Feb 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions .changeset/workflow-conflict-warning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
"wrangler": patch
---

Add confirmation prompt when deploying workflows with names that belong to different workers.

When deploying a workflow with a name that already exists and is currently associated with a different worker script, Wrangler will now display a warning and prompt for confirmation before proceeding. This helps prevent accidentally overriding workflows.

In non-interactive environments this check is skipped by default. Use the `--strict` flag to enable the check in non-interactive environments, which will cause the deployment to fail if workflow conflicts are detected.
Loading
Loading