name	release
description	Use when managing HACS releases for this integration, including version bumps, tags, beta/pre-release publishing, and release notes.

Release Workflow

Use this skill when preparing a HACS release for the SEMS integration.

Update the semantic version in custom_components/sems/manifest.json.
For beta releases from branches, use the x.x.x-beta version 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.

Run the narrowest relevant tests before releasing.
Run ruff check and ruff format --check for the touched area if code changed.
Confirm the manifest version matches the tag and release metadata.

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.

name	release
description	Use when managing HACS releases for this integration, including version bumps, tags, beta/pre-release publishing, and release notes.

Use this skill when preparing a HACS release for the SEMS integration.

Update the semantic version in custom_components/sems/manifest.json.
For beta releases from branches, use the x.x.x-beta version 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.

Run the narrowest relevant tests before releasing.
Run ruff check and ruff format --check for the touched area if code changed.
Confirm the manifest version matches the tag and release metadata.

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.