Update engine.version

[camsim99]

Sets engine.version to release build from 3eead6b. Part of #176744

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• I followed the breaking change policy and added Data Driven Fixes where supported.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[flutter-dashboard]

This pull request was opened from and to a release candidate branch. This should only be done as part of the official Flutter release process. If you are attempting to make a regular contribution to the Flutter project, please close this PR and follow the instructions at Tree Hygiene for detailed instructions on contributing to Flutter.

Reviewers: Use caution before merging pull requests to release branches. Ensure the proper procedure has been followed.

[gemini-code-assist]

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

[camsim99]

Hmm the release builder ran on this commit so I thought the test would pass?

[camsim99]

In the meantime, running postsubmits on the previous commit. I did this by accident but there are actual errors, e.g. https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_arm64%20verify_binaries_codesigned/628/overview and https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20Production%20Engine%20Drone/1305670/overview

I may need to dig into this first.

[jtmcdole]

Release builder is required to build all the binaries? I can't see the results, but 3eead6b0480ba4aacab8f0e0d058ac77f550bc1d Is the correct hash

[jtmcdole]

59c4900 is not a valid githash... 404: 59c4900

curl --head https://storage.googleapis.com/flutter_infra_release/flutter/59c4900ce5d1ecf691330e7e6abc7d5821feffd2/flutter-web-sdk.zip
HTTP/2 404
content-type: application/xml; charset=UTF-8
x-guploader-uploadid: AAwnv3J44F-ZcuoS1vzDq4kYfDbpL8z_h0f3gCl3XGNlYS9YkiOKn9mGRrmaKnKym7xiyo4gL6V94AI
content-length: 252
access-control-allow-origin: *
access-control-expose-headers: Content-Type
date: Thu, 09 Oct 2025 19:54:10 GMT
expires: Thu, 09 Oct 2025 19:54:10 GMT
cache-control: private, max-age=0
server: UploadServer
alt-svc: h3=":443"; ma=2592000,h3-29=":443"; ma=2592000

[camsim99]

59c4900 is not a valid githash... 404: 59c4900

Looks like you're talking about https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20Production%20Engine%20Drone/1305670/overview. Do you know where that commit is even coming from?

[justinmc]

This is out of date as of the cherry pick #176883. I will update this PR or create a new PR after that build succeeds.

[justinmc]

I was able to push a commit to update the hash 👍