Skip to content

ci: remove workflow_dispatch from web-production #54

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
lukeocodes merged 1 commit into from
May 4, 2026
+6 −1
Merged

ci: remove workflow_dispatch from web-production #54

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
7 changes: 6 additions & 1 deletion .github/workflows/web-production.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,13 @@ on:
# Using workflow_call avoids the GitHub Actions limitation where
# GITHUB_TOKEN-created releases do not trigger release: published
# in other workflows.
#
# workflow_dispatch is intentionally omitted: deploying main outside
# the release pipeline can ship a landing page that advertises a
# version not yet published to PyPI (the cli.deepgram.com vs PyPI
# skew that broke installs in May 2026). Production deploys must be
# gated on a real root v* tag.
workflow_call:
workflow_dispatch:

# Only one production deploy at a time; never cancel in-progress
concurrency:
Expand Down
Loading