From bccd7d098c81730714aa004ed8ff8684463cee6a Mon Sep 17 00:00:00 2001 From: Jay Weeldreyer Date: Mon, 6 Apr 2026 21:04:43 -0700 Subject: [PATCH] docs: add post-update validation guidance MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Adds a concise post-update validation checklist (git status, hermes doctor, version check, gateway status). Adapted from PR #3050 with corrections — removed inaccurate submodule claim (hermes update already handles submodules) and tightened the checklist. Cherry-picked and adapted from PR #3050. --- website/docs/getting-started/updating.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/website/docs/getting-started/updating.md b/website/docs/getting-started/updating.md index 04abcc40e..16bb0ce47 100644 --- a/website/docs/getting-started/updating.md +++ b/website/docs/getting-started/updating.md @@ -45,6 +45,20 @@ Already up to date. (or: Updating abc1234..def5678) ✅ Hermes Agent updated successfully! ``` +### Recommended Post-Update Validation + +`hermes update` handles the main update path, but a quick validation confirms everything landed cleanly: + +1. `git status --short` — if the tree is unexpectedly dirty, inspect before continuing +2. `hermes doctor` — checks config, dependencies, and service health +3. `hermes --version` — confirm the version bumped as expected +4. If you use the gateway: `hermes gateway status` +5. If `doctor` reports npm audit issues: run `npm audit fix` in the flagged directory + +:::warning Dirty working tree after update +If `git status --short` shows unexpected changes after `hermes update`, stop and inspect them before continuing. This usually means local modifications were reapplied on top of the updated code, or a dependency step refreshed lockfiles. +::: + ### Checking your current version ```bash