deps/locked-install/flutter
Installs use the lockfile strictly
Implements deps/locked-install for flutter.
| Severity | warning |
| Tiers | 1, 2 |
| Stacks | flutter |
| Scope | each |
| Kind | expr |
| Source | library v0.3.1 |
| Selected by | fleetlint-recommended@v0.3.1 |
Requirement
A recipe or CI step runs flutter pub get --enforce-lockfile (or dart pub get --enforce-lockfile), and none runs pub upgrade outside an update target.
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()
+ params.runners.filter(f, file(f)).map(f, lines(f)).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'\b(flutter|dart)\s+pub\s+get\b[^;&|]*--enforce-lockfile\b'))
&& !(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'\b(flutter|dart)\s+pub\s+upgrade\b'))Parameters
noise:^\s*[@+-]*\s*(\{\{[^}]*\}\}\s*|\$[({][A-Za-z_]+[)}]\s*)?(#|//|echo\b|printf\b)runners:[../Makefile ../justfile ../Justfile ../Taskfile.yml ../Taskfile.yaml ../../Makefile ../../justfile ../../Justfile ../../Taskfile.yml ../../Taskfile.yaml ../../../Makefile ../../../justfile ../../../Justfile ../../../Taskfile.yml ../../../Taskfile.yaml]
Fix
Run flutter pub get --enforce-lockfile in CI before the checks.
Agent instruction: 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.
See: https://fleetlint.org/baseline/#dependencies, https://fleetlint.org/stacks/#flutter--dart
Generated by fleetlint docs from catalog v0.3.1.