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

deps/locked-install/kotlin

Installs use the lockfile strictly

Implements deps/locked-install for kotlin.

Severitywarning
Tiers1, 2
Stackskotlin
Scopeeach
Kindexpr
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

Gradle checks resolved versions against gradle.lockfile (and artifacts against verification metadata) on every build; this holds unless a recipe or CI step outside an update target passes --write-locks, --update-locks or --write-verification-metadata, which is what is checked.

Why

An install that quietly re-resolves builds and tests something other than what the lockfile in git says, and the drift shows up only in production.

Check

!(taskrunner.recipes.filter(t, !t.matches(r'(?i)update|upgrade|lock|bump|renovate')).map(t, taskrunner.recipes[t]).flatten()
    + workflows().map(w, steps(w).map(s, s.run.split("\n")).flatten()).flatten())
    .filter(l, !l.matches(params.noise)).exists(l, l.matches(r'--(write|update)-locks\b|--write-verification-metadata\b'))

Parameters

  • noise: ^\s*[@+-]*\s*(\{\{[^}]*\}\}\s*|\$[({][A-Za-z_]+[)}]\s*)?(#|//|echo\b|printf\b)

Fix

Move lock updates to an update-locks target that is not part of CI.

Agent instruction (from deps/locked-install): Switch the CI and task-runner installs to the package manager’s locked mode; if that fails, regenerate the lockfile in a separate commit rather than relaxing the install.

Sources


Generated by fleetlint docs from catalog v0.8.0.