| name | prepare-flet-release |
| description | Use when asked to prepare new Flet release by bumping versions and author release notes. |
Inputs
- Previous Flet version from repo tags.
- Whether it's minor or major release.
Related Skills
Always use flet-deprecation during release prep
to audit deprecations for the target version. Also use it when release prep includes:
- adding new deprecations in this release,
- removing APIs whose
delete_version equals this release version,
- auditing changelog entries that mention deprecations/removals.
Use write-changelog-entry for drafting or refining individual changelog items.
That skill is the source of truth for item wording, scope selection, and what should or should not be mentioned in a single entry.
Steps
- Take latest Flet release version from the repo and
increment third (patch) digit to get the next version if it's a minor release
or second (minor) digit if it's a major release.
- Pull the latest
main and create a new branch named prepare-release-{new_version} from main.
- Set new version in packages/flet/pubspec.yaml.
- Run pub get in /client dir to refresh pubspec.lock with new version.
- Add new entries into
packages/flet/CHANGELOG.md and /CHANGELOG.md from the git log since the last release.
- Use
write-changelog-entry for every individual item.
- Build the candidate set from relevant commits, PRs, and issues since the last release.