Skip to content

Home Assistant AC Defender v0.1.4586 — No public code name resolved

Latest

Choose a tag to compare

@DingDingChae DingDingChae released this 17 Oct 10:42

Home Assistant AC Defender v0.1.4586

Locally built from commit 775d93068c897ab6dc9b8a444981de6c7603d4b5. Separate Docker image archives are prepared for linux/amd64 and linux/arm64. Independent published-download proof is established only by the authoritative release asset readback below.

  • ac-defender-docker-0.1.4586-amd64.tar.gz: run gunzip ac-defender-docker-0.1.4586-amd64.tar.gz, then docker load --input ac-defender-docker-0.1.4586-amd64.tar; use the exact image reference from its metadata.
  • ac-defender-docker-0.1.4586-arm64.tar.gz: run gunzip ac-defender-docker-0.1.4586-arm64.tar.gz, then docker load --input ac-defender-docker-0.1.4586-arm64.tar; use the exact image reference from its metadata.

Published service image: ghcr.io/ding-ding-projects/homeassistantacdefender@sha256:cfecd107be66f56c30fcde558a014de6f8aa6f6c388a8b1744b6015a44ee3d0a. The attached Compose manifest pins this digest. Anonymous pull verification: success. A successful anonymous pull is required before this release can be published.

Portable Windows hosting setup is attached separately from the existing Squirrel controller.

Windows Electron controller

Locally built and locally checked unsigned Squirrel.Windows Setup.exe, .nupkg update package, and RELEASES feed are prepared for the Windows controller. Background updates use HTTPS plus RELEASES/package hashes and retain an unsigned-artifact warning contract; visible controller warning copy remains an integration follow-up. Independent published-download proof is established only by release asset readback. No signing certificate is used.

Workflow timing

  • Workflow started: 2026-10-17T10:20:39Z
  • Workflow completed: 2026-10-17T10:42:00Z
  • Workflow duration (workflow-start first job through gh release create completion): 00:21:21

Release code name

No public code name resolved

No unused public photo was available at release time; the software release is not blocked by catalog availability.

CI line-count report

Reproducible line-count report

Generated by python scripts/count_lines.py at the checked-out commit.

Area Files Total lines Non-blank lines Agent-attributed lines
Configuration/other text 52 24594 24427 17894
Documentation 107 10511 8225 6534
Application source 112 34457 30617 13929
Styles/markup 209 20970 19179 11209
Tests 19 9073 8057 3143
Project total 499 99605 90505 52709
Excluded binary/non-text 119 — — —
Grand total (tracked files) 618 99605 text + binary 90505 text + binary —
  • Grand total of counted text: 99605 lines (90505 non-blank).
  • Agent attribution rule: surviving git blame lines are agent-written when the commit author identity or an explicit Co-Authored-By trailer names an automation identity (agent, automation, bot, codex, or claude).
  • Excluded: 119 tracked binary/non-text files plus build/runtime/vendor trees (.git, bin, obj, App_Data, and node_modules). Binary files are excluded because they have no portable source-line meaning.

Checks

  • Docker images: linux/amd64 and linux/arm64 archives were built from this commit with OCI revision/version labels and checksums.
  • Electron: npm run dist, unsigned packaging-control checks, and non-empty Setup.exe/.nupkg/RELEASES checks ran on windows-latest.
  • Local checks remain in the repository but are not run by GitHub Actions; this workflow intentionally builds, packages, and publishes only.