mflux release prep
Releases are prepared in-repo; tagging/publishing is handled by GitHub Actions.
When to Use
- •You’re preparing a release PR.
- •You need to bump version and update the changelog/lockfile correctly.
Instructions
- •Prefer the existing Cursor command:
- •
/release-prep
- •
- •Checklist:
- •Bump version in
pyproject.toml - •Review commits since last release tag:
- •
git log --oneline v.<last-version>..HEAD
- •
- •Browse relevant file contents if needed to clarify changes
- •Weigh commit impact: some are minor; skim earlier changelog entries to gauge what's worth reporting vs tiny fixes
- •Add a descriptive entry to
CHANGELOG.mdbased on those commits - •Update lockfile:
uv lock - •Sanity checks (optional unless requested):
make test-fast,make build - •Manual checks (optional): if the release includes CLI/callback/image-path changes, consider running the
mflux-manual-testingskill to exercise the touched commands and visually review outputs.
- •Bump version in
- •Do not tag releases locally unless explicitly requested (normally handled by CI).