aaif-goose · DOsinga · Jan 29, 2026 · Jan 27, 2026 · Jan 27, 2026 · Jan 29, 2026
diff --git a/.github/workflows/bundle-desktop-windows.yml b/.github/workflows/bundle-desktop-windows.yml
@@ -57,7 +57,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@1a4442cacd436585916779262731d5b162bc6ec7 # pin@v3
         with:
-          node-version: 22
+          node-version: 24
 
       - name: Cache node_modules
         uses: actions/cache@2f8e54208210a422b2efd51efaa6bd6d7ca8920f # pin@v3

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -41,9 +41,16 @@ If you use Goose, Copilot, Claude, or other AI tools to help with your PRs:
 
 ## Prerequisites
 
-goose includes Rust binaries alongside an electron app for the GUI. To work
-on the Rust backend, you will need to [install Rust and cargo][rustup]. To work
-on the App, you will also need to [install node and npm][nvm] - we recommend through nvm.
+goose includes Rust binaries alongside an electron app for the GUI.
+
+We use [Hermit][hermit] to manage development dependencies (Rust, Node, npm, just, etc.).
+Activate Hermit when entering the project:
+
+```bash
+source bin/activate-hermit
+```
+
+Or add [shell hook auto-activation](https://cashapp.github.io/hermit/usage/shell/#shell-hooks) so Hermit activates automatically when you `cd` into the project (recommended).
 
 We provide a shortcut to standard commands using [just][just] in our `justfile`.
 
@@ -285,8 +292,7 @@ Then you can view your traces at http://localhost:3000
 This project follows the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) specification for PR titles. Conventional Commits make it easier to understand the history of a project and facilitate automation around versioning and changelog generation.
 
 [issues]: https://github.com/block/goose/issues
-[rustup]: https://doc.rust-lang.org/cargo/getting-started/installation.html
-[nvm]: https://github.com/nvm-sh/nvm
+[hermit]: https://cashapp.github.io/hermit/
 [just]: https://github.com/casey/just?tab=readme-ov-file#installation
 
 ## Developer Certificate of Origin

diff --git a/ui/desktop/.npmrc b/ui/desktop/.npmrc
@@ -1 +1,2 @@
 registry=https://registry.npmjs.org/
+engine-strict=true
diff --git a/ui/desktop/package-lock.json b/ui/desktop/package-lock.json
diff --git a/ui/desktop/package.json b/ui/desktop/package.json
@@ -4,7 +4,8 @@
   "version": "1.21.0",
   "description": "Goose App",
   "engines": {
-    "node": "^24.0.0"
+    "node": ">=24.10.0",
+    "npm": ">=11.6.1"
   },
   "main": ".vite/build/main.js",
   "scripts": {
Original file line number	Diff line number	Diff line change
		@@ -1 +1,2 @@
		registry=https://registry.npmjs.org/
		engine-strict=true
Copilot AI Jan 27, 2026 Copy link Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. With `engine-strict=true` and `"node": "^24.0.0"` in `ui/desktop/package.json`, any `npm install` in this package (including the `Bundle Desktop (Windows)` workflow which currently uses Node 22 via `actions/setup-node`) will now fail the engine check; please either align the CI/workflow Node version with `^24.0.0` or relax/remove `engine-strict` so existing release workflows continue to run. Copilot uses AI. Check for mistakes. zanesq Jan 27, 2026 Copy link Copy Markdown Contributor Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. @lifeizhou-ap is this valid? lifeizhou-ap Jan 29, 2026 Copy link Copy Markdown Collaborator Author Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. yes, what copilot said is valid. Now I decided to remove it and not to enforce the check. I've also update the doc so that it is clear for users about the prerequisite of hermit activation