Release v1.64.0-beta.3 candidate

Issue: #156
User-Visible: yes
This commit is contained in:
Sergey Matyunin
2026-08-14 22:31:36 +03:00
parent 6ebf12af1e
commit 20d7883699
12 changed files with 25 additions and 23 deletions
+2 -2
View File
@@ -21,8 +21,8 @@ metadata). Only an explicit owner-approved emergency hotfix may skip this gate.
| Item | State |
|---|---|
| Version | **v1.64.0** everywhere (manifest, const.py, package.json, CARD_VERSION) — stable promotion candidate after published v1.64.0-beta.2 |
| Current local cycle | v1.64.0 promotes the published beta line without product-code changes. It contains the read-only cold-start fix (#131), persistent virtual-light toggles (#107), four-phase Sun background (#146), visible plan snap topology (#137), shared-wall room autoclose (#138), seamless wall junctions (#141) and dialog-footer polish (#140), plus merged test, CI, process and documentation maintenance. The independent #124 exact-SHA view-toggle performance debt remains open under the owner's accepted exception. |
| Version | **v1.64.0-beta.3** everywhere (manifest, const.py, package.json, CARD_VERSION) — performance-repair candidate after the stable gate exposed #156 |
| Current local cycle | v1.64.0-beta.3 preserves the published beta feature line and removes the Full Performance regressions from #156: runtime consumers no longer build an unused physical-wall union on every floor switch, and initial Plan snap hover updates only its active marker. The owner explicitly authorized implementation and self-review in one Codex session while Claude/status automation was unavailable. After a green exact-SHA beta, stable v1.64.0 is promoted again without product-code changes. The independent #124 view-toggle debt remains open under the owner's accepted exception. |
| Hidden Labs Stage | #89 Stage 1 ships in v1.63.0-beta.1. #122 Stage 2 ships in v1.64.0 and evolves the same hidden, expiring `iso` experiment with matte walls, a low exterior floor edge, restrained shared shadows and live vertical door/window/gate panels. Flat remains default; editors and `houseplan-space-card` remain flat; live floor effects and HA actions remain unchanged. Public activation remains a separate task. |
| Workflow | Superseded 2026-08-12: the pre-1.62 rule of "local edits without tests or commits" is **dead** — since release 1.62 every product change follows `PROCESS.md` (issue in `S5-ready`+, branch `issue/<NN>-slug`, trailers on every commit, review pipeline; `AGENTS.md` is the summary). Release mechanics below remain current. A requested pre-release gets a production build plus the smallest targeted unit/smoke set covering the changed surfaces, one tested `dev` commit/tag and a GitHub Release with `prerelease=true`; `main` stays untouched. The complete local frontend/backend/smoke gate runs only before a stable release, after which `main` is fast-forwarded to the exact tested `dev` SHA and the GitHub Release uses `prerelease=false`. Release bodies are short and bilingual (Russian first): only significant user changes get individual bullets, while minor/code-only work is grouped as `Мелкие исправления и улучшения` / `Small fixes and improvements`; every body ends with separate links to the Russian and English changelogs. Detailed RU/EN changelog bullets may link the corresponding closed GitHub Issues; open or partially delivered issues are never presented as shipped. Telegram announcements are sent only for stable releases; beta and RC publication is silent. `docs/RELEASE-NOTES.md` is the current canonical body instance; `npm run release:prerelease -- <tag> --issues=… --yes` is the primary local publication path and the manual `Publish prerelease` workflow is its GitHub-only equivalent once present on `main`. Nothing is copied to the home instance by hand |
| GitHub | https://github.com/Matysh/houseplan-card — [Issues](https://github.com/Matysh/houseplan-card/issues) are the canonical task records; their labels carry priority and workflow status (`PROCESS.md` §9). GitHub Projects is no longer used. `main` carries stable releases; pre-release tags may point directly at `dev`. Work lands on `dev` and is merged into `main` for a stable release, so `dev` is normally equal to or ahead of `main`, never behind. Push via SSH key `ha_jb` (remote git@github.com:…); API releases via the fine-grained PAT in `~/.git-credentials` (Contents R/W, issued 2026-07-23) |