Repository navigation
Drop the 0.10 bind import and the legacy forge installation state - #53
Merged
Merged
Conversation
Bobowski
force-pushed
the
cli-http-split
branch
from
November 2, 2026 22:56
4c77e94 to
588c883
Compare
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bobowski
force-pushed
the
drop-010-migrations
branch
from
November 2, 2026 22:56
26fab25 to
5331f33
Compare
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
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.
Intent
Remove the code that moves a 0.10 host to 0.11. Source: the user, in the Yard audit. The user asked me to check the host with the yard CLI first. This pull request stacks on #52.
Found
The host runs 0.11 and has moved:
yard --versionprints0.11.0.yard statusshowsyard-app-1on the commit of The deploy container is the only deploy record and the deploy lock #47.hostcolumn ofyard statuscomes from the site files, so the site files exist. Thus the 0.10 import does nothing at boot.yard forge ls --jsonshows the GitHub state with aninstallationslist, and each entry has an account. Thus no state has the old top-levelinstallation_id.The code that only served the move:
sites._import_binds,_bind, and_owner: with no site file, boot wrote default sites from the 0.10 bind routes that Caddy resumed. Four tests covered it, one of them on a real Caddy with a 0.10 autosave.Forge.installationsread a top-levelinstallation_idas one installation.installation_forlet an installation with no account own every repo. Eachsavedropped the old keys.Changed
sites.bootonly loads the Caddyfile, with the same retry when Caddy is not up yet. Three new small tests cover the retry, the give-up, and a refused load.Forge.installationsreads theinstallationslist only.installation_formatches the account, case-insensitively. The saves drop onlyinstallations.CHANGELOG.md: two breaking lines ("upgrade a 0.10 host through 0.11 first") and the line for the hosts cache from One Podman look for the status report and the app page; compose runs through Podman.stream #50.AGENTS.mdno longer names_import_binds.Not done
CADDY_ADMINstays inops/compose.yml.ops/Caddyfilesets the same admin socket, so the env is now redundant. But a change to the Caddy service recreates the Caddy container on the next yard deploy, and this pull request must not touch the proxy.status._image_plan(a host with no labelled deploy container) stays. It also serves an app that has no deploy container at all.Proof
Questions
None
🤖 Generated with Claude Code