Install a pinned tool release

Download one pinned, checksummed release in shared setup and skip the per-worker package-manager upgrade.

Prompt

Evaluate and apply this CI technique to my repository: Install a pinned tool release.

Download one pinned, checksummed release in shared setup and skip the per-worker package-manager upgrade.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/pin-small-tool-install.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How Stripe used this technique

Read what Stripe changed and follow the original sources.

Install a pinned tool release

Stripe iOS replaced a Homebrew upgrade of xcodes on every worker with a download of a specific release, checked against a SHA-256, in one shared install workflow.

Use it when: Shared CI setup updates a package manager on every run to obtain one CLI.
Before applying it: Verify the checksum before running the binary, keep platform compatibility, and give someone ownership of version updates.

How Stripe used this technique

Install a pinned tool release

Related techniques

Build before starting the emulator

Release query results before they become a timeout

Reuse exact baseline analysis results

Company Playbooks