dsh-home-hosted 0.7.1 → 0.7.2

package/docs/DESIGN.md

@@ -38,7 +38,7 @@ its page.
 `onPortConflict: kill` arrived in home-hosted 0.6.0 and `persistent` in 0.6.3, and an older panel
 handed either key can refuse to *boot* from the config. The plugin used to consult the answering
 panel's version and refuse or drop them (`KILL_UNSUPPORTED`). That is gone on purpose: it pins
-`home-hosted@^0.7.2` and autostarts its own copy, so a panel older than those keys is only reachable by
+`home-hosted@^0.7.3` and autostarts its own copy, so a panel older than those keys is only reachable by
 deliberately preferring an old global install — and this is pre-1.0. Supporting older panels again means
 bringing that check back from history, not re-deriving it.
 

package/docs/PANEL.md

@@ -16,7 +16,8 @@ The range is stated twice and both must agree: `dependencies['home-hosted']` in
 is older). Bumping one alone makes the page recommend a range the plugin is not built against. A bump
 is therefore those two plus the version-coupled tests — *unless* the release moved something this
 plugin names: a path under `.hh`, `CONFIG_SCHEMA`, `serverSchema`, `/api/settings`, or a CLI
-subcommand. 0.7.2 (the panel's reverse proxy, all under `.hh/.proxy/`) moved none of them.
+subcommand. 0.7.2 (the panel's reverse proxy, all under `.hh/.proxy/`) moved none of them, and neither
+did 0.7.3 (DNS-01 through the panel's own DNS accounts, and a Namecheap API provider).
 
 That copy resolves to a pnpm path carrying a version and a peer hash, which moves on the next install
 and disappears when the profile is rebuilt. A boot entry that baked it in would fail exactly when it

package/lib/index.js

@@ -2722,7 +2722,7 @@ import { createRequire } from "node:module";
 import fs11 from "node:fs";
 import path9 from "node:path";
 import process5 from "node:process";
-var EXPECTED_RANGE = "^0.7.2";
+var EXPECTED_RANGE = "^0.7.3";
 var MIN_SUPPORTED_VERSION = "0.7.0";
 function pinnedManifestPath() {
   try {