mflux-release

Prepare a release in mflux (version bump, changelog, uv lock) without tagging/publishing.

⭐1.7kstars🔀109forks📁View on GitHub🕐Updated Jan 10, 2026

When & Why to Use This Skill

The mflux-release skill automates the essential steps of the software release preparation process. It streamlines version management, changelog generation, and dependency locking, ensuring that repositories are perfectly staged for deployment without the risk of manual errors in configuration files.

Use Cases

  • Automated Version Bumping: Quickly update version strings in pyproject.toml and other configuration files to maintain consistent release numbering.
  • Changelog Documentation: Automatically analyze git commit history since the last release to generate descriptive and organized entries for CHANGELOG.md.
  • Dependency Synchronization: Execute lockfile updates (such as uv lock) to ensure environment consistency before a release pull request is finalized.
  • Pre-release Workflow Optimization: Standardize the checklist for release preparation, including optional sanity checks and build tests to verify code stability.
namemflux-release
descriptionPrepare a release in mflux (version bump, changelog, uv lock) without tagging/publishing.

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.md based 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-testing skill to exercise the touched commands and visually review outputs.
  • Do not tag releases locally unless explicitly requested (normally handled by CI).