Automate HotPlex releases with version bumps, changelogs, and unified component versions.
npx skills add https://github.com/hrygo/hotplex --skill hotplex-release
Please help me install this Agent Skill. Skill: hotplex-release Source: https://github.com/hrygo/hotplex/tree/main/.agents/skills/hotplex-release Command: npx skills add https://github.com/hrygo/hotplex --skill hotplex-release
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.
main.CHANGELOG.md following Keep a Changelog with a clear, user-facing Summary.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.
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.
High-intent search queries and answers about installing and using this skill.
To unify component versions for a release, you update Go gateway references, WebChat UI, SDK examples, and Dockerfile labels, then validate that all components report the same semantic version before publishing to ensure cross-repository consistency.
You can prepare release artifacts on a feature branch, but strict branch guardrails enforce that creating Git tags and publishing GitHub Releases must only occur on the main branch to maintain deterministic CI builds and release correctness.
After publishing a release, you trigger CI builds by pushing the annotated tag, replace auto-generated GitHub release notes with the full extracted changelog content, and verify post-release artifacts to ensure deterministic workflow correctness across all unified components.
The best way to ensure CI-triggered artifact verification is to push an annotated Git tag to trigger CI builds, replace auto-generated release notes with extracted changelog content, and validate post-release artifact correctness across all project components.
Yes, the release workflow supports preparing version bumps and changelogs on feature branches, while enforcing strict guardrails so that actual tag creation, GitHub release publishing, and CI artifact verification only happen on the main branch.
thebrokencubeEnforce conventional commit message formatting with type, scope, and description.
CyanAutomationAutomate tag-triggered Docker image and GitHub release publication.
nccasiaCreate GitHub Actions workflows for CI/CD testing, Docker builds, Kubernetes deployment, and security scanning.
Iron-HamPreview version bumps, changelog updates, and release notes without modifying the repository.