Upgrade Neondeck

Neondeck checks the matching npm release channel shortly after startup and every 24 hours while it remains running. Beta installations follow next; stable installations follow latest. When a newer version is available, the dashboard shows a compact update banner and a durable notification.

Upgrading the application does not replace your runtime home. Repositories, sessions, watches, schedules, notifications, memory, skills, secrets, and app data remain under NEONDECK_HOME or your resolved XDG home. Neondeck applies recognized database migrations when the new server starts.

Before upgrading

Confirm the installed version and optionally create a manual app-data backup:

neondeck --version
neondeck db backup

Read the GitHub release notes for behavior changes or extra migration instructions.

Global npm installation

Beta releases currently use npm's next channel:

npm install --global neondeck@next

Once Neondeck reaches a stable release, stable installations can use:

npm install --global neondeck@latest

Restart a login service

On macOS or Linux, reinstall the service definition after the npm update. This refreshes its absolute Node and Neondeck server paths and restarts it:

neondeck service install
neondeck service status

Restart a foreground server

Stop the existing neondeck serve process with Ctrl+C, then start it again:

neondeck serve

Release archive installation

Download the new neondeck-<version>.tar.gz and matching .sha256 file from the GitHub releases page.
Verify the checksum before extracting the archive.
Install production dependencies in the new extracted directory.
Link the new CLI and reinstall or restart the service.

shasum -a 256 -c neondeck-<version>.tar.gz.sha256
tar -xzf neondeck-<version>.tar.gz
cd neondeck-<version>
npm install --omit=dev
npm link
neondeck service install

Use sha256sum -c instead of shasum -a 256 -c on systems where that is the available checksum command.

Source checkout

Follow the repository's development guide to update dependencies and rebuild. If a login service points at that checkout, run neondeck service install after rebuilding.

After upgrading

neondeck --version
neondeck status
neondeck service status

Reload any dashboard window that remained open while the server restarted. Neondeck displays a separate reload message if the browser bundle and running server versions do not match.

Disable automatic checks

Update checks make one unauthenticated request to the public npm registry and do not send runtime-home contents or product telemetry. To disable them, add this setting to the runtime-home .env and restart Neondeck:

NEONDECK_DISABLE_UPDATE_CHECK=1

Disabling the check hides update banners and notifications. You can still compare neondeck --version with the npm or GitHub release page manually.