[cupertino_ui] Batch release - #12410
Closed
fluttergithubbot wants to merge 1 commit into
Closed
Conversation
fluttergithubbot
added
the
override: batch-cupertino_ui
github-actions
Bot
added
triage-framework
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the cupertino_ui package version to 0.0.3+1 in pubspec.yaml, adds a corresponding entry in CHANGELOG.md regarding the removal of an unresolvable doc import for flutter_test, and removes a temporary changelog metadata file. There are no review comments, and I have no feedback to provide.
auto-submit Bot
pushed a commit
that referenced
this pull request
Aug 10, 2026
Updates the `enabled_branches` regex patterns in `.ci.yaml` to support SemVer release branch names with optional pre-release tags (e.g., `-dev.1`) and build metadata suffixes (e.g., `+1`). Previously, `enabled_branches` used the strict pattern `release-<package>-\d+\.\d+\.\d+`. When release branches were created with build metadata suffixes (e.g., `release-material_ui-0.0.3+1`), Cocoon CI failed validation with: > `release-material_ui-0.0.3+1 is not enabled for this .ci.yaml. Add it to run tests against this PR.` Blocked PRs: - #12412 - #12410 Updated the regex for release branches to `release-<package>-\d+\.\d+\.\d+(?:-[\w.]+)?(?:\+[\w.]+)?`, allowing valid SemVer pre-release and build metadata identifiers while maintaining strict matching against non-version branch names. ### Pattern Verification Examples | Branch Name | Match Result | Status | | --- | --- | --- | | `release-material_ui-0.0.3` | **Match** | ✅ Standard SemVer | | `release-material_ui-0.0.3+1` | **Match** | ✅ Build metadata suffix | | `release-material_ui-0.0.3-dev.1+2` | **Match** | ✅ Pre-release & build metadata | | `release-material_ui-invalid-branch` | **No Match** | ❌ Rejected | ## Pre-Review Checklist **Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). 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. [^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
Contributor
|
Closing to retry after fix in #12419 landed |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was created automatically to batch release the
cupertino_ui.