From a928a5015007ca9e78a7b50447c6682ddda27673 Mon Sep 17 00:00:00 2001 From: Polina Cherkasova Date: Mon, 27 Jul 2026 17:32:42 -0700 Subject: [PATCH 1/3] Update release.md --- docs/contributing/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/release.md b/docs/contributing/release.md index 3405e3dce..8130480e2 100644 --- a/docs/contributing/release.md +++ b/docs/contributing/release.md @@ -92,7 +92,7 @@ TODO(polina-c): update this section after fix of https://github.com/dart-lang/ec Weekly: 1. Make sure each releasable dart package is released (TODO: [auto-create P0 bug](https://github.com/dart-lang/ecosystem/issues/423)) - 1.1. Check the `Package publishing` table in the latest merged PR to see if all non-wip versions are marked `already published`. + 1.1. Check the `Package publishing` table in the [latest merged PR](https://github.com/flutter/genui/pulls?q=is%3Apr+is%3Amerged+) to see if all non-wip versions are marked `already published`. 1.2. For packages not yet published, publish them by running `flutter pub publish` (if you do not have permissions, ask in the team chat to be made an admin on the admin page of the package). 2. Make sure publishable changes are not under `wip` in `CHANGELOG.md` (should be [auto-validated](https://github.com/dart-lang/ecosystem/issues/422) in future). From 5fe711dc83f013bf49ad2cd02c0aafc41e31679f Mon Sep 17 00:00:00 2001 From: Polina Cherkasova Date: Mon, 27 Jul 2026 17:35:02 -0700 Subject: [PATCH 2/3] Update release.md --- docs/contributing/release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/contributing/release.md b/docs/contributing/release.md index 8130480e2..11bdf1774 100644 --- a/docs/contributing/release.md +++ b/docs/contributing/release.md @@ -92,7 +92,7 @@ TODO(polina-c): update this section after fix of https://github.com/dart-lang/ec Weekly: 1. Make sure each releasable dart package is released (TODO: [auto-create P0 bug](https://github.com/dart-lang/ecosystem/issues/423)) - 1.1. Check the `Package publishing` table in the [latest merged PR](https://github.com/flutter/genui/pulls?q=is%3Apr+is%3Amerged+) to see if all non-wip versions are marked `already published`. + 1.1. Check the `Package publishing` table in the [latest merged PR that touches releasable code](https://github.com/flutter/genui/pulls?q=is%3Apr+is%3Amerged+%22Package+publishing%22) to see if all non-wip versions are marked `already published`. 1.2. For packages not yet published, publish them by running `flutter pub publish` (if you do not have permissions, ask in the team chat to be made an admin on the admin page of the package). 2. Make sure publishable changes are not under `wip` in `CHANGELOG.md` (should be [auto-validated](https://github.com/dart-lang/ecosystem/issues/422) in future). From c2a2a854a3e402a2c4d7343af59cb0f6e89a3767 Mon Sep 17 00:00:00 2001 From: Polina Cherkasova Date: Mon, 27 Jul 2026 17:41:40 -0700 Subject: [PATCH 3/3] Update release.md --- docs/contributing/release.md | 20 +++----------------- 1 file changed, 3 insertions(+), 17 deletions(-) diff --git a/docs/contributing/release.md b/docs/contributing/release.md index 11bdf1774..3e4e7b75e 100644 --- a/docs/contributing/release.md +++ b/docs/contributing/release.md @@ -91,23 +91,9 @@ TODO(polina-c): update this section after fix of https://github.com/dart-lang/ec Weekly: -1. Make sure each releasable dart package is released (TODO: [auto-create P0 bug](https://github.com/dart-lang/ecosystem/issues/423)) - 1.1. Check the `Package publishing` table in the [latest merged PR that touches releasable code](https://github.com/flutter/genui/pulls?q=is%3Apr+is%3Amerged+%22Package+publishing%22) to see if all non-wip versions are marked `already published`. - 1.2. For packages not yet published, publish them by running `flutter pub publish` (if you do not have permissions, ask in the team chat to be made an admin on the admin page of the package). - -2. Make sure publishable changes are not under `wip` in `CHANGELOG.md` (should be [auto-validated](https://github.com/dart-lang/ecosystem/issues/422) in future). - - If publishable changes are under `wip` in `CHANGELOG.md`: - - 2.1. Convert the wip version to a non-wip version in `CHANGELOG.md`. - - 2.2. Publish the new version. - - 2.3. Comment on the PR that merged publishable changes under `wip`: - - > This PR wrongly placed publishable changes under a `wip` version. This is corrected in PR . See guidelines [here](https://github.com/flutter/genui/blob/main/docs/contributing/publishing.md#-wip-vs-non--wip-production-ready-versions). - - 2.4. Make sure the PR author and reviewers acknowledged the comment. +Make sure each releasable dart package is released (TODO: [auto-create P0 bug](https://github.com/dart-lang/ecosystem/issues/423)) + 1. Check the `Package publishing` table in the [latest merged PR that touches releasable code](https://github.com/flutter/genui/pulls?q=is%3Apr+is%3Amerged+%22Package+publishing%22) to see if all non-wip versions are marked `already published`. + 2. For packages not yet published, publish them by running `flutter pub publish` (if you do not have permissions, ask in the team chat to be made an admin on the admin page of the package). ## How upgrade of dependencies happens?