RE
release
Use when managing HACS releases for this integration, including version bumps, tags, beta/pre-release publishing, and release notes.
Install
mkdir -p .claude/skills/release-timsoethout && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/15851" && unzip -o skill.zip -d .claude/skills/release-timsoethout && rm skill.zipInstalls to .claude/skills/release-timsoethout
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Use when managing HACS releases for this integration, including version bumps, tags, beta/pre-release publishing, and release notes.132 chars✓ has a “when” trigger
About this skill
Release Workflow
Use this skill when preparing a HACS release for the SEMS integration.
Steps
- Update the semantic version in custom_components/sems/manifest.json.
- For beta releases from branches, use the
x.x.x-betaversion format and mark the GitHub Release as a Pre-release. - Create a git tag for the new version:
x.x.x(-beta). - Publish a GitHub Release for that tag. Tags alone are not enough for HACS; the latest release tag is what remote version checks use.
- Write release notes that summarize the changes since the previous release, ideally based on commits since the prior tag.
Validation
- Run the narrowest relevant tests before releasing.
- Run
ruff checkandruff format --checkfor the touched area if code changed. - Confirm the manifest version matches the tag and release metadata.
Notes
- Keep release notes concise and focused on user-visible changes.
- For pre-releases, make the beta/pre-release state explicit in both the version and the GitHub Release settings.