Jacob MacDonald

Unfortunately there can't be any perfect solution here in build_runner because the analysis_options.yaml files are not always going to be readable by the build. However, we could support very specifically...

The upper bound isn't just there for no reason... we have a somewhat tight upper bound as an agreement with the web compiler team, because it allows those tools (and...

New versions have been published that allow 3.3.x, not closing this for now though since I think there is more discussion to be had for future releases.

Fwiw - we have a similar situation with `dart_internal`. So whatever process we have for that package could be also used for these packages? For macros we also plan to...

I am definitely happy to do a pre-emptive bump. It typically should not take more than a day of turnaround time. I just don't know how to coordinate that with...

I added a row to the release checklist template under the dart_internal bump

Is that sufficient to close this issue? Presumably I will get assigned a task for future releases?

Basically what Nate said, this package has a tight SDK dependency because it utilizes directly various tools shipped with the SDK. As an example, sometimes certain resources (SDK summaries for...

+1 I think this is a process issue and not a technical issue. We can publish these versions well in advance, we just need to be notified to do so....

> but to move development to the SDK repo, so the SDK version bump and the change to the dependency constraint can happen together Ah, you still have to publish...