Fix Cloudsmith publish step broken by cloudsmith-cli release-layout change - #6316
Merged
Andriy Knysh (aknysh) merged 3 commits intoAug 5, 2026
Merged
Conversation
…-layout change cloudsmith-io/action@v0.6.10's install step naively downloads GitHub release assets[0] for "latest" cloudsmith-cli and execs it directly. That worked only because cloudsmith-cli used to publish a single raw binary; it now publishes separate per-platform .tar.gz archives, so assets[0] can resolve to the wrong architecture (or a non-executable archive), breaking every apk/deb/rpm publish with "Exec format error". Bumping the action's pin doesn't fix it: v0.6.14 switches to a Python-based install that requires actions/setup-python, which doesn't support the Alpine/musl containers this repo builds in. Replace the dependency on cloudsmith-io/action with a small local composite action (.github/actions/cloudsmith-push) that installs a pinned, known-good cloudsmith-cli release directly (the static musl build, portable across musl and glibc containers) and invokes `cloudsmith push` itself. Regenerated all package workflows from the updated template via `make -C .github workflows`. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Erik Osterman (Cloud Posse) (osterman)
requested a review
from a team
as a code owner
August 5, 2026 21:30
The "musl" cloudsmith-cli tarball is dynamically linked against musl (interpreter /lib/ld-musl-x86_64.so.1), not statically linked as assumed. That path only exists on Alpine, so every deb/rpm publish job (glibc-based containers) failed with "No such file or directory" execing the binary. Select the musl vs gnu variant based on the container (/etc/alpine-release), not unconditionally. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
aquasecurity/trivy deleted the v0.68.2 GitHub release (the git tag still exists, but there's no published Release, so every download of trivy_0.68.2_Linux-64bit.tar.gz 404s). This broke both the trivy apk build (alpine-trivy) and the build-and-push Dockerfile step, which installs trivy as one of the build-time tools baked into the base image. Verified the new version's release assets resolve for all platforms this repo builds. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Andriy Knysh (aknysh)
approved these changes
Aug 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
what
cloudsmith-io/action@v0.6.10with a new local composite action,.github/actions/cloudsmith-push, for the "Push artifact to package repository" step..github/workflows/*.ymlpackage workflows from the updated.github/package-template.yml(mechanical substitution only, no other changes).why
cloudsmith-io/action@v0.6.10's install step downloads GitHub releaseassets[0]for "latest"cloudsmith-cliand execs it directly. That only worked becausecloudsmith-cliused to publish a single raw binary; it now publishes separate per-platform.tar.gzarchives, soassets[0]can resolve to the wrong architecture or a non-executable archive, breaking every apk/deb/rpm publish withExec format error(e.g. https://github.com/cloudposse/packages/actions/runs/31040732661/job/92428197131).actions/setup-python, which doesn't support the Alpine/musl containers this repo builds packages in.cloudsmith-clirelease directly (the statically-linked musl build, portable across musl and glibc containers) and invokescloudsmith pushitself, removing the fragile dependency on an unpinned upstream "latest release" lookup.references