Repository navigation
chore: bump THIS_VERSION to v712.20 - #40
Merged
Merged
Conversation
main has drifted two files past the v712.19 release - the prediction kernel source and its aarch64 binary, from the round_py perf change in #39 - so check_install compares the running files against a release they no longer match and every startup logs the size mismatches followed by "Predbat files are installed but have modifications". Verified against the live pi5 install: --check v712.19 reports prediction_kernel.cpp (expected 53079, got 57697) and prediction_kernel_lib_aarch64.so (expected 243216, got 244096). Bumping makes release.yml publish v712.20 from the merge commit, so check_install fetches a listing that matches the shipped code, and Home Assistant's update.predbat_version entity has a release to install - without the bump the perf fix sits in main and never reaches any installation. manifest.yaml is not touched here on purpose: it is gitignored and regenerated at runtime from the GitHub listing whenever it is absent, so the fix is the version alone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Summary
Bumps
THIS_VERSIONso the kernel performance fix from #39 actually ships.release.ymlpublishes a release tagged fromTHIS_VERSIONon every push to main. #39 merged without a bump, so the workflow ran but found v712.19 already released — no new release was created, Home Assistant'supdate.predbat_versionentity had nothing to install, and the perf fix has been sitting in main unreachable by any installation.It also leaves
check_installcomparing running files against a release they no longer match. Verified against the live pi5 install with--check v712.19:Exactly the two files #39 touched. Bumping to v712.20 makes
release.ymlpublish from the merge commit, socheck_installfetches a listing that matches the shipped code and the warnings clear.manifest.yamlis deliberately untouched — it is gitignored and regenerated at runtime from the GitHub listing whenever absent, so the fix is the version alone.🤖 Generated with Claude Code