NodePilot 1.4.0

The dashboard answers its history from precomputed hourly buckets and charts execution durations, the web UI gains minimal light and dark skins, HA recovery and execution dispatch were hardened on real PostgreSQL and SQL Server, and the desktop package can be installed over itself, uninstalled completely and installed again. CHANGELOG.md carries the full entries.

Upgrading from 1.3.0 — read this first

There is no automatic upgrade path from 1.3.0 or earlier. The development-era migration history was consolidated into a single baseline. A 1.3.0 database does not know that migration, so 1.4.0 tries to create the schema again and the API stops at start-up with relation "AuditLog" already exists. A server update rolls back and keeps 1.3.0 running; the desktop setup reports the failed provisioning.

To move across:

1. On 1.3.0, export a system configuration backup (/backup or np backup export) and keep its passphrase.
2. Install 1.4.0 against a new, empty database. On the desktop, uninstall first and choose Delete everything.
3. Restore the backup.

Workflows, folders, machines, credentials, globals, users, custom activities, alerting rules and settings come across; execution history, audit log and statistics do not. Databases created by 1.4.0 upgrade normally from here on.

Dashboard

• Execution duration instead of a success-rate trend: median and P95 per time bucket, for all workflows or one selected workflow.
• History from hourly buckets. A 30-day window sums at most 720 bucket rows instead of scanning the raw table. The dashboard falls back to raw rows while the initial backfill runs and whenever the buckets stop being updated; buckets older than 32 days are removed.
• Minimal light and dark skins across the web UI.
• The AI chat page column and the floating widget can be dragged wider; the global launcher stays out of the workflow designer.

Desktop package

• Uninstall asks about your data: Keep data, Delete everything or Cancel (/PURGEDATA=1 unattended). Delete everything leaves nothing behind — database, keys, settings, logs, per-user app data and the certificate's private key.
• Installing over a running installation works: setup backs up the database and stops the app, clients and services before copying files, and aborts without touching a file if it cannot.
• No default password. The first administrator is created on the setup page. Data left behind by an uninstall is offered for keeping or deleting on the next install (/DISCARDDATA=1 unattended).
• The API service now starts reliably on slow machines, and a failed provisioning makes setup exit with code 20 instead of 0.

Engine, HA and operations

• HA recovery works in bounded batches and no longer holds the lease for a whole backlog; dispatch claims are atomic on PostgreSQL and SQL Server.
• llmQuery retries without temperature when a reasoning model rejects it.
• The REST activity reaches hosts whose DNS records mix link-local and routable addresses; blocked addresses are still never connected to.
• /metrics works again with Prometheus scraping enabled — every scrape containing a histogram answered HTTP 500 since 1.2.15.
• The service reads its early start-up configuration from the installation instead of System32, so Performance:ManualTuning applies from the first second.
• Both installer wizards carry the NodePilot logo.

Downloads

File	What it is
NodePilot-Server-Setup-1.4.0.exe	Windows server installer (GUI and /VERYSILENT)
NodePilot-Desktop-Setup-1.4.0.exe	offline desktop installer, all services set to start at boot
NodePilot-1.4.0.zip	server payload for Install-NodePilot.ps1
NodePilot-Deploy-Scripts-1.4.0.zip	the install scripts on their own, so the verifying script can be had before the archive it verifies
NodePilot-Switcher-1.4.0-win-x64.zip	the Switcher standalone, for a machine with no NodePilot installation
NodePilot-1.4.0.zip.manifest.json + .p7s	detached signed manifest
nodepilot-release-signing.cer	publisher certificate
NodePilot-1.4.0.SHA256SUMS.txt	checksums covering every file above

Signature and first run

Publisher: CN=NodePilot Release Signing.
Certificate thumbprint: 277EAB317A581C88302CE92BE805938C86B4650D.

Both installers are Authenticode-signed with a self-signed release certificate. Windows SmartScreen will show an unrecognised-app prompt and the chain will read as untrusted — there is no public CA behind this certificate yet. Before choosing More info → Run anyway, compare the download's SHA-256 against the attached checksum file and the publisher certificate against the thumbprint above. The attached .cer carries no private key.