Skip to content

ci: bump pinned Flutter SDK to version 3.41.9#8955

Closed
github-actions[bot] wants to merge 1 commit into
mainfrom
auto-update-flutter-sdk
Closed

ci: bump pinned Flutter SDK to version 3.41.9#8955
github-actions[bot] wants to merge 1 commit into
mainfrom
auto-update-flutter-sdk

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented May 6, 2026

An automated check has detected a new stable release of the Flutter SDK.

  • New Pinned Version: 3.41.9

This Pull Request updates our shared provisioning script (tool/provision_flutter.sh) to target this version. All presubmit tests will be run against this version to verify compatibility.

@google-cla
Copy link
Copy Markdown

google-cla Bot commented May 6, 2026

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@pq
Copy link
Copy Markdown
Collaborator

pq commented May 6, 2026

Closing in favor of a retry.

@pq pq closed this May 6, 2026
@pq pq deleted the auto-update-flutter-sdk branch May 6, 2026 23:07
pq added a commit that referenced this pull request May 7, 2026
Our automated Flutter SDK version-bump presubmit was failing to trigger
subsequent CI/CD test workflows and was getting blocked by Google's CLA
check. (See for example: #8955.)

* Standard `GITHUB_TOKEN` creations do not trigger downstream actions on
PR creation (preventing presubmit tests from running on the PR).
* system `github-actions[bot]` commits are not registered with Google's
CLA bot, blocking the merge path.

This PR configures the workflow to authenticate using our organization's
pre-approved `flutteractionsbot` credentials, enabling instant CLA
compliance and automatic presubmit test execution. (Note I had to create
a fork of this repo for `flutteractionsbot` behind the scenes,
explaining some action failures leading up to the success below).

I verified this works by manually kicking off the action, which produced
this PR:

#8958

which has the right CLA credentials:

<img width="1832" height="534" alt="image"
src="https://github.com/user-attachments/assets/c39b2e4c-910b-4399-9d81-cd743b80cf9b"
/>

Completes the work started in #8953. 

🚀 🚀 🚀 

---

### Proposed Changes

* **[Modified]
[.github/workflows/update_flutter.yaml](file:///+github/workflows/update_flutter.yaml)**:
* Configured the `Checkout` and `Create Pull Request` steps to
authenticate via the organization's `secrets.FLUTTERACTIONSBOT_CP_TOKEN`
PAT.
* Explicitly overrode `committer` and `author` git metadata to match
`flutteractionsbot <flutter-actions-bot@google.com>` to pass Google's
CLA checks automatically.
* Configured `push-to-fork: flutteractionsbot/flutter-intellij` to push
the PR branch to the bot's fork, bypassing upstream main-branch push
restrictions.

---

### Verification Results
* **JUnit Integrity Tests**: Checked locally using `./gradlew test
--tests io.flutter.CIIntegrityTest` — **BUILD SUCCESSFUL** (all
meta-tests compile and pass).
* **YAML Syntax Vetted**: Validated structured parameters against the
latest `peter-evans/create-pull-request` specifications.

Replaces #8956

---

Review the contribution guidelines below:

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.
- [x] I've included the required information in the description above.
- [x] My up-to-date information is in the `AUTHORS` file.
- [x] I've updated `CHANGELOG.md` if appropriate.

<details>
  <summary>Contribution guidelines:</summary><br>

- See
  our [contributor guide](../CONTRIBUTING.md) and
the [Flutter organization contributor
guide]([https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md)
  for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Dart contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use
  `dart format`.
- Java and Kotlin contributions should strive to follow Java and Kotlin
best
practices
([discussion](#8098)).

</details>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant