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

repo/lockfile-committed

Dependency lockfile is committed

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.

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

Requirement

Each stack’s dependency manager has its lockfile tracked in git next to the manifest, or, for a member of a workspace that keeps one lockfile for all members (npm, pnpm, yarn and bun workspaces, Cargo, uv and pub workspaces), at the workspace root; a manifest without dependencies needs none.

Why

Builds are reproducible only when dependency versions are pinned in git.

Fix

Generate the lockfile with the package manager and commit it; remove it from .gitignore.

Agent instruction: Run the package manager to produce the lockfile, remove any .gitignore entry for it, and commit it.

Sources


Generated by fleetlint docs from catalog v0.8.0.