Repository navigation
fix: unify FTW update guidance and block retired release publication - #1473
Conversation
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a01a0bdb23
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| The old Docker workflows, tags and receipts describe past releases and remain | ||
| for recovery and audit. Their presence is not authority to cut another 2.x or | ||
| 3.x release. Do not dispatch them or the old Home Assistant publication path. |
There was a problem hiding this comment.
When a maintainer opens .github/workflows/release.yml, its lines 3–8 and 29–30 still explicitly authorize an exceptional 2.x safety release, while scripts/check-legacy-release-line.sh continues to accept 2.x tags. That directly contradicts the new no-dispatch policy here and leaves a documented, executable path for publishing a release on the retired line; update or disable those workflow entry points as part of retiring the path.
AGENTS.md reference: AGENTS.md:L228-L234
Useful? React with 👍 / 👎.
| Move directly to the new line using one of the paths below. Keep the old | ||
| installation and its data for recovery; the new setup does not import them. |
There was a problem hiding this comment.
When an existing-site owner follows this new switch-now guidance but invokes scripts/install.sh --help or hits its refusal path, the active installer still says that an existing installation “must wait for the guided 0.x migration” and directs the owner to “try 0.x beside it.” That stale user-facing path contradicts the newly selected separate-card/project migration guidance and can cause owners to defer the required switch, so the active installer messages need to point to the same current guide and terminology.
AGENTS.md reference: AGENTS.md:L202-L206
Useful? React with 👍 / 👎.
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
Signed-off-by: Fredrik Ahlgren <fredrik@sourceful-labs.com>
frahlg
changed the title
1 participant
Problem and result
Old install pages disagree about Docker, Pi images, 3.x beta and the new 0.x packages. A user can follow an old update path or leave two Core instances controlling the same equipment.
Make
docs/native-beta.mdthe common entry point, with a Swedish guide and a route for each install type. State the owner's policy: no further 2.x or 3.x releases; use new 0.x now. Explain separate new setups, the unshipped data migration, backups, MQTT, old start rules and checks after reboot. Align README, support, agent rules, both deployment-skill copies, product docs, all five Pi guides and retired script messages. The deployment skill no longer pulls retired Dockerlatestor applies a saved override as a general update recipe. Restore the old Pi-image URL as a retirement notice.Scope and safety
No runtime control or migration behavior changes. Native installer help and refusal messages use the same current paths. Current
beta.ymlandrelease-assets.ymlentry points fail before checkout or registry access. Manual publication throughrelease.ymlalso fails there; pushes still run the native Changesets version PR. Historical workflow revisions must not be dispatched. Retired scripts still exit without changing a site. Docker's missing-version message now asks for an exact published tag. Historical release artifacts and recovery material remain available.Paired with the website and Home Assistant documentation changes in
srcfl/ftw-webandsrcfl/home-assistant-addons. The owner requested and authorized this cross-repository audit and merge.Checked open PRs #1051, #1292 and #1364 and their reviews. This change uses separate install/release-policy sections and preserves their pending product, proposal and CLAUDE-shim work.
Verification
make verify: passed again after the publication guards (tests, vet and build).bash scripts/test-install-native.sh: passed.bash scripts/test-modular-compose.shandbash scripts/test-upgrade-paired-release.sh: passed after final wording changes; retired paths make no site changes.docker compose -f deploy/docker/compose.yaml config --quiet: rejects a missing tag with the new message; passes with an explicit published new 0.x tag.git diff --check: passed. No hardware behavior is changed or claimed as tested.Checklist
Paired PRs: web, Home Assistant. Merge Core before the links to its new guide go live.