Skip to content

fix: Add a version constraint to the material_ui dependency - #4075

Merged
spydon merged 1 commit into
mainfrom
fix/material-ui-version-constraint
Sep 30, 2026
Merged

spydon merged 1 commit into
mainfrom
fix/material-ui-version-constraint

Conversation

@spydon

@spydon spydon commented Sep 30, 2026

Copy link
Copy Markdown
Member

Description

The decoupling migration in #4066 added material_ui: any to every package. dart pub publish refuses an unconstrained dependency, so the Prepare release workflow fails during the dry run:

https://github.com/flame-engine/flame/actions/runs/36740924859/job/109974817579

This constrains it to ^1.0.0 everywhere. All packages already require Flutter >=3.44.0, which is the first stable that ships with material_ui 1.x, so this matches the existing environment without narrowing it further. The resolved version in the lockfile is unchanged.

Checklist

  • I have followed the Contributor Guide when preparing my PR.
  • I have updated/added tests for ALL new/updated/fixed functionality.
  • I have updated/added relevant documentation in docs and added dartdoc comments with ///.
  • I have updated/added relevant examples in examples or docs.

Breaking Change?

  • Yes, this PR is a breaking change.
  • No, this PR is not a breaking change.

The decoupling migration added material_ui as an unconstrained
dependency, which makes pub publish fail validation and broke the
prepare release workflow. All packages already require Flutter 3.44,
which ships with material_ui 1.x, so ^1.0.0 matches the existing
environment.
@spydon
spydon enabled auto-merge (squash) September 30, 2026 19:38
@spydon
spydon disabled auto-merge September 30, 2026 19:45
@spydon
spydon merged commit 7ce35d8 into main Sep 30, 2026
9 checks passed
@spydon
spydon deleted the fix/material-ui-version-constraint branch September 30, 2026 19:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants