@jmagman I was working with plugins and noticed this so I thought I'd just fix it, but just discovered you already had the issue for it assigned to you #101961. Hopefully you haven't worked on it yet and this will save you some time.

One thing, in the issue it says:

Up the Flutter SDK constraint to whatever version #101960 ships on to enforce that the 11.0 migration has happened on the app side.

How can I tell which version that shipped with?

@jmagman How did you know which versions?

Also, looks like the sdk version is now dynamic so I did not change it:

@jmagman How did you know which versions?

Actually it's Flutter 3.1, not 3.3. #101963 was first available in 3.1, and that dart version was 2.18.0, so sdk: ">=2.18.0 <3.0.0" is still the right dart range.

The easiest way to find the corresponding dart version is to checkout the Flutter version and run doctor:

$ git checkout 3.1.0
$ flutter doctor -v
...
[✓] Flutter (Channel unknown, 3.1.0, on macOS 13.2.1 22D68 darwin-x64, locale en-US)
...
    • Dart version 2.18.0 (build 2.18.0-44.1.beta)

Also, looks like the sdk version is now dynamic so I did not change it:

This is why I too haven't done this yet. 🙂

On master on a new plugin the constraint is:

environment:
  sdk: '>=3.0.0-322.0.dev <4.0.0'
  flutter: ">=2.5.0"

I think we should hold off on this for now until we know what the plan is to increase these versions. Fortunately this isn't that urgent, if plugin authors want to adjust these constraints manually, they can, but worst case they keep supporting older versions of Flutter, which isn't a bad thing.

So this is be blocked on #118837, which is actively being worked on #122546
You can either close and wait for all that to settle and re-open, or you can convert this to a draft until that's done.

See also #122739

I think just changing the (comically old) 2.5 to 3.3 is fine here, rather than blocking this. I don't see any downside to doing so while we figure out a longer term plan; it's not worse, and it won't make the long-term change any harder.

I think just changing the (comically old) 2.5 to 3.3 is fine here

(here):

Should we skip to 3.3? We only need 3.1 for this change.

I would do 3.3 rather than 3.1, since 3.3 is the oldest stable with what we need. Hard-coding an old beta version seems weird.

I would do 3.3 rather than 3.1, since 3.3 is the oldest stable with what we need. Hard-coding an old beta version seems weird.

Oh you're right, I forgot 3.1 was just a stable candidate. That versioning is confusing...

Okay @vashworth I stand corrected, if you update the plugin template to flutter: '>=3.1.0' flutter: '>=3.3.0' then this isn't blocked! Thanks @stuartmorgan for jumping in with context.

@jmagman Do you mean 3.3?

I would do 3.3 rather than 3.1, since 3.3 is the oldest stable

Oh you're right, I forgot 3.1 was just a stable candidate. That versioning is confusing...

It's currently 3.3.0, should I change it to 3.3?

@jmagman Do you mean 3.3?

Yes.

It's currently 3.3.0, should I change it to 3.3?

The spot we're talking about is 2.5

Where do you see 3.3.0?

Where do you see 3.3.0?

Sorry, I meant it's already been changed to 3.3.0 in this PR