fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

repo/toolchain-pinned

Toolchain version is pinned

A capability: each stack checks it with its own tools, and every implementation that runs must pass. Implemented for cpp, dotnet, flutter, go, hugo, java, kotlin, node, php, python, ruby, rust.

Severitywarning
Tiers1, 2
Stacksany
Scopeeach
Kindcapability
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

Each stack pins its compiler or runtime to a version in a file the tools read, in the project’s directory or a parent directory (for a workspace member, typically the repository root): the stack’s version file, .tool-versions / mise.toml naming the stack’s tool with a version, or devbox.json naming its package with a version. A file that names another tool, or a moving alias like lts or latest, does not count.

Why

Without a pin, every machine and every CI run builds with whatever compiler or runtime happens to be installed, and failures cannot be reproduced.

Fix

Add the stack’s version file with the version you build with today.

Agent instruction: Add the stack’s toolchain pin set to the version currently installed; do not upgrade the toolchain in the same change.

Sources


Generated by fleetlint docs from catalog v0.8.0.