From b910c81f2af27c77d73d1bb842ef9262f06a0017 Mon Sep 17 00:00:00 2001 From: Krzysztof kuhy Rudnicki Date: Fri, 28 Aug 2026 13:03:16 +0200 Subject: [PATCH] Pin .fvmrc to a Flutter version, not a channel `{"flutter": "stable"}` names a moving target: two machines on the same commit can build with different SDKs, and a freshness check has nothing to compare it against. This is the only .fvmrc in the fleet, and it was the one file the new dependency-freshness gate could not evaluate. Purely declarative today -- nothing in any repo invokes `fvm flutter`, and fvm has no SDKs cached, so the build path is unchanged and still resolves the pacman-installed SDK through ~/.local/bin/flutter. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01CRykabMwPgDzFHcARoqpaK --- meta/.fvmrc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/meta/.fvmrc b/meta/.fvmrc index 5a4e0c20..16a96ef4 100644 --- a/meta/.fvmrc +++ b/meta/.fvmrc @@ -1,3 +1,3 @@ { - "flutter": "stable" + "flutter": "3.47.2" }