github jordibrouwer/nextdash v1.31.0

one hour ago

Compose stacks you can read, edit, check and run from the Containers view, reminders on bookmarks, related links on the preview card, and a bell that rings less and shakes more.

Bookmarks

  • new — Reminders on bookmarks. Set a time on a bookmark from its context menu (a drawn clock), with Z, with :remind <when> or :remind <name> <when> in the palette, or in the edit form; :remind clear removes it. A clock on the row shows that one is set, and a due reminder becomes a row in the bell that stays until you answer it. While the dashboard is closed the server looks once a minute for due reminders and pushes them once, as one combined push when several come due together; a reminder more than a week late is marked handled without a push, and the bell still shows it. A setting in Config turns the push off (reminder.go, dashboard-reminders.js, reminder-bell-source.js).
  • new — Related links on the preview card. The card of a bookmark gets a row with up to three links that belong with it, ranked on shared tags, the site, and bookmarks opened together. A tag or site counts for less the more of the library carries it, so a common site or a tag on a third of the library relates nothing by itself, and the same page under http and https or with and without www. is the bookmark itself, not a relation. The row has a checklist entry in the preview settings, a context menu item, and :related in the palette (Enter opens a link, Alt+Enter opens it in a new tab). GET /api/related?url= answers read-only (related.go, dashboard-related.js).
  • new — Shift+V opens What's new. Listed in the keyboard help and the legends.

Search

  • fix — A tag typed in full is a best match. Typing a bookmark's whole tag now ranks that bookmark first instead of among the fuzzy hits (fuzzy-search.js).

Config

  • fix — The key legend sits at the foot of Bookmarks and Data & backups, and there is no rule under the Config header.

Containers

  • new — Compose stacks work in the demo. The demo's five stacks (media, photos, security, infra, home) have a compose.yml and a .env in a folder of their own, written again at every reset, and their containers carry the labels a real compose project has. NEXTDASH_COMPOSE_MAP is set for the demo (/srv/stacks on its imaginary host). The demo's daemon plays the helper container: it reads the arguments of docker compose, checks the files (a YAML error with its line, a service without an image, a variable nothing sets), and changes the demo's own containers for Up (a missing service is made, a stopped one started, one whose image changed made again), Down (which stops the containers and keeps them, because a stack with none would leave the list and could not be brought up again until the reset), Pull and Restart, with the dry run the preview needs and compose version. Nothing runs a docker binary or reaches a registry. The compose routes moved from the demo's denied writes to its allowed ones (docker_demo_compose.go, demo_guard.go).
  • fix — The stack panel stays open after a compose run. Pressing Close on the progress window of a run that failed (Up, Down, Pull) counted as a press outside the panel and closed it, so the exit code and last lines were lost together with the panel. The drawer now ignores presses in that window (list-view-drawer.js).
  • new — Find a stack's compose files from its labels (engine). NEXTDASH_COMPOSE_MAP (hostPrefix:containerPrefix, comma separated) says where a stack folder appears inside nextDash. A label path is mapped by the longest prefix, must still lie under that prefix after symlinks are followed, must be a regular file of at most 1 MiB, and compose files must end .yml or .yaml. The request names only the project; every path comes from the daemon's labels (docker_compose_files.go).
  • new — Secrets masked in compose and env files (engine). Values under keys like password, secret, token, key, cred or private, in the map and the list form of environment, and every value in an env file, are replaced by •••••• in place, so comments and layout stay. A file that does not parse is masked line by line (docker_compose_redact.go).
  • new — See a stack's compose file. GET /api/docker/compose/{project}/files answers the compose files and env files of a stack, masked, with a sha256 and the state of each (unmapped, missing, denied, outside, not YAML, too large), and what to add when the folder is not mapped. Not on other Docker hosts. Config → Containers' status gains the resolved map (docker_compose_api.go).
  • new — Reveal one masked value. GET /api/docker/compose/{project}/files/value gives back a single value the file view masked, behind the write token, never cached (docker_compose_api.go).
  • new — Edit a stack's compose file. The stack panel's Compose file and .env tabs get Edit: a plain text box on the file, an unsaved marker, Save and Reload. Save sends the version it loaded, so a file changed on disk since is refused and you choose Reload or Keep editing; a YAML error shows its line and column and puts the cursor there; a file on a read-only mount or without write permission says which, instead of a Save button. Only with NEXTDASH_DOCKER_CONTROL=1, and never for nextDash's own stack. The Backups tab lists the copies made before each save and restores one after asking (dashboard-docker-compose.js).
  • new — Up, Down and Pull for a stack. The stack panel has Up, Down and Pull with the output as it runs, in the same progress list as an update; Down asks first and says that volumes and images stay. With control off, on nextDash's own stack or on another Docker host the buttons are disabled and say why (dashboard-docker-compose.js, dashboard-docker-actions.js).
  • new — Save a stack's compose file (engine). PUT /api/docker/compose/{project}/files checks the YAML first (line and column on an error, 422), refuses a file changed on disk since it was opened (409, with the current sha256), keeps nextDash's own stack read-only, and copies the old file to data/compose-backups/ before every write. The file keeps its mode, owner and symlink; when the folder is not writable the answer says to set NEXTDASH_RUN_AS_ROOT=1 or fix ownership. GET …/files/raw hands over the unmasked file behind the write token (docker_compose_save.go).
  • new — Compose file backups (engine). The last 20 copies per file are listed (GET …/backups) and can be put back (POST …/backups/{stamp}/restore); a restore first copies the current file. Backups stay out of the settings backup, since they can hold secrets (docker_compose_save.go, backup.go).
  • new — Run a stack's compose without a terminal (engine). POST /api/docker/compose/{project}/up|down|pull runs docker compose in a short-lived helper container (NEXTDASH_COMPOSE_IMAGE, default docker:29.7-cli; the socket's host path from nextDash's own mounts or NEXTDASH_COMPOSE_SOCKET) with the stack folder at its own host path, checks the file with compose config -q before Up, streams the output, and removes the helper whatever happens. Down never removes volumes. Not offered for nextDash's own stack or on other Docker hosts yet (docker_compose_run.go).
  • fix — nextDash's own helper containers stay out of sight. The compose helper and the disk-size probe no longer show in the container list, the Glances and system views, or raise a crash notice when they exit non-zero (docker_compose_run.go, docker_notify.go).
  • new — Check a stack's compose file without touching it (engine). POST /api/docker/compose/{project}/check runs compose config -q in a helper and answers {ok}, or 422 compose-invalid with the output and, when compose names one, the line and column. Same gates as Up, no container is locked. A body {file, content} checks that text in place of the file, fed to compose on stdin, so nothing is written (docker_compose_ext.go).
  • new — Edited, not applied (engine). Every successful whole-stack Up records the sha256 of the stack's files in data/compose-applied.json; the files answer carries appliedSha256 per file and pendingChange per file and for the stack. Only stacks nextDash itself brought up are flagged; Down forgets the record (docker_compose_ext.go).
  • new — Up, Pull and Restart for one service (engine). The run routes take ?service=, checked against the services in the stack's files and in its containers' labels (compose-unknown-service otherwise, compose-service-not-allowed for Down). Only that service's containers are locked (docker_compose_run.go).
  • new — Restart and Pull and Up for a stack (engine). Run actions restart and update (validate, pull, up -d). An update writes the update history for every container whose image changed; nextDash's own stack stays refused (docker_compose_run.go).
  • new — One log for the whole stack (engine). GET /api/docker/compose/{project}/logs/stream merges every container's log as NDJSON, each line tagged with its service and container; the history of all services comes out in time order first. Behind the write token like a container's log, no control needed (docker_compose_ext.go).
  • new — A Services tab in the stack panel. The panel now opens on the stack's services: state, health, ports and the image, with round Up, Pull and Restart buttons per service that act on that service alone (dashboard-docker-compose.js).
  • new — Check, diff and Apply in the editor. Check runs compose config on the text in the editor, saved or not, and marks the line it names, with a Go to line link. A Changes chip shows the diff of your edit against the file on disk before saving, and each backup has a Diff button that shows what restoring it would change. Apply checks, saves, then runs Up; a text that fails the check is never written, and if Up fails the file stays and the previous copy can be restored. Ctrl/⌘+S saves and Tab types two spaces (Esc then Tab leaves the field).
  • new — Edited, not applied. A chip on the stack heading, a dot on the Compose tab and a note on the Services tab appear when the file changed after the last Up nextDash ran.
  • new — Stack Restart, Pull and Up, and a Logs tab. Restart (asks first) and Pull and Up sit in the heading; the Logs tab follows every service in one stream, each line tagged, with a chip per service to filter (docker_view.go now sends composeService; GET …/backups/{stamp}/raw serves a copy for the diff).
  • fix — The stack panel no longer drops unsaved edits. Going Back, opening another container or stack, pressing Escape or beside the panel, or restoring a backup now asks first and names the file whose text would be lost. Restore says so in its own question, and the page asks before a tab with an unsaved edit is closed.
  • fix — The Logs tab keeps following. The end-of-stream markers no longer show as blank rows. When a service stops or is recreated (Up, Restart) the stream opens again from the last line, a dropped connection retries with a growing wait and says so instead of "Following", and after the last try a Reconnect button appears.
  • new — The stack's Logs tab reads like a container's log. Search with next match (Enter), Filter, All / stdout / stderr, Last N, Timestamps, Wrap, Copy, Download and Follow (f) now work on the whole stack, with a line count; the tab and the single-container logs window share one reader (dashboard-docker-logs.js, DockerLogView).
  • new — Pause and Resume a stack's log. A Pause button (key p) holds new lines back while the connection stays open; the status line says Live, Paused · N waiting, Reconnecting or Stream ended, and Resume brings in every waiting line.
  • new — Open a stack's logs in the large window. The Logs tab has an Open logs window button that shows every service of the stack in the same window as a container's log, with chips per service.
  • fix — The container panel keeps its image and stack link after Back. Coming back from the stack panel with its back link left the chips under the tabs empty, because the container was reopened by name only; it is now looked up in the list first (dashboard-docker-drawer.js).
  • new — The stack link says where it leads. The chip in a container's panel reads "Compose stack {name} ›" with a tooltip naming the services, compose file, .env, logs and backups.
  • new — Info buttons in the stack panel. An ℹ above the tabs explains Reload, Up, Down, Pull and Restart (and that nextDash runs compose in a helper container); each tab has one for Services, Compose file and .env, Logs and Backups, in the same modal as the view headers.
  • new — The stack Logs tab is narrow-friendly. Search, Pause and a ⋯ menu (Follow, Filter, stdout/stderr, Last N, Timestamps, Wrap, Copy, Download) fit one row, the log area uses the panel's height, and a labelled Open logs window button sits above the service chips.
  • fix — The stack heading in the list shows "Edited, not applied". The chip sits next to Files on every stack nextDash started, without opening the panel.
  • new — Apply shows its steps. Check, Save and Up appear as one list under the editor, each with its state. A failed Check says nothing was written; a failed Save says nothing was started; a failed Up says the file stays and offers the previous copy. A text too long to check (over 96 KiB) goes straight on to Save, since Up checks it.
  • fix — Editing a .env file no longer ends in a generic error. A .env file has no Check button; Apply saves it and runs Up. A file that cannot be checked says so in words.
  • new — Up asks before it recreates. Up, Pull and Up and Apply confirm once: services whose file or image changed are recreated, and variables that only exist in your shell or an env file you passed by hand are blank in the helper.
  • new — Compose files in Config → Containers. The Connection panel shows the folders NEXTDASH_COMPOSE_MAP resolved to, what it refused, or the variable to set when none is.
  • fix — Small faults in the stack panel. Two masked values on one line each get their own Reveal, named by key; Go to line follows the error you pressed; a second Edit says why nothing happens; the log chips say which one is on; the editor text is 16 px on phones so iOS does not zoom; the services table becomes one block per service on a narrow screen; the panel no longer keeps the unmasked text after a save.
  • new — Variable check before Up (engine). POST …/check answers varCheck: each ${VAR} the compose files use that no env file sets, with the services, files and lines that use it. Unset without a default is a warning (it becomes blank), set empty on purpose is fine, ${VAR:?msg} and a missing env_file block. The same data rides on the 409 compose-unset-vars and the 422 compose-invalid of an Up, and an unsaved .env or compose text is checked in place (docker_compose_vars.go).
  • new — Preview what Up would change (engine). POST …/preview runs compose up -d --dry-run in the helper and answers what would be recreated, created, started, left alone or is an orphan, each with its reason (image, ports, config, new service, not in file); an unsaved edit can be previewed. A Compose older than 2.20 answers compose-too-old. Up takes ?removeOrphans=1, off by default (docker_compose_preview.go).
  • new — A watch on the stack after Up (engine). For a minute (longer for a long health-check start period) nextDash follows the stack's containers and says watching, slow, healthy or problem (GET …/watch, GET …/watches). A restart loop, an unhealthy or a failed container raises a container notice that follows the usual mute list, and POST …/watch/restore puts back the copy taken before the last save and runs Up again (docker_compose_watch.go).
  • new — Setup check data for Config → Containers (engine). The Docker status gains compose.setup: six checks (mapping, mount read-write, user and file owner, helper image, socket path, container actions), each ok or failed with a one-line fix in the real setting names such as NEXTDASH_COMPOSE_MAP, NEXTDASH_COMPOSE_IMAGE and NEXTDASH_COMPOSE_SOCKET (docker_compose_setup.go).
  • new — One summary line per stack (engine). GET /api/docker/compose/summary gives each stack its pending-change flag, health count, restarts in 24 hours and, when nextDash already samples them, CPU and memory, without any new stats polling (docker_compose_setup.go).
  • new — Edit a .env in place without losing its secrets (engine). An env file saved with masked: true keeps every value that is still the mask exactly as it is on disk; the mask text is never written as a value, by any save of any file. A backup can be compared with the current file (GET …/backups/{stamp}/diff) without a secret value in the answer: a changed secret reads as changed, not as what it was (docker_compose_envedit.go, docker_compose_diff.go).

Dashboard

  • fix — The bell rings at most once per five minutes. Several sources arriving close together, a second tab or a reload could each play the tone; now one tone sounds per five minutes, and the time of the last one is shared between tabs in this browser (notification-bell.js).
  • new — The bell calls for attention more often while something is unread. The badges pulse every 20 seconds (was 60, and only until the panel had been opened) and the bell shakes every 90 seconds (was every hour), both until the rows are read or answered. The shake is wider and the bell swells while it swings, and the badge pulse is larger (notification-bell.js, notification-bell.css).
  • fix — Dropping text that is not a link no longer leaves the dashboard. Words or a mailto: link dragged in from another window were taken at dragover but not at the drop, so Firefox loaded them in the dashboard's tab. The drop is now cancelled whenever it was taken (dashboard-link-drop.js).
  • fix — The bell drops Immich failures once they are cleared. With status tiles on two pages for one server, the bell kept the largest failed count, so a tile on a page left behind held it after the jobs were cleared. It now follows the newest answer per server (immich-bell-source.js, dashboard-media-tile.js).
  • fix — Show what's new works again. In Config → News & features the button opens the release it belongs to. In the What's new modal, rows wrap on narrow screens and pictures show in the rows and larger (whats-new-modal.js, modal.css).
  • fix — The preview checklist keeps its upgrade markers. Saving settings no longer drops the markers that tell which checklist rows are new (models.go).

Docs

  • docs — README.md, MANUAL.md and the feature pages. The README feature list names Compose stacks, reminders and related links, and its variable table has the four NEXTDASH_COMPOSE_* settings; the manual has the Reminders and Related links sections, Shift + V, :remind, :related and chapter 15.12; five new pictures under screenshots/manual.md/ come from tests/manual-screenshots-v1-31.spec.js.
  • docs — Config → Help, Tips, News & features, cheat sheet. The bell's and the notifications' help say the new rhythm (every 20 seconds, every 90, one tone in five minutes) in all six languages; Help gains a Compose stacks paragraph under Containers and Related links under Bookmarks, and a Reminders paragraph under the bell. Tips tipReminder, tipRelatedLinks and tipComposeStacks; three News & features cards with since: "v1.31.0"; cheat sheet rows for Z, Shift + V, :remind and :related, and the sheet and its PDF generated again.
  • docs — translations. 234 strings of the stack panel that existed only as English fallbacks behind its t() wrapper, and 50 for reminders, related links and the Compose lines, are in all six locale files.
  • docs — static/data/whats-new/v1.31.0.json, its index entry and one picture under media/; whats-new-stub.js moved to 2026.11-dashboard-release-v1.31.0 and whats-new-v380.
  • Compose lines in the example files. Commented NEXTDASH_COMPOSE_MAP and a read-only mount in docker-compose.yml and docker-compose.prod.yml.
  • fix — More secrets stay masked in a compose file. Credentials inside a URL (DATABASE_URL, SENTRY_DSN), values in labels, command and x- lists, a secret passed through a YAML anchor and alias, the lines of a block value in a half-edited file, and every .env line that is not plain NAME=value are masked now; keys named auth, dsn, pwd, salt, jwt, cookie, session or webhook count too. When in doubt the value is masked (docker_compose_redact.go).
  • fix — Up uses the variables the stack was started with. The helper passes the stack's environment_file as --env-file and the profiles of its running services. Up, Apply and Pull and Up now stop with compose-unset-vars and the names when a variable is set nowhere (?allow-unset=1 goes on anyway); Check lists them as unsetVars (docker_compose_run.go, docker_compose_ext.go).
  • fix — A slow Pull and Up no longer kills a running compose up. Pull and Up each get their own limit (30 minutes for a pull, 10 for starting). A start that runs over is left to finish and answered compose-timeout with what to do; the next run is refused (compose-running) until it is done. A pull that runs over is stopped, and nothing was changed (docker_compose_run.go).
  • fix — A stack whose containers disagree on their files keeps the override order. The run follows the newest container's compose files in their own order instead of a sorted list, where an override file could land before its base; the file list still shows every file (docker_compose_files.go).
  • fix — Check and Apply work on an edited .env. Check feeds the edited text to compose as the stack's env file; the text of a service's own env_file entry is checked as saved and the answer says stagedIgnored (docker_compose_ext.go).
  • fix — The helper's log follower ends before the run does. No line is written after the run returned, and the output buffer is guarded against the race (docker_compose_run.go).
  • fix — nextDash's helpers are hidden at the source. listContainers never returns a helper, so the update checker, MCP tools, discovery, the status page, auto-update and the disk views skip them too; finished compose helpers of any stack are removed once at start-up (docker_client.go, docker_notify.go).
  • fix — Saving a compose file explains a mount it cannot replace, and copes with vfat and non-root. A file mounted on its own answers compose-file-mount ("mount the folder instead"); a file system that keeps no mode or owner (Unraid /boot, some shares) saves with a note; running as non-root, a file owned by somebody else is written in place so its owner stays (docker_compose_save.go).
  • fix — Private images: the helper can use the host's registry logins. NEXTDASH_COMPOSE_DOCKER_CONFIG names a folder with config.json, mounted read-only into the helper; a pull that fails on authorisation answers with that hint (docker_compose_run.go).
  • fix — compose-applied.json is in the data-file register. It is never exported (backup.go).
  • fix — A bare-metal or rootless daemon gets its own socket path. Outside a container the helper binds NEXTDASH_DOCKER_SOCKET instead of /var/run/docker.sock (docker_compose_run.go).
  • fix — Every masked value gets its own Reveal. Each masked value in a compose or env file now carries its name and an index, and the reveal route takes index (or line with key), so two secrets on one line, or the same variable twice in an .env, no longer share one button. The old key-only form still works; save and restore answer with the new sha256 only (docker_compose_redact.go, docker_compose_api.go).

v1.30.0 — 16 November 2026

Several Docker hosts in the Containers view, a widget you can put on every page, links dragged in from another window, a Watch feeds switch on the phone and three more Christmas themes.

Containers

  • new — Several Docker hosts in the Containers view. Under Config → Containers → Connection → Other Docker hosts you can add up to four more hosts, each reached through a Docker socket proxy (tcp) or the daemon's own TLS with a CA and an optional client certificate. With a host added, a strip of tabs above Containers | Disk picks the host; the list, side panel, logs and live logs follow it. Test says why a host does not answer (refused, no answer, certificate not trusted, client certificate turned down). A host is read-only until its Allow actions switch is on, and then start, stop, restart, pause, unpause and remove work there; NEXTDASH_DOCKER_CONTROL and the own-container guard apply to this host only. Check for updates works on every host's tab, with an arrow on a container that is behind and the same schedule as the local check; each host keeps its own results in docker-updates-<id>.json, which a backup leaves out. Update, rollback, Disk, the timeline, notices, statistics, widgets, and the settings kept by container name (hidden, muted, automatic updates, web address, icon) stay with this host. Hosts live in docker-hosts.json, their certificates in docker-secrets.json; the Containers tour has a new step on other hosts (seven steps now); installs with one host change nothing (internal/app/docker_hosts.go, docker_hosts_api.go, docker_endpoint.go, docker_host_request.go, dashboard-docker.js, dashboard-config-containers.js).

Bookmarks

  • new — Drag a link in from another window. A link, tab or address dropped on a category opens the bookmark form with the address, title, page and category filled in. Dropped elsewhere on the dashboard it follows paste (the choice dialog, the form or the Inbox, as set), and several links at once go to the Inbox. Your own drags, files and fields are left alone, and turning off Paste a URL turns the drop off too (dashboard-link-drop.js, link-drop-model.js).

Widgets

  • new — A widget on every page. The edit panel of a widget has a Show on pages switch: This page or Every page. On Every page the widget gets a copy on each other page, as an ordinary widget you move, resize, hide or limit to a screen per page; its name and settings are shared, so a change on one page carries to the others. Deleting a copy takes it off that page only. Switching back to This page removes the copies from the other pages, and a page created later starts with them. A stack stays on its page (widgets_everywhere.go, everywhere and everywhereSkip on a widget).
  • new — Five Immich widgets. Photos, Slideshow, Albums, People and Status read one Immich library. The API key goes in the X-Api-Key header and is set once in Config → Widgets; Connect lists your albums and people to pick from, and the same key works for all five. Photos and the slideshow can show the whole library, favorites, one album, one person, memories or On this day, in random, newest or oldest order, with or without videos, cover or contain, and a date caption; a tile can be drawn as a frame, grid, strip, hero or list. Status shows the library totals, the disk and the background jobs; a key that does not belong to an administrator gets neither totals nor jobs, and the panel says so. Pictures come through /api/widgets/<type>/image, so the key never reaches the browser (widgets_immich.go, widgets_immich_status.go).
  • new — A bell row for failed Immich jobs. When the Status widget sees failed background jobs, the bell gets a quiet row for them. It reads what the widget already fetched, so it makes no request of its own, and it stays until the jobs are cleared in Immich (immich-bell-source.js).
  • new — A one-photo frame and a slideshow in the media tile. A photo can fill the tile as one big picture with its date. The slideshow changes photo every 3 to 300 seconds (8 by default), loads the next one ahead, waits while the tab is hidden or the pointer or keyboard is on it, has Play and Pause, and starts paused with no fade for someone who asked their system for less motion (dashboard-media-tile.js).

Phone

  • new — A Watch feeds switch in More. On a phone, More → Quick settings has a Watch feeds switch. Off hides everything the watched feeds show on that phone: the feed icon and badge on rows, the hover card, the Watched feeds card on Status, the bell row and the tab count, and the phone stops fetching the watch list. The feeds stay watched and the server keeps polling them, so the desktop and push notices are unchanged. The choice is kept in this browser, not on the server (dashboard-feed-watch.js, mobile-tabbar.js).

Appearance

  • new — Three more Christmas themes in Holidays, each with a dark and a light half. Snow Globe (frost) puts the page inside a glass globe on a wooden base with a brass plate and a turning wind-up key, over a small town with a church, smoking chimneys, a string of lights and two skaters on a frozen pond. The snow lands: it piles up on the top edge of each category, and switching page shakes the globe so the caps come off and the snow swirls before it settles again. Paper Advent (paper) is a cut-paper village in four layers, lit from behind, that shifts in depth as the pointer moves, under a punched-out sky with a cut moon, a passing sleigh and a turning Moravian star; from 1 to 24 December one more window is lit each day and today's glows with its number, and paper snowflakes fall. Nutcracker Theatre (velvet) opens a red curtain once when the page loads, onto a stage under a gilt arch with swags, tassels and a crest, between tied-back drapes, with two nutcrackers who salute in turn, the Sugar Plum Fairy turning on a pedestal, footlights, sweeping beams, a spotlight that follows the pointer and falling sugar-plum glitter. Motion stops under reduced motion and with Effects off, leaving a still picture (static/js/theme-holidays.js, static/css/theme-holidays.css, internal/app/models.go).

Docs

  • docs — README.md, MANUAL.md and Config → Help. The manual gains the five Immich widgets (kinds, settings, key, a screenshot with public-domain photos), the six holiday themes and the new theme counts (223 families, 446 themes); the README counts 63 kinds and mentions Immich, other Docker hosts, a widget on every page and dragging a link in. Help gets paragraphs for a widget on every page, Immich, other Docker hosts, the Watch feeds switch on a phone, the Immich bell row and dragging a link in, and three new tips (tipAddDrag, tipWidgetEverywhere, tipHostOtherHosts).
  • docs — translations. 175 strings that existed only as English fallbacks in the code (Docker hosts, Immich, the slideshow, Show on pages, the link drop, the Watch feeds switch) are in all six locale files, and seven that validate:locale-referenced found missing; five tips nothing referenced any more are gone.
  • docs — static/data/whats-new/v1.30.0.json, its index entry and three pictures under media/; whats-new-stub.js moved to 2026.11-dashboard-release-v1.30.0 and whats-new-v379, tests/whats-new-hidden-release.spec.js follows. Four cards in overview-features.json with since: "v1.30.0". go generate refreshed asset_hashes_gen.go.

Don't miss a new nextdash release

NewReleases is sending notifications on new releases.