Skip to content

Guard Cloudsmith exit code before GHCR push in Windows nightlies - #328

Merged
SeanTAllen merged 1 commit into
mainfrom
guard-windows-cloudsmith-exit-code
May 29, 2026
Merged

Guard Cloudsmith exit code before GHCR push in Windows nightlies#328
SeanTAllen merged 1 commit into
mainfrom
guard-windows-cloudsmith-exit-code

Conversation

@SeanTAllen

Copy link
Copy Markdown
Member

The two Windows nightly jobs run the Cloudsmith push and the GHCR push in the same pwsh step. In a pwsh step the step's exit code is that of the last native command, so a failed Cloudsmith push followed by a successful GHCR push would exit 0 — the board goes green, no Zulip alert fires, and the nightly never reaches Cloudsmith, the primary download source.

This adds an explicit $LASTEXITCODE guard after the Cloudsmith push in both Windows jobs, matching what ponyc's release.yml already does. The Linux/macOS jobs are unaffected because their bash scripts use set -e.

Closes #327

In a pwsh step the step's exit code is that of the last native command,
so a failed Cloudsmith push followed by a successful GHCR push exits 0 and
masks the failure to the primary download source. The Linux/macOS jobs are
unaffected because their bash scripts use set -e.

Closes #327
@SeanTAllen
SeanTAllen merged commit e931ec8 into main May 29, 2026
9 checks passed
@SeanTAllen
SeanTAllen deleted the guard-windows-cloudsmith-exit-code branch May 29, 2026 02:56
@ponylang-main ponylang-main added discuss during sync Should be discussed during an upcoming sync and removed discuss during sync Should be discussed during an upcoming sync labels May 29, 2026
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.

Windows nightly upload can silently mask a Cloudsmith failure

2 participants