[erikdarlingdata]

Why

The first dev run of the two-job dependency submission workflow from #656, run 38660830104, failed at the Restore SSMS projects step:

msbuild: command not found
Error: Process completed with exit code 127.

The submit job was skipped, so dev got no snapshot from that run.

Cause

The round-1 review of #656 switched that step to shell: bash so the first failing restore would fail the step (pwsh only reports the last command's exit code). On the Windows runner the msbuild folder that microsoft/setup-msbuild adds to PATH reaches pwsh steps but not bash steps. The green run before that change (38657114293) ran the step under pwsh.

Change

One step in .github/workflows/dependency-submission.yml:

• shell: pwsh instead of shell: bash.
• Each of the three restore commands is followed by if ($LASTEXITCODE) { exit $LASTEXITCODE }, so a failure in the first or second command still fails the step.
• The comment above the step explains both points and names the failed run.

Nothing else in the workflow changes. The submit job, the snapshot script and the artifact handling are untouched.

Verification

• The workflow runs on push to dev, so the merge of this PR is the test. Expected: detect and submit both green, and the submit log prints result: ACCEPTED (dev is not the default branch, so GitHub accepts the snapshot without using it for alerts).

Refs #655.

🤖 Generated with Claude Code

https://claude.ai/code/session_018MrD9SGvLFx4kJaeGZyXG9

[claude]

Reviewed the diff: a single workflow step switched to pwsh with per-command $LASTEXITCODE checks. The check after the last msbuild call is redundant, since pwsh already reports the last command's exit code. It's harmless. I found no correctness, security or convention issues. The merge to dev is the real test, as the description says.