chore(deps): update ghcr.io/pouzor/homelable-mcp docker tag to v3.3.5

[github-actions]

This PR contains the following updates:

Package	Update	Change
ghcr.io/pouzor/homelable-mcp	minor	3.1.2 -> 3.3.5

---

Release Notes

Pouzor/homelable (ghcr.io/pouzor/homelable-mcp)

v3.3.5

Compare Source

Features

• Deep-scan a single device from its inventory detail: the Services section gets a Deep scan button that sweeps the device over a port range you pick, prefilled with the full 1-65535 range and narrowable when you know where the service lives. The run is a normal Scan Run, so stop, progress and Scan History work as usual, and the fresh services are merged in — never replacing what you added by hand. (#​363)

Fixes

• A deep rescan of a slow host no longer comes back empty. The run hit its timeout and nmap discarded every port it had already found; the full range is now scanned in slices, a partial sweep is reported as partial instead of passed off as complete, and the timeout is a total budget between slices rather than an nmap flag. (#​363)
• A scan no longer repaints the service icons you picked by hand: the fingerprint's guess overwrote your choice, and cleared it outright on a port no signature covers. Since 3.3.0 the inventory row is the only copy, so one scan changed the service on every canvas at once. (#​363)
• A rescan finishing while you edit a device no longer throws the edit away, and it no longer tags every device it touches as network-discovered — a Proxmox guest, a rack mount or a hand-added host keeps its own source. A failed run is also recorded as error, the status Scan History filters and colours. (#​363)
• A property with no value gets the full node width for its label instead of being truncated against empty space. (#​362)
• A same-origin OIDC deployment behind a reverse proxy no longer answers 403 to every write. The CSRF check validated the browser's Origin against CORS_ORIGINS alone; the app's own origin, taken from OIDC_REDIRECT_URI, is accepted too, and startup warns when CORS_ORIGINS omits it. (#​360)

v3.3.4

Compare Source

Fixes

• A network scan no longer deletes the services you added by hand. The scanner replaced a device's whole service list with what it fingerprinted, so one scan wiped manual entries on every canvas at once and brought back the ones you had deleted. It merges now. (#​347)
• A node whose services were all replaced under it no longer renders empty: when nothing a node's view names is left on the device, the device's own list is drawn instead of hiding everything. (#​347)
• Properties added while running 3.3.0–3.3.2 survive the 3.3.3 upgrade. The view recovered from the pre-3.3.0 backup could not know about them, so they were hidden on every canvas; they are kept visible, and the per-canvas arrangement the backup does know is still restored. (#​347)

v3.3.3

Compare Source

Features

• Each node now keeps its own view of a device's services and properties: order and visibility are per node, so a service the scanner fingerprinted no longer appears on every canvas drawing that device, and a property added on one schematic stays there. The facts still live on the inventory row — hiding is per node, deleting is device-wide. Upgrades keep what each canvas showed today. (#​357)

Fixes

• The one-off view seed no longer re-opens the pre-upgrade backup on every boot: a node pointing at a deleted device kept matching the seed query and logged a recovery that recovered nothing. (#​357)

v3.3.2

Compare Source

Fixes

• Devices upgraded from 3.2.0 keep their ip, services, hostname, notes and hardware. The 3.3.0 migration aborted on timestamps SQLite returns as text, so nothing was carried across to the Device Inventory and every device read back blank. (#​347, #​348)
• A canvas saved while an earlier migration was stuck no longer loses its device facts: the migration now fills the blank inventory row that save created, instead of skipping the node and dropping the columns holding its only copy. (#​347)

v3.3.1

Compare Source

Fixes

• Approving a device no longer fails after an upgrade from 3.2.0: a node the 3.3.0 inventory backfill could not link kept the old device columns on nodes, and their NOT NULL constraint rejected every new node. (#​352)

v3.3.0

Compare Source

Features

• The Device Inventory is now the source of truth for device data: a node reads and edits its facts from its inventory row, and the device sheet is grouped by what a reader is after. (#​339)
• Per-service host override, so a service can point at a host other than the node's own. (#​338)
• A zone now parents the nodes dropped inside it. (#​343)
• Node properties accept an empty value. (#​345)
• Nodes can be given 0 connection points on top and bottom. (#​336)
• KVM switch added as a device type. (#​335)
• The sidebar version row links to the public changelog.

Fixes

• Alignment guides show for nodes inside groups and containers. (#​337)
• The status check interval is applied to the running scheduler. Thanks @​JaG-v2. (#​319)
• Bumped undici and ip-address to patch high severity advisories. (#​342)

Docs

• The pre-built GHCR images are documented in the install guide.

v3.2.0

Compare Source

Features

• Rack canvas: a third design type, next to network and electrical, with racks, mounted devices and port-to-port patching. (#​315)
• Declarative SVG faceplates picked from a visual catalog, including desktop NAS enclosures in 2, 4 and 5 bays. (#​315)
• Rack gear is filed in the Device Inventory, and a mount can be picked from the rackable entries. (#​315)
• Cables carry a type, colour, label and properties, printed on the canvas at the midpoint of the run. (#​315)
• Mounted devices follow the status check of the logical node they match, and links can be imported from the logical canvas. (#​315)
• Getting Started walkthrough covers the rack canvas. (#​315)
• Show the logical view of a mounted device, and link a mount to any Device Inventory entry. (#​323)

Fixes

• Guard rack rows against cross-design saves and half-applied faceplates. (#​315)
• A rack height edit no longer orphans its mounts; height and colour commit on blur, and a blanked field no longer shrinks the rack. (#​315)
• Import links is idempotent, and stays usable after a run that matched nothing. (#​315)
• Stop the device modal losing cables, status and inventory rows. (#​315)
• Name rack inventory entries the way the Device Inventory does. (#​315)
• Stamp the linked node's last-seen with an offset. (#​323)
• Bump js-yaml to 4.3.1 for CVE-2026-59870. (#​315)
• CI: stop the secret scan reporting pytest names as Lob keys. (#​315)

Docs

• Document the rack canvas for users. (#​315)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.