Skip to content

fix: invoke scalar deploy without subcommand - #140

Merged
hseshadr merged 1 commit into
mainfrom
fix/deploy-scalar-terminal-20260829
Aug 30, 2026
Merged

fix: invoke scalar deploy without subcommand#140
hseshadr merged 1 commit into
mainfrom
fix/deploy-scalar-terminal-20260829

Conversation

@hseshadr

Copy link
Copy Markdown
Owner

Summary

  • remove the invalid trailing sync from the scalar deploy invocation
  • add a fail-closed workflow mutant that prevents terminal subcommands from returning
  • preserve the exact protected run, secret, environment, and provider boundaries

Incident evidence

Exact-main deploy run 33285975502 failed during CLI argument parsing with unknown command "sync" for "dagger call deploy". Parsing stopped before the deploy function or provider transport executed.

Verification

  • RED: focused workflow contract failed only the committed deploy job
  • GREEN: focused workflow contracts 24/24
  • Foundation/deployment/workflow contracts 82/82
  • actionlint
  • zizmor 1.29.0 targeted + full
  • dagger develop
  • real generated deploy help verifier
  • cached dagger call contracts stdout
  • independent review: Ready Yes, no P0-P3 findings

No deploy, provider, environment, or secret mutation was performed.

@hseshadr
hseshadr merged commit 5a66394 into main Aug 30, 2026
2 checks passed
@hseshadr
hseshadr deleted the fix/deploy-scalar-terminal-20260829 branch August 30, 2026 02:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant