Release automation.

.github/dependabot.yaml

@@ -12,7 +12,8 @@ updates:
     labels:
       - "autosubmit"
   - package-ecosystem: "pub"
-    directory: "/"
+    directories:
+      - "/**"
     schedule:
       interval: "daily"
     labels:

.github/workflows/post_summaries.yaml

@@ -0,0 +1,22 @@
+# Copyright 2025 The Flutter Authors.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# A CI configuration for pub-publish to write comments on PRs.
+
+name: Comment on the pull request
+
+on:
+  workflow_dispatch: # This means the job is manual-only.
+  # TODO(polina): re-enable the workflow_run trigger in a follow-up PRs.
+  # workflow_run:
+  #   workflows: 
+  #     - Publish
+  #   types:
+  #     - completed
+
+jobs:
+  upload:
+    uses: dart-lang/ecosystem/.github/workflows/post_summaries.yaml@main
+    permissions:
+      pull-requests: write

.github/workflows/publish.yaml

@@ -0,0 +1,31 @@
+# Copyright 2025 The Flutter Authors.
+# Use of this source code is governed by a BSD-style license that can be
+# found in the LICENSE file.
+
+# A CI configuration to auto-publish pub packages.
+
+name: Publish
+
+on:
+  workflow_dispatch: # This means the job is manual-only.
+  # TODO(polina): re-enable the pull_request trigger in a follow-up PRs.
+  # pull_request:
+  #   branches: [ main ]
+  #   types: [opened, synchronize, reopened, labeled, unlabeled]
+  # push:
+  #   # Match <package-name>-v<version> publish tags
+  #   tags: [ '[A-z0-9]+-v[0-9]+.[0-9]+.[0-9]+' ]
+
+jobs:
+  publish:
+    if: ${{ github.repository_owner == 'flutter' }}
+    uses: dart-lang/ecosystem/.github/workflows/publish.yaml@main
+    with:
+      # See https://github.com/dart-lang/ecosystem/tree/main/pkgs/firehose#options
+      sdk: beta # version of dart sdk to use for publishing
+      use-flutter: true
+      write-comments: false
+      checkout_submodules: false
+    permissions:
+      id-token: write
+      pull-requests: write

CONTRIBUTING.md

@@ -1,25 +1,10 @@
-# Contributing to GenUI for Flutter
+# Contributing to this repository
 
-## Guidelines
+## Coding guidelines
 
-Please follow [Flutter contributor guidelines][flutter_guidelines].
-
-## Run Examples
-
-To run examples:
-
-1. Configure Firebase as described in [README.md][readme_md].
-2. Run `flutter run`.
-
-NOTE: For Google-internal projects see go/flutter-genui-internal.
-
-## Shell scripts
-
-To run a script in `tool/`, open the script in VSCode and press ⇧⌘B.
-
-## Detailed documentation for contributors
-
-See [docs/contributing.md](docs/contributing.md).
+Please follow:
+  * [Flutter-wide contributor guidelines][flutter_guidelines].
+  * [A2UI-specific guidelines](docs/contributing/README.md).
 
 ## Issue triage
 
@@ -57,7 +42,7 @@ of the front-line triage include:
 
 ### Periodic second-line triage
 
-### Bi-weekly during the planning meeting
+#### Bi-weekly during the planning meeting
 
 Check that existing issues are labeled and organized appropriately:
 
@@ -66,7 +51,7 @@ Check that existing issues are labeled and organized appropriately:
 * Set a milestone to all [P0 and P1 issues][p0_p1_issues_without_milestone].
 * Add all [projectless open issues][projectless_open_issues] to the "genui" project.
 
-### Weekly during the planning meeting
+#### Weekly during the planning meeting
 
 Triage issues ready for second-line review:
 
@@ -82,40 +67,15 @@ Triage issues ready for second-line review:
 At the end of a triage session, the untriaged issue list should be as close to
 empty as possible.
 
-## Versioning
-
-We use [Semver] for package versioning, although before 1.0.0, we will be
-incrementing only the minor number for breaking changes and the patch number for
-non-breaking changes. After 1.0.0, we will be using standard Semver, bumping the
-major number for breaking changes.
-
-We release the following packages in lock step,
-with the same version number, so when one is released, they are all released:
-
-* `genui`
-* `genui_a2a`
-* `genui_firebase_ai`
-* `genui_google_generative_ui`
-
-These packages are released independently on their own schedule, with their
-own version number:
+## Internal information
 
-* `genai_primitives`
-* `json_schema_builder`
+For Google-internal information see go/a2ui-internal.
 
-"Releasing" consititutes manually publishing them all to [pub.dev] after the
-pull request containing the version bump has passed CI. The packages must be
-published by someone with permission to publish under the labs.flutter.org
-owner.
 
-Use the [release tool](tool/release/README.md) to help automate the process of
-releasing a new version.
+<!-- references -->
 
-[pub.dev]: https://pub.dev
-[Semver]: https://semver.org/
 [for-front-line]: https://github.com/flutter/genui/issues?q=is%3Aissue%20state%3Aopen%20-label%3AP0%20%20-label%3AP1%20-label%3AP2%20%20-label%3AP3%20-label%3Afront-line-handled
 [flutter_guidelines]: https://github.com/flutter/flutter/blob/master/CONTRIBUTING.md
-[readme_md]: packages/genui/README.md#configure-firebase-ai-logic
 [assigned_p2_p3_issues]: https://github.com/flutter/genui/issues?q=is%3Aopen%20is%3Aissue%20label%3AP2%2CP3%20assignee%3A*
 [p0_p1_issues_without_milestone]: https://github.com/flutter/genui/issues?q=is%3Aopen%20is%3Aissue%20label%3AP1%2CP0%20no%3Amilestone
 [projectless_open_issues]: https://github.com/flutter/genui/issues?q=is%3Aopen%20is%3Aissue%20no%3Aproject
@@ -124,14 +84,3 @@ releasing a new version.
 [P1]: https://github.com/flutter/genui/labels?q=P1
 [P2]: https://github.com/flutter/genui/labels?q=P2
 [P3]: https://github.com/flutter/genui/labels?q=P3
-
-## pubspec.lock files
-
-`pubspec.lock` files are not git ignored to make the bots faster.
-
-If you include `pubspec.lock` file to your PR, make sure to run `flutter pub upgrade`,
-when your Flutter is latest at beta channel.
-
-## Internal information
-
-For Google-internal information see go/a2ui-internal.

dev_tools/catalog_gallery/linux/flutter/generated_plugins.cmake

@@ -8,7 +8,6 @@ list(APPEND FLUTTER_PLUGIN_LIST
 )
 
 list(APPEND FLUTTER_FFI_PLUGIN_LIST
-  jni
 )
 
 set(PLUGIN_BUNDLED_LIBRARIES)

dev_tools/catalog_gallery/macos/Flutter/GeneratedPluginRegistrant.swift

@@ -12,5 +12,5 @@ import video_player_avfoundation
 func RegisterGeneratedPlugins(registry: FlutterPluginRegistry) {
   AudioplayersDarwinPlugin.register(with: registry.registrar(forPlugin: "AudioplayersDarwinPlugin"))
   UrlLauncherPlugin.register(with: registry.registrar(forPlugin: "UrlLauncherPlugin"))
-  VideoPlayerPlugin.register(with: registry.registrar(forPlugin: "VideoPlayerPlugin"))
+  FVPVideoPlayerPlugin.register(with: registry.registrar(forPlugin: "FVPVideoPlayerPlugin"))
 }

dev_tools/composer/linux/flutter/generated_plugins.cmake

@@ -10,7 +10,6 @@ list(APPEND FLUTTER_PLUGIN_LIST
 )
 
 list(APPEND FLUTTER_FFI_PLUGIN_LIST
-  jni
 )
 
 set(PLUGIN_BUNDLED_LIBRARIES)

dev_tools/composer/macos/Flutter/GeneratedPluginRegistrant.swift

@@ -15,6 +15,6 @@ func RegisterGeneratedPlugins(registry: FlutterPluginRegistry) {
   AudioplayersDarwinPlugin.register(with: registry.registrar(forPlugin: "AudioplayersDarwinPlugin"))
   ScreenRetrieverMacosPlugin.register(with: registry.registrar(forPlugin: "ScreenRetrieverMacosPlugin"))
   UrlLauncherPlugin.register(with: registry.registrar(forPlugin: "UrlLauncherPlugin"))
-  VideoPlayerPlugin.register(with: registry.registrar(forPlugin: "VideoPlayerPlugin"))
+  FVPVideoPlayerPlugin.register(with: registry.registrar(forPlugin: "FVPVideoPlayerPlugin"))
   WindowManagerPlugin.register(with: registry.registrar(forPlugin: "WindowManagerPlugin"))
 }

dev_tools/composer/pubspec.yaml

@@ -4,7 +4,6 @@
 
 name: composer
 publish_to: "none"
-version: 0.1.0
 
 environment:
   sdk: ">=3.10.0 <4.0.0"

dev_tools/composer/windows/flutter/generated_plugins.cmake

@@ -11,7 +11,6 @@ list(APPEND FLUTTER_PLUGIN_LIST
 )
 
 list(APPEND FLUTTER_FFI_PLUGIN_LIST
-  jni
 )
 
 set(PLUGIN_BUNDLED_LIBRARIES)

docs/contributing/README.md

@@ -1,13 +1,17 @@
-# GenUI specifications
+# Contributing to this repository
 
 This folder provides guidance for contributors,
 targeted at both AI models and human developers.
 
-## Index of Specifications
+## Index of specifications
 
 This directory contains the following specifications:
 
-- [Style Guide](styleguide.md)
+- [Style guide](styleguide.md)
+- [Design](design.md)
+- [Pull requests](pull_requests.md)
+- [Publishing](publishing.md)
+- [Examples](../../examples/README.md)
 
 ## Note for AI models
 
@@ -23,15 +27,22 @@ I have read and understood ./docs/contributing/README.md.
 1. Documentation in the repository (all .md files) should be clear, consistent, concise and up-to-date.
 2. Documentation should not contain details that are easy to infer from the code.
 3. If code does not match the documentation, there should be TODO comments in the code to signal the discrepancy should be resolved.
+4. For documentation use [sentence case for headings](https://developers.google.com/style/capitalization#capitalization-in-titles-and-headings).
 
-## Code reviews
+## Shell scripts
 
-Do not review pull requests when they are in draft state, unless explicitly requested by the author.
+To run a script in `tool/`:
 
-## Key commands
+- If you are on mac and use VS Code, open the script and press `⇧⌘B` (see [.vscode/tasks.json](../../.vscode/tasks.json)).
+- Otherwise, you can invoke the scripts on the command line from any directory.
 
-- **Run all checks and tests:**
+## pubspec.lock files
 
-  ```bash
-  ./tool/run_all_tests_and_fixes.sh
-  ```
+`pubspec.lock` files are not git ignored to make the bots faster.
+
+If you include `pubspec.lock` file to your PR, make sure to run `flutter pub upgrade`,
+when your Flutter is using the latest version of the beta channel (run `flutter channel beta && flutter upgrade` to make sure you're on the right one).
+
+<!-- references -->
+
+[Semver]: https://semver.org/

docs/contributing/publishing.md

@@ -0,0 +1,85 @@
+
+# Publishing 
+
+Publishing to [pub.dev](https://pub.dev) happens automatically via GitHub Actions, with the help of
+[firehose rules](https://github.com/dart-lang/ecosystem/tree/main/pkgs/firehose).
+
+There are two CI workflows that enable this automation:
+
+1. [post_summaries.yaml](../../.github/workflows/post_summaries.yaml) - job `publish / validate` runs on pre-submit.
+2. [publish.yaml](../../.github/workflows/publish.yaml) - job `publish / publish` runs on tagging.
+
+## Passing the publish / validate job
+
+In general, the job [publish / validate](https://github.com/flutter/genui/actions/workflows/post_summaries.yaml) checks if all pub.dev packages are ready for publishing.
+
+To make sure your PR passes this validation, follow [firehose rules](https://github.com/dart-lang/ecosystem/tree/main/pkgs/firehose).
+
+## Package categories
+
+Packages in this repo fall into the following categories:
+
+1. **Not published**: `pubspec.yaml` contains `publish_to: none`. Workspace tools and example apps that are never pushed to pub.dev.
+2. **Not yet published**: the package's `version:` ends with a `-dev<N>` suffix (see "`-dev` vs non-`-dev`" below). Published to pub.dev to reserve the name or to test the package; not ready for general use yet.
+3. **Published**: any other package. Each has its own version cadence on pub.dev.
+
+## About `resolution: workspace`
+
+`resolution: workspace` in a `pubspec.yaml`:
+
+1. Tells Dart to share dependency resolution and a lockfile with the monorepo.
+
+2. Tells to use current repo as a source for the package, not pub.dev (for local runs).
+
+Note that a package can opt out (by omitting `resolution: workspace`) to have separate dependency resolution.
+
+## `-dev` vs non-`-dev` (production ready) versions
+
+The packages code should be always release ready. That means:
+
+1. Use `-dev` version (format `0.1.0-dev002`) if **at least one** of the following statements is true:
+
+   1.1. The package is planned to be released in the future. In this case it is published with `-dev` suffix in order to reserve the package name.
+
+   1.2. The package's changes touch only non-publishable code or docs (like tests, tools, or not-publishable docs).
+
+   You can publish `-dev<number>` versions (where `<number>` is a three-digit, zero padded integer like `-dev003`), if you need it for development. 
+
+2. If your feature is partially implemented, hide the feature's code behind a false-by-default flag, and use **release-ready** version. (There is no detailed guidance how to define this flag yet. It should be outlined when it is needed. Please create an issue if you need it soon.)
+
+## Versioning
+
+We use [Semver] for package versioning, although before 1.0.0, we will be
+incrementing only the minor number for breaking changes and the patch number for
+non-breaking changes. After 1.0.0, we will be using standard Semver, bumping the
+major number for breaking changes.
+
+<!-- references -->
+
+[Semver]: https://semver.org/ 
+
+## How publishing happens?
+
+TODO(polina-c): add information, https://github.com/google/A2UI/issues/1383
+
+## How upgrade of dependencies (for both siblings and third party) happens?
+
+### For local development runs
+
+For packages with `resolution: workspace` in their pubspec.yaml, pub resolves every sibling from its local source directory — not from pub.dev, as long as its `version:` satisfies the consumer's constraint.
+
+If a local bump escapes that constraint (e.g. `^0.9.0` → `0.10.0`), you must update the consumer's `pubspec.yaml` in the same PR. While `dart pub` natively silently falls back to the published version on pub.dev, **our `test_and_fix` CI suite contains a verification step that will explicitly throw an error** and fail your PR if internal workspace version constraints are not met.
+
+### For runs by external packages
+
+After a new version of a dependency (including sibling package in this repo) is published, this is how upgrade will happen:
+
+1. [Dependabot] detects the new version on pub.dev and opens a PR per dependency, bumping the constraint in each consuming `pubspec.yaml`. See [About Dependabot version updates] for details.
+2. The PR runs `publish / validate` and the rest of CI.
+3. A maintainer reviews and merges the PR. 
+
+TODO: Consume solution for [dependabot issue][dependabot/dependabot-core#15057] when it is fixed.
+
+[Dependabot]: ../../.github/dependabot.yaml
+[About Dependabot version updates]: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/about-dependabot-version-updates
+[dependabot/dependabot-core#15057]: https://github.com/dependabot/dependabot-core/issues/15057

docs/contributing/pull_requests.md

@@ -0,0 +1,17 @@
+# Authoring pull requests
+
+## Make your PR easy to review
+
+1. Make sure your PR has meaningful title and description.
+2. Make sure your PR is not too large. Smaller PRs are easier to review.
+3. Separate code reorgs from feature changes.
+
+## CI presubmit errors
+
+You may get CI presubmit errors on pull requests for several reasons. This section explains how to fix some of the less obvious ones.
+
+### From `publish / validate` job
+
+In general, the job checks if all [pub.dev](https://pub.dev) packages are release ready. 
+
+See [publishing.md](publishing.md) for more details.

examples/simple_chat/linux/flutter/generated_plugins.cmake

@@ -8,7 +8,6 @@ list(APPEND FLUTTER_PLUGIN_LIST
 )
 
 list(APPEND FLUTTER_FFI_PLUGIN_LIST
-  jni
 )
 
 set(PLUGIN_BUNDLED_LIBRARIES)

examples/simple_chat/macos/Flutter/GeneratedPluginRegistrant.swift

@@ -12,5 +12,5 @@ import video_player_avfoundation
 func RegisterGeneratedPlugins(registry: FlutterPluginRegistry) {
   AudioplayersDarwinPlugin.register(with: registry.registrar(forPlugin: "AudioplayersDarwinPlugin"))
   UrlLauncherPlugin.register(with: registry.registrar(forPlugin: "UrlLauncherPlugin"))
-  VideoPlayerPlugin.register(with: registry.registrar(forPlugin: "VideoPlayerPlugin"))
+  FVPVideoPlayerPlugin.register(with: registry.registrar(forPlugin: "FVPVideoPlayerPlugin"))
 }

examples/simple_chat/pubspec.yaml

@@ -4,7 +4,6 @@
 
 name: simple_chat
 publish_to: "none"
-version: 0.1.0
 
 environment:
   sdk: ">=3.10.0 <4.0.0"