Repository navigation
when is Flame v1.38.0 expected to be available via flutter pub upgrade? #3973
|
I have code that is working around the fact that the HasWorldReference.onRemove didn't call super and wanted to know when I would safely be able to remove that code |
Replies: 1 comment 1 reply
|
It's already out. 1.38.0 landed on pub.dev on 19 July, and your fix is in it. From the changelog: FIX: HasWorldReference.onRemove() should call super.onRemove() (#3920) So the workaround can go as soon as you upgrade. If If you use Heads up that 1.38.0 has breaking changes, including a new |
It's already out. 1.38.0 landed on pub.dev on 19 July, and your fix is in it. From the changelog:
FIX: HasWorldReference.onRemove() should call super.onRemove() (#3920)
So the workaround can go as soon as you upgrade.
If
flutter pub upgradeisn't picking it up, a plain^1.37.0isn't the reason. That resolves to>=1.37.0 <2.0.0, so 1.38.0 is already allowed. The usual culprits are the lockfile or a companion package holding you back:If you use
flame_tiled,flame_forge2dor similar, one of them may still cap flame below 1.38.0, and pub will silently keep you on the highest version that satisfies everyone.flutter pub upgrade flamewill name the constraint tha…