Skip to content

Conversation

@justinmc
Copy link
Contributor

The version I set in #176799 was incorrect so the release build failed. This updates it to the correct engine version.

@justinmc justinmc requested a review from camsim99 October 17, 2025 18:05
@justinmc justinmc self-assigned this Oct 17, 2025
@justinmc justinmc requested a review from jtmcdole as a code owner October 17, 2025 18:05
@github-actions github-actions bot added the engine flutter/engine related. See also e: labels. label Oct 17, 2025
@justinmc justinmc changed the base branch from master to flutter-3.38-candidate.0 October 17, 2025 18:05
@flutter-dashboard
Copy link

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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the content-aware hashing scripts to correctly detect the LUCI CI environment by checking for the LUCI_CONTEXT environment variable instead of LUCI_CI. The corresponding tests are updated to reflect this change. Additionally, a temporary file, engine/TRIGGER.md, is added to trigger a new engine release build by changing the engine's content-aware hash.

Copy link
Contributor

@camsim99 camsim99 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks right to me since ced5a93 didn't touch the engine!

@camsim99
Copy link
Contributor

Sigh maybe that commit doesn't work because it was pre the fix for #176838. Maybe @jtmcdole can confirm. If so, do we need introduce another bogus engine change? Maybe we can delete the file I added in #176842

auto-submit bot pushed a commit that referenced this pull request Oct 17, 2025
My PR updating engine.version (#177178) for the 3.38.0 beta release isn't passing the analyzer because the engine artifacts don't exist. This PR will trigger another engine build, and then I'll use its merge SHA in engine.version. And it conveniently deletes the file used for this same purpose in #176842.
@github-actions github-actions bot removed the engine flutter/engine related. See also e: labels. label Oct 17, 2025
@justinmc
Copy link
Contributor Author

justinmc commented Oct 17, 2025

Alright I have merged another PR that deletes the engine file (#177181) and updated the SHA to that merge commit. The analyzer test just failed because the engine artifacts haven't finished building yet. After they finish I will rerun and, if we're right, it should pass.

@justinmc justinmc added the autosubmit Merge PR when tree becomes green via auto submit App label Oct 17, 2025
@auto-submit auto-submit bot merged commit 7e592fe into flutter:flutter-3.38-candidate.0 Oct 17, 2025
5 checks passed
@justinmc justinmc deleted the 3.38.0-beta-engine-version branch October 17, 2025 23:08
engine-flutter-autoroll added a commit to engine-flutter-autoroll/packages that referenced this pull request Nov 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

autosubmit Merge PR when tree becomes green via auto submit App

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants