ci: pin autotag binary by version + sha256#145
Open
joemiller wants to merge 1 commit into
Open
Conversation
Replace the deprecated `git.io/autotag-install` one-liner with a direct download of `autotag_linux_amd64` from a pinned release, verified against a hardcoded SHA-256. Why: - The installer is generated by godownloader (also deprecated upstream) and, while it does check the checksum file published with each GitHub release, those checksums are mutable — anyone who can publish a release can publish matching checksums. There's no way to pin an out-of-band expected SHA. - autotag's maintainers are me and a couple of trusted ex-coworkers (incl. @will.milton) and I trust the code, but a compromise of the `autotag-dev` org or a maintainer account would silently flow into every pipeline that runs the installer. Hardcoding the SHA in our workflow makes that class of supply-chain attack fail loudly. - autotag rarely changes and we only use its most basic functionality, so we don't upgrade often. Grabbing the new binary's SHA from `checksums.txt` on bump is a cheap one-time step for meaningful hardening. See: https://github.com/autotag-dev/autotag/blob/main/README.md (CI install section) for the recommended pattern.
dctrwatson
approved these changes
May 15, 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.
Summary
Replace the deprecated
git.io/autotag-installone-liner in.buildkite/Dockerfile.releasewith a direct download ofautotag_linux_amd64from a pinned release (v1.4.3), verified against a hardcoded SHA-256.Why
autotag-devorg or a maintainer account would silently flow into every pipeline that runs the installer. Hardcoding the SHA in our workflow makes that class of supply-chain attack fail loudly.checksums.txton bump is a cheap one-time step for meaningful hardening.See: autotag README, CI install section.
Second commit bumps stale README version examples so the plugin-linter passes.
Test plan
mainand verify the release container builds.