CI broken by lack of recent tags in Flutter main/master branch

[gnprice]

CI started failing yesterday with the following error:

Run flutter pub get
Resolving dependencies...
The current Flutter SDK version is 0.0.0-unknown.

Because zulip requires Flutter SDK version >=3.33.0-1.0.pre.832, version solving failed.
[…]

E.g., #1698 (comment) or #1702 (comment).

Diagnosis

I think the problem is that the last tag is more than 1000 commits behind origin/main (or, equally, master). Here's what I found last night (#1698 (comment)):

$ flutter --version
Flutter 3.33.0-1.0.pre-1005 • channel main • https://github.com/flutter/flutter.git
Framework • revision 9c626d9f9a (3 hours ago) • 2025-07-16 23:03:27 -0400
Engine • hash de6ba3d359194bd9ddc0c917c2d1f4c531a63ed0 (revision 9c626d9f9a) (2 hours ago)
• 2025-07-17 03:03:27.000Z
Tools • Dart 3.10.0 (build 3.10.0-6.0.dev) • DevTools 2.48.0

The quick fix is to bump the --depth in ci.yml so that it fetches, say, 2000 commits instead of 1000.

Followup

Then we should probably also follow up to get the upstream Flutter release team to start putting tags in main again, so that version numbers in the main/master channel are accurate. There's been a 3.34 and a 3.35 at this point, so the version number shouldn't be saying "3.33".

The particular symptom above that's breaking our CI is related to our making a shallow clone with git clone --depth. But those inaccurate version numbers are an issue whenever using the main (or master) channel, even when one makes a full clone without using --depth.