timsoethout/goodwe-sems-home-assistant/release

HACS Release

1. Version: Update custom_components/sems/manifest.json. Base the next stable version on the latest stable release: patch for fixes, minor for features, major for breaking changes. Use numbered prereleases (for example, 11.12.0-beta.1) for the intended stable version; breaking beta changes target the next major. Never reuse a published tag.
2. Release notes: Update RELEASE_NOTES.md with all user-visible changes since the previous stable tag, including every beta. Keep notes concise; preserve existing links, add verified links when available, and never invent them. Include limitations and compatibility notes.
3. Contributors: Credit code authors and people who contributed information, testing, or troubleshooting. Verify GitHub handles; do not infer them from email addresses.
4. Publish:

• Stable: Prepare the manifest and stable notes in a PR to master. Merging it triggers .github/workflows/stable-release.yml, which extracts the matching stable notes and creates the GitHub Release. It uses .github/scripts/upload_release_asset.py to attach custom_components/sems/sems.zip. Do not manually tag or publish a stable release. After merge, verify the workflow completed and the ZIP is attached. The workflow skips prerelease versions and avoids re-creating existing releases.
• Prerelease: Continue to create and publish beta releases manually, mark them as prereleases, and use the matching beta notes. Publishing triggers .github/workflows/release-assets.yml to upload the ZIP; a tag alone is insufficient.

For a stable release after betas, use the same version number and preserve the full beta history in its notes. HACS users must opt into prereleases to receive betas.

Before finishing

• Run the narrowest relevant tests; if code changed, run ruff check and ruff format --check on the touched area.
• Before merging a stable release-preparation PR, confirm the manifest version matches exactly one stable release-notes section and that the tag is unused; do not publish manually.
• After merge, confirm the stable GitHub Release tag matches the manifest, it is not a prerelease, and sems.zip is attached.
• For a manually published prerelease, confirm the tag matches the manifest, the prerelease flag is set, and sems.zip is attached.