Repository navigation
chore(ci): Flutter 3.47.7 - #1842
Merged
Merged
Conversation
…nux touch-event leak, libpng security fix)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the pinned Flutter from 3.47.1 to 3.47.7 in every workflow, the devcontainer Dockerfile and the docs.
Why: 3.47.6 fixes Windows production apps hanging (flutter/192513); 3.47.2 fixes a Linux touch-event memory leak (flutter/190518), Linux screen-reader headers and a libpng security issue.
Do not merge until the vsync-patched Linux engine for the new content hash
d8a2d6c768c334d53e16277f837970ffa1e2de81is published in QueryaHub/flutter-engine-linux-120hz (tagengine-d8a2d6c7…). Otherwiseapply_patched_engine.shonly warns and the Linux build ships the stock 60 fps engine (#980). After merging, check that the Linux job log saysspliced in vsync-patched engine.