hotplex-release

What problem does it solve?

HotPlex release preparation and publishing involves many error-prone, repetitive steps (version bump, changelog quality, tag/release creation, and cross-component version consistency), and this Skill ensures a consistent, auditable workflow on both main and feature branches.

Core Features & Use Cases

• Version determination & guardrails: Reads the current HotPlex version, computes the next semver (patch/minor/major), and enforces the rule that tags and GitHub Releases must only be created on main.
• Change collection & categorized Changelog: Collects commits since the last release tag, groups changes into user-relevant sections, and writes CHANGELOG.md following Keep a Changelog with a clear, user-facing Summary.
• Version unification across the whole project: Updates Go gateway version references, WebChat UI version, SDK example versions, Dockerfile labels, and validates that versions match before publishing.
• Release orchestration: On main, creates an annotated tag, pushes to trigger CI builds, replaces auto-generated release notes with the full extracted changelog content, and verifies artifacts and post-release correctness.

Example use case: you need to publish v1.2.1 with a patch release, ensuring the changelog Summary and categorized Added/Changed/Fixed sections are correct and that every component (gateway, UI, SDK examples, Docker label) reports the same version.

Quick Start

Ask the assistant to prepare a HotPlex patch release to v1.2.1 on your current branch, ensuring it updates CHANGELOG and unifies versions, and if you are on main then it should proceed to tag, publish, and verify artifacts.