Skip to content

Simplify and improve release steps. #1013

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
polina-c merged 3 commits into from
Jul 28, 2026
Merged

Simplify and improve release steps. #1013

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a928a50
Update release.md
polina-c Jul 28, 2026
5fe711d
Update release.md
polina-c Jul 28, 2026
c2a2a85
Update release.md
polina-c Jul 28, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 3 additions & 17 deletions docs/contributing/release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 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 <link>. 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?

Expand Down
Loading