Skip to content

Offer releases after commit-based installations - #5562

Open
SeoFood wants to merge 1 commit into
hacs:mainfrom
SeoFood:seofood/hacs-commit-to-release-update
Open

SeoFood wants to merge 1 commit into
hacs:mainfrom
SeoFood:seofood/hacs-commit-to-release-update

Conversation

@SeoFood

@SeoFood SeoFood commented Sep 30, 2026

Copy link
Copy Markdown

When a repository publishes its first release, an existing commit-based installation can stop receiving update notifications if its abbreviated SHA parses as a version. For example, 3730b11 is considered newer than 0.2.0, so pending_update returns False.

Only compare release versions when installed_version is set. Commit-based installations fall through to the existing comparison instead. Tests cover both parseable and non-parseable SHAs, older/equal/newer release versions, and an explicitly selected default branch.

Fixes #5504.

Validation: all 435 tests pass with Home Assistant 2025.3.0 and Python 3.13.12, matching the minimum-version CI job. The two parseable-SHA regression cases fail before the fix. Pre-commit checks pass for all changed files.

@SeoFood

SeoFood commented Sep 30, 2026

Copy link
Copy Markdown
Author

@codex review

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Commit-installed repositories are permanently never offered an update once the repo publishes its first release

1 participant