Silence neovim default and ssh matchBlocks deprecation warnings #9
No reviewers
Labels
No labels
blocked
bug
decision
duplicate
enhancement
help wanted
invalid
landed?
question
ready-to-merge
stale
wontfix
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
allod/profiles!9
Loading…
Reference in a new issue
No description provided.
Delete branch "agent/hm-deprecations"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Every VM and the hypervisor's user profile stop printing the two neovim default warnings and the
matchBlockswarning attributed tohosts/dev/allod-dev/home.nix. The rendered~/.ssh/configis unchanged. The one behavioural change is that neovim no longer bundles its Ruby and Python providers, which is the 26.05 default and which nothing in this profile uses. If it is wrong, revert this PR.Merge order with allod/archetypes#80 (issue allod/archetypes#79). Do not land this before the archetypes migration, and do not bump the deploy lock's
profilesinput past this commit before itsarchetypesinput carries that change. With archetypes still onmatchBlocksand this profile onsettings, Home Manager's legacy conversion drops the framework'smkDefaultand retypes the identity file, andallod-devfails to evaluate with a conflicting-type error. Measured against the current archetypes pin. With the archetypes change in place, evaluation is clean.What changes
modules/preferences.nix:programs.neovim.withRuby = falseandwithPython3 = false, set explicitly becausehome.stateVersionpredates the new default.home.stateVersionis unchanged.hosts/dev/allod-dev/home.nix: the forge-host block moves fromprograms.ssh.matchBlockstoprograms.ssh.settingswith the same values under the upstream namesHostName,User,Port,IdentityFile,IdentitiesOnly.Risk
R2. Localized to two files; the config render is pinned byte-for-byte below; the ordering hazard above is the integration uncertainty, and the deploy repo's composed-layer canary fails a lock bump in the wrong order before any machine is built. Rollback is a revert.
Validation
Run by the integrator at
0f94a10:nix flake checkin this repo passes.--override-input profiles <this worktree> --override-input archetypes <allod/archetypes#79 branch>:allod-devevaluates with no warnings, and its rendered~/.ssh/configis byte-identical to master's. With this override alone, evaluation fails with the conflicting-type error described above, which is the ordering constraint.Cold cross-family review:
gpt-5.6-terraviacodex exec, reasoning efforthigh, read the diff at0f94a10(a Claude-family worker authored it). One finding, marked blocker: with the framework still onmatchBlocks, this profile'sIdentityFilestring collides with the legacy conversion's list at equal priority instead of overriding it. Confirmed by the measurement above; it is the ordering constraint at the top of this body, not a defect in the migrated form, and no code change follows. No other findings.Closes allod/profiles#8
closed in favor of allod/strategy#56
Pull request closed