[cupertino_ui] Publish pre-release 0.0.2 by justinmc · Pull Request #12251 · flutter/packages

justinmc · 2026-07-20T17:58:26Z

This PR attempts to enable the batch release process for cupertino_ui.

gemini-code-assist

Code Review

This pull request removes the publish_to: none restriction from the pubspec.yaml files of both cupertino_ui and material_ui packages to prepare them for publication. The review feedback notes that publishing will fail due to unresolved path dependencies between the two packages, which must be addressed before publishing to pub.dev.

gemini-code-assist · 2026-07-20T17:59:13Z

 name: material_ui
 description: The official Flutter Material UI Library, implementing Google's Material Design design system.
 version: 0.0.2
-publish_to: none


Attempting to publish material_ui will fail because it contains a path dependency on cupertino_ui under dependencies (line 18 of pubspec.yaml). Packages published to pub.dev cannot have path dependencies in their dependencies section. You must first publish cupertino_ui to pub.dev, and then update material_ui to use that hosted version before removing publish_to: none.

This is true! I plan to do this in another PR after cupertino_ui is published.

gemini-code-assist · 2026-07-20T17:59:14Z

 name: cupertino_ui
 description: The official Flutter Cupertino Design Library, implementing the iOS design system.
 version: 0.0.2
-publish_to: none


Attempting to publish cupertino_ui will fail because it contains a path dependency on material_ui under dev_dependencies (line 32 of pubspec.yaml). Packages published to pub.dev cannot have path dependencies in their dev_dependencies section. Since material_ui also depends on cupertino_ui, this creates a circular dependency. You will need to temporarily remove or resolve this path dependency to publish cupertino_ui first.

Hrm. Is this true?

I'm hoping this is not true and I can fix it after publishing.

Piinks

LGTM

stuartmorgan-g · 2026-07-20T18:08:26Z

Is there a reason this is being pre-landed, rather than as part of the PR that actually does the publishing?

This will mean that if we try to land any batch change that touches these packages, it'll cause publishing issues.

justinmc · 2026-07-20T18:47:22Z

Talked offline, I'm going to try to modify this PR to do the release via the automated batch release process if possible.

stuartmorgan-g

LGTM other than the current version (with the caveat that I've not actually used the batch release mechanism myself).

stuartmorgan-g · 2026-07-20T19:15:31Z

@@ -1,7 +1,6 @@
 name: cupertino_ui
 description: The official Flutter Cupertino Design Library, implementing the iOS design system.
 version: 0.0.2


I believe you need to make this 0.01 since that's the currently published version.

Ah I was just seeing this error in CI and I thought I had to add 0.0.2 to the changelog, but you must be right, the correct thing to do is to make this 0.0.1.

Probably due to enabling the batch release process now, shouldn't happen in future PRs if I understand correctly. Because at this point I would not know that this PR will necessarily be 0.0.2 (another PR could land first and claim that version).

bumped!

CI isn't happy about me making manual changes there. Let's revert them and let the batch release process bump the package to 0.0.3 instead. Pub never got version 0.0.2 but I think that's ok.

justinmc · 2026-07-20T19:53:26Z

Waiting on #12252

cupertino_ui has had publishing turned off, but we're going to turn on the batch release process soon. This PR adjusts the pubspec version and Changelog to match what's on Pub, so that the batch release process can take over from there. The version was originally bumped manually in #11649. PR #12251 will come after this one and will enable the batch release process.

Piinks · 2026-07-20T23:00:51Z

+  workflow_dispatch:
+  schedule:
+    # Run every Monday at 8:00 AM. Update cron as needed.
+    - cron: "0 8 * * 1"


I think this means this won't go out until next Monday?

Any way to manually trigger it?

Yes: https://github.com/flutter/packages/actions/workflows/cupertino_ui_batch.yml

I'll try it after postsubmits pass.

Remove publish_to none now that we are going to publish

1425ed0

justinmc requested a review from Piinks July 20, 2026 17:58

flutter-dashboard Bot added the CICD Run CI/CD label Jul 20, 2026

justinmc self-assigned this Jul 20, 2026

github-actions Bot added triage-framework Should be looked at in framework triage p: cupertino_ui p: material_ui labels Jul 20, 2026

gemini-code-assist Bot reviewed Jul 20, 2026

View reviewed changes

Piinks approved these changes Jul 20, 2026

View reviewed changes

Well I'll have to do this for material after publishing cupertino

26aabe1

github-actions Bot removed the p: material_ui label Jul 20, 2026

justinmc changed the title ~~[material_ui, cupertino_ui] Remove publish_to none now that we are going to publish~~ [cupertino_ui] Publish pre-release 0.0.2 Jul 20, 2026

justinmc requested review from chunhtai and stuartmorgan-g July 20, 2026 19:02

justinmc force-pushed the publish_to branch from 777b201 to f02c066 Compare July 20, 2026 19:03

Attempt at setting up batch release

cad31b6

justinmc force-pushed the publish_to branch from f02c066 to cad31b6 Compare July 20, 2026 19:04

stuartmorgan-g approved these changes Jul 20, 2026

View reviewed changes

justinmc added 4 commits July 20, 2026 12:18

Actually no, I think the version in the pubspec shouldn't have been

c58cc64

bumped!

Instructions are wrong: pending_changelogs not pending_changes!

39f9534

Revert changes to changelog and pubspec version.

5be51c0

CI isn't happy about me making manual changes there. Let's revert them and let the batch release process bump the package to 0.0.3 instead. Pub never got version 0.0.2 but I think that's ok.

justinmc mentioned this pull request Jul 20, 2026

[cupertino_ui] Undo unpublished version info #12252

Merged

justinmc added 2 commits July 20, 2026 13:46

Merge branch 'main' into publish_to

f6468c3

CI says i need this

3cda54c

justinmc added the autosubmit Merge PR when tree becomes green via auto submit App label Jul 20, 2026

auto-submit Bot merged commit 8260a1e into main Jul 20, 2026
13 checks passed

auto-submit Bot deleted the publish_to branch July 20, 2026 22:45

Piinks reviewed Jul 20, 2026

View reviewed changes

Uh oh!

Conversation

justinmc commented Jul 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

gemini-code-assist Bot Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

gemini-code-assist Bot Jul 20, 2026

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Piinks left a comment

Choose a reason for hiding this comment

Uh oh!

stuartmorgan-g commented Jul 20, 2026

Uh oh!

justinmc commented Jul 20, 2026

Uh oh!

stuartmorgan-g left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

justinmc commented Jul 20, 2026

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

justinmc commented Jul 20, 2026 •

edited

Loading