Repository navigation
Bumping version tag of provisioning profile cipd package. (#137710) - #137782
auto-submit[bot] merged 2 commits into
Conversation
…7710) Bug:flutter#137166 *Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.* *List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.* *If you had to change anything in the [flutter/tests] repo, include a link to the migration guide as per the [breaking change policy].*
|
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. |
| dependencies: >- | ||
| [ | ||
| {"dependency": "apple_signing", "version": "version:2022_to_2023"} | ||
| {"dependency": "apple_signing", "version": "version:to_2024"} |
There was a problem hiding this comment.
yes, thats whats checked in currently
XilaiZhang
added
the
autosubmit
|
Looks like |
XilaiZhang
added
autosubmit
|
Can someone attach an approval to this pull request for it to be merged? Thank you! maybe @CaseyHillers? |
XilaiZhang
left a comment
XilaiZhang
left a comment
There was a problem hiding this comment.
I will stamp a LGTM here to unblock the release
XilaiZhang
added
autosubmit
5 participants
Bug:#137166
Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue. An issue is not required if the PR fixes something trivial like a typo.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist
///).If you need help, consider asking for advice on the #hackers-new channel on Discord.