Skip to content

ci(docker): only upload standalone binaries when a release will use them #223

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
shockalotti merged 1 commit into from
Nov 4, 2026
Merged

ci(docker): only upload standalone binaries when a release will use them #223

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
9 changes: 9 additions & 0 deletions .github/workflows/docker-publish.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -128,7 +128,16 @@ jobs:
cd dist/release
sha256sum ./*.tar.gz > checksums.txt

# Only upload when a release job will consume the artifact. Exporting and
# packaging above stay ungated on purpose: they prove the `standalone` stage
# still builds on every PR, so a break is caught there rather than during a
# release. This step is the one that costs storage for nothing on PRs and
# branch pushes.
#
# The condition must match the `release` job exactly, including the
# workflow_dispatch dry run, or the rehearsal finds no artifact to download.
- name: Upload standalone binaries
if: startsWith(github.ref, 'refs/tags/v') || (github.event_name == 'workflow_dispatch' && inputs.dry_run)
uses: actions/upload-artifact@v7
with:
name: standalone-binaries
Expand Down
Loading