Question about pub updating the pubspec.lock file

Ever since updating our Flutter app projects to Dart 3.9.0, Dependabot has started adding `flutter: ">=3.35.5"` to the `pubspec.lock` file. Previously it was `flutter: "3.35.5"`, which would be in line with the configuration of the project overall.

When running our build pipeline afterwards the regular `pub get` resets this back to `flutter: "3.35.5"`, which then causes problems because the working tree is no longer clean.

Is there a way to prevent this from happening?

Start by reproducing the reported difference between Dependabot's pubspec.lock output and the result of running pub get in the Flutter app projects. Compare the Flutter constraint entries before and after each operation, then determine whether the dependency update behavior or the pipeline expectation should change. Done means the lockfile remains consistent after the normal build step.

Written by the indexing model from the issue text.