You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Prepare a new 0.82.1 release: bump packages/flet version and refresh client pubspec.lock, add 0.82.1 entries to root and packages/flet CHANGELOGs, and update sdk/python/packages/flet-ads CHANGELOG (Unreleased -> 0.82.1; section renamed). Also update the release preparation skill doc to require creating a prepare-release branch, use GitHub profile links for author attribution in changelogs, and ensure inferred PRs/issues have the {version} milestone.
Copy file name to clipboardExpand all lines: .codex/skills/prepare-flet-release/SKILL.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,22 +13,24 @@ description: Use when asked to prepare new Flet release by bumping versions and
13
13
* Take latest Flet release version from the repo and
14
14
increment third (patch) digit to get the next version if it's a minor release
15
15
or second (minor) digit if it's a major release.
16
+
* Pull the latest `main` and create a new branch named `prepare-release-{new_version}` from `main`.
16
17
* Set new version in packages/flet/pubspec.yaml.
17
18
* Run pub get in /client dir to refresh pubspec.lock with new version.
18
19
* Add a new entry into packages/flet/CHANGELOG.md from a git log since the last release. Go through all commits and collect all mentioned issues and pull requests. There could be several issues done in a single PR (commit) - group them by creating a single descriptive change/fix/feature item and put all issues and PR links in `[#<issue_number>](<issue_url>)` format in braces next to it. Do not add chore/trivial/duplicate items.
19
20
Every changelog item must include both related issue link(s) and PR link(s) when available (issue first, PR second). If no issue exists, include PR link(s) only.
20
21
Also include issue-only items when a change was done via direct commit without PR (for example, an issue referenced in commit context but no PR exists).
21
-
Every changelog item must include author attribution in GitHub style: `by @<github_login>`.
22
+
Every changelog item must include author attribution as a GitHub profile link: `by [@<github_login>](https://github.com/<github_login>)`.
22
23
Place attribution at the end of each item after links, for example:
23
-
`* Added feature X ([#123](...), [#456](...)) by @contributor.`
24
+
`* Added feature X ([#123](...), [#456](...)) by [@contributor](https://github.com/contributor).`
24
25
Use PR author login for PR-based items. For issue-only direct-commit items, use the commit author GitHub login if available.
25
26
If one item groups multiple PRs by different authors, attribute all relevant authors:
Ensure that all infered PRs and issues in the changelog have `{version}` milestone attached on GitHub.
27
29
As it's a Flutter package prefer items having changes on Flutter side.
28
30
* Add a new entry into /CHANGELOG.md. Do not add chore/trivial/duplicate items, add "worth while" items with related issue or PR.
29
31
Every changelog item must include both related issue link(s) and PR link(s) when available (issue first, PR second). If no issue exists, include PR link(s) only.
30
32
Also include issue-only items when a change was done via direct commit without PR (for example, an issue referenced in commit context but no PR exists).
31
-
Every changelog item must include author attribution in GitHub style: `by @<github_login>`.
33
+
Every changelog item must include author attribution as a GitHub profile link: `by [@<github_login>](https://github.com/<github_login>)`.
32
34
Use PR author login for PR-based items. For issue-only direct-commit items, use the commit author GitHub login if available.
33
35
* Scan all changelogs for `Unreleased` sections, not only the root ones:
0 commit comments