-
Notifications
You must be signed in to change notification settings - Fork 29.1k
Update CHANGELOG.md to include link to 3.35 changelog #173869
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
add link to 3.35 blog post as proxy for 3.35 changelog
This pull request was opened against a branch other than master. Since Flutter pull requests should not normally be opened against branches other than master, I have changed the base to master. If this was intended, you may modify the base back to stable. See the Release Process for information about how other branches get updated. Reviewers: Use caution before merging pull requests to branches other than master, unless this is an intentional hotfix/cherrypick. |
There was a problem hiding this 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 introduces significant changes beyond what the title suggests. While the title mentions updating CHANGELOG.md
, the core of this PR is a major refactoring of the iOS device deployment and debugging workflow, notably adding support for LLDB-based debugging for CoreDevices. This includes:
- A new
IOSCoreDeviceLauncher
to handle different launch strategies. - A new
lldb.dart
library to interact with the LLDB process. - Refactoring of
IOSDevice
to use the new launcher and decide between LLDB and Xcode debugging. - Updates to
devicectl
interaction incore_devices.dart
. - Refactoring of the
last_engine_commit
scripts to be more robust on release branches.
The changes appear to be well-structured and improve the iOS tooling. My main feedback is a small robustness improvement for the last_engine_commit.sh
script to handle cases where a file might not exist, ensuring custom error messages are displayed correctly.
bin/internal/last_engine_commit.sh
Outdated
MERGE_BASE_COMMIT="$(git merge-base HEAD master || echo "")" | ||
# 1. Determine when the release branch was started, and prevent set -e from exiting. | ||
RELEASE_CANDIDATE_VERSION_PATH="$(git rev-parse --show-toplevel)/bin/internal/release-candidate-branch.version" | ||
REFERENCE_COMMIT="$(git log -1 --pretty=format:%H -- "$RELEASE_CANDIDATE_VERSION_PATH")" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This command will cause the script to exit if git log
fails (e.g., if $RELEASE_CANDIDATE_VERSION_PATH
doesn't exist), due to set -e
. This would prevent your custom error message below from being displayed. To ensure your custom error handling is triggered, you should prevent the script from exiting on failure here, similar to how the old script handled git merge-base
.
You can append || true
to the command to prevent it from exiting the script on failure.
REFERENCE_COMMIT="$(git log -1 --pretty=format:%H -- "$RELEASE_CANDIDATE_VERSION_PATH")" | |
REFERENCE_COMMIT="$(git log -1 --pretty=format:%H -- "$RELEASE_CANDIDATE_VERSION_PATH" || true)" |
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. |
An existing Git SHA, To re-trigger presubmits after closing or re-opeing a PR, or pushing a HEAD commit (i.e. with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Changed the base branch to flutter-3.35-candidate.0 |
@camsim99 Can you merge this in? |
Detected the If you add the The "Merge" button is also unlocked. To bypass presubmits as well as the tree status, press the GitHub "Add to Merge Queue". |
Adding emergency label to override tree status which should probably not apply to release branches. |
Thank you for the help here! |
@sethladd According to this response #173966 (comment) you need to push an amendment or new commit to retrigger ci.yaml validation. I am not aware of another way to rerun or unstall that check and that check ignores the emergency label. The good news is that changelog only prs run a very small subset of tests so hopefully it will be fast. |
thanks! pushed a cosmetic change |
autosubmit label was removed for flutter/flutter/173869, because - The status or check suite Linux analyze has failed. Please fix the issues identified (or deflake) before re-applying this label. |
Re-runnning linux analyze. It found ktlint violations but that appears to be because java was missing. |
Thank you! |
Just to be clear, it doesn't look like we install the Java (JDK) during this builder: Lines 349 to 351 in 2265d94
|
add link to 3.35 blog post as proxy for 3.35 changelog
Pre-launch Checklist