[evski]

Why

HACS default inclusion asks for a GitHub release created after hassfest and HACS validation have succeeded on that commit. v0.1.1 was published at 2026-11-07 11:39:18 GMT. Validate run 42369085242 on the same commit finished hassfest at 11:39:40 GMT and HACS validation at 11:39:57 GMT, so that release is too early to link from a default-repository submission.

This pull request prepares the next patch. It does not publish a release and it does not submit the repository to hacs/default.

Changes

• Bump custom_components/lite_resources/manifest.json to 0.1.2.
• Add CHANGELOG.md and a Releasing section in the README with the order: merge, wait for Validate, then create the release.
• Add tests/test_release_metadata.py for the version, changelog, workflow, brand icon, and single-package layout. python3 -m unittest discover -s tests -v passes (7 tests).

Resource filtering is unchanged.

Validation on this branch

Both runs completed successfully, with no ignore key in the workflow:

• Push to this branch: 42370103667 (hassfest 11:54:13 GMT, HACS 11:54:28 GMT)
• Pull request: 42370112652 (hassfest 11:54:21 GMT, HACS 11:54:37 GMT)

After this merges

1. Wait until the Validate workflow on the merge commit succeeds, with both hassfest and HACS green and no ignored checks.
2. Create GitHub release v0.1.2 for that commit, targeting main. The release has to be created after that run finishes.
3. Only then open the hacs/default pull request, with links to that release and to the successful runs.