Update ci for + releases

[Piinks]

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:

• [material_ui] Batch release #12412
• [cupertino_ui] Batch release #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

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. 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.

Footnotes

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. ↩ ↩²

[gemini-code-assist]

Code Review

This pull request updates the regular expressions for enabled release branches in .ci.yaml to support optional pre-release and build metadata suffixes. The review feedback points out that the regex character class [\w.] should be updated to [\w.-] to correctly support hyphens, which are valid in SemVer 2.0.0.

[gemini-code-assist]

The regular expression [\w.] matches alphanumeric characters, underscores, and dots, but it does not match hyphens (-). According to the SemVer 2.0.0 specification, both pre-release identifiers and build metadata can contain hyphens (e.g., 1.0.0-alpha-1 or 1.0.0+build-123).\n\nTo fully support valid SemVer release branch names, the character class should be updated to include hyphens, i.e., [\w.-]. Note that the hyphen should be placed at the end of the character class to avoid being interpreted as a range.

  - release-go_router-\d+\.\d+\.\d+(?:-[\w.-]+)?(?:\+[\w.-]+)?\n  - release-cupertino_ui-\d+\.\d+\.\d+(?:-[\w.-]+)?(?:\+[\w.-]+)?\n  - release-material_ui-\d+\.\d+\.\d+(?:-[\w.-]+)?(?:\+[\w.-]+)?

[stuartmorgan-g]

LGTM.

In practice the only thing we ever actually use in this repo is +[\d]+, but there's not much risk of false positives here given the prefixes

[justinmc]

LGTM 👍

[auto-submit]

autosubmit label was removed for flutter/packages/12419, because - The status or check suite Dashboard Checks has failed. Please fix the issues identified (or deflake) before re-applying this label.