Repository navigation
Support first stable Home Assistant releases after prereleases - #1061
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repositories with only prereleases have no GitHub latest stable release. Preparing their first stable Home Assistant or HACS release consequently selects the synchronized metadata version again and fails when that tag is already occupied.
Use the highest published three-part release version as the baseline when GitHub's latest-release endpoint returns 404. Preserve the existing stable baseline, normal increment policy, historical prerelease tags and assets, target-tag preflight, and prepared-commit recovery checks. Drafts and unsupported tags are excluded, and an incomplete paginated search fails closed.
This was reproduced while releasing Waste Pickup Planner after its visual bin controls change: metadata
0.1.5with only thev0.1.5prerelease now plans a new stablev0.1.6. PowerForge owns version selection; the consumer retains its thin release receiver. The hosted workflow route requires a published PowerForge.Build containing this fix and corresponding immutable workflow pins.Validation: 43 focused Home Assistant release/client tests passed, an independent read-only contract review found no actionable defects, and a read-only plan against the merged consumer confirmed
v0.1.6.