Skip to content

docs: simple update steps for the first native stable - #1530

Draft
frahlg wants to merge 29 commits into
masterfrom
stable-update-guide
Draft

frahlg wants to merge 29 commits into
masterfrom
stable-update-guide

Conversation

@frahlg

@frahlg frahlg commented Oct 7, 2026 •

Copy link
Copy Markdown
Member

Keep the full FTW data and configuration through install, update and migration. The guide covers verified fullbackup export, separate source/target data, one controlling Core including autostart, interrupted work and return. It names the current published v0.142.1-beta.1 copy checks while retaining every older proof’s actual target version. Stable publication and the remaining migration requirements still gate this draft.

Coverage includes current offline/partial history, split SQLite fullbackup/restore/revert, Cloud-key omission and opt-in after portable restore, DuckDB cold-history interruption/resume, native Linux install across two test hosts, one custom Linux 386 copy, and one actual native macOS ARM64 source copy. Historical HAOS, MQTT entity, custom external and Docker updater/daemon/reboot checks keep their .1414 targets and limits. None supplies general migration, every community layout, Pi/SD or physical power-loss evidence.

The native macOS test passes 45 checks using an own unchanged-tag 2.3.2 Mach-O build with all source networking denied, including its API. Two published Linux target starts and native macOS return preserve charts, Parquet values, config, goals and identity. Its backup was checked outside the export container on the same physical Mac; source API, a published macOS package, installer and a backup on another physical host remain unqualified. The guide also notes that Ctrl-C can leave a live .142.1 backup running until #1615 reaches a later release.

This PR changes seven documentation/test files, with no runtime, version or consumed changeset changes; the docs-only exception applies.

Validation on 2ef6520277411b487fa50ae25c7b4841602655a1: 14 install-recipe tests and full make verify pass outside sandbox. CI run 38430714205 and all 12 checks succeed or skip as intended on that exact head. Human UI review and release/migration holds remain pending. The paired public site PR is srcfl/ftw-web#17; both remain draft until stable and all requirements are verified.

@frahlg frahlg added the no-changeset PR intentionally exempt from the changeset requirement (dev tooling / non-shipping) label Oct 10, 2026
@frahlg
frahlg force-pushed the stable-update-guide branch 2 times, most recently from 648decc to 4ddf3e9 Compare October 12, 2026 01:22
@frahlg
frahlg force-pushed the stable-update-guide branch 7 times, most recently from 1d263ca to ebfbbf9 Compare October 13, 2026 11:42
frahlg and others added 17 commits October 13, 2026 15:40
Put a one-table answer at the top of Install and update FTW and its
Swedish copy: what each kind of install does to reach v0.140.1. Make the
install recipes use a stable placeholder, document the Update button and
how channels follow the running release, and drop text saying no 0.x
stable exists.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
@frahlg
frahlg force-pushed the stable-update-guide branch from ed6e751 to 2b604e7 Compare October 13, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-changeset PR intentionally exempt from the changeset requirement (dev tooling / non-shipping)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant