@easonwumac/computer-linker 0.1.5 → 0.1.6

package/CHANGELOG.md

@@ -5,6 +5,17 @@ All notable changes to Computer Linker will be documented in this file.
 This project follows a small pre-1.0 changelog: breaking contract changes are
 called out even when the package version is still `0.x`.
 
+## 0.1.6 - 2026-06-27
+
+### Changed
+
+- The local npm release wrapper now loads `NODE_AUTH_TOKEN` from the Windows
+  User environment when the current shell process has not inherited it, avoiding
+  a false `npm whoami` 401 after saving a token with `setx` or the Windows
+  environment UI.
+- README and release checklist now document that Windows release token
+  hydration behavior.
+
 ## 0.1.5 - 2026-06-27
 
 ### Changed

package/README.md

@@ -491,9 +491,12 @@ release tag after a successful npm publish. After npm accepts the publish, the
 wrapper waits for registry metadata, verifies the npm dist-tag, and runs the
 published CLI from a clean temporary directory. Use `npm run release:verify` to
 repeat that post-publish check for the current `package.json` version.
-
-For a public alpha from this private dogfooding checkout, use the fresh public
-snapshot path:
+On Windows, if `NODE_AUTH_TOKEN` is saved in the User environment but the
+current shell has not picked it up yet, the release wrapper loads it only into
+the current release process before running `npm whoami` or `npm publish`.
+
+For a public alpha from this private dogfooding checkout, use the fresh public
+snapshot path:
 
 ```bash
 npm run public:release-ready

package/docs/release-checklist.md

@@ -56,8 +56,10 @@ release tag automatically before publishing, `--otp <code>` for npm 2FA, and
 version metadata, verifies the configured npm dist-tag, and runs the published
 CLI from a clean temporary directory. `release:verify` repeats only that
 post-publish registry check for the current `package.json` version.
-
-For the one-command local alpha readiness gate, run:
+On Windows, a `NODE_AUTH_TOKEN` saved in the User environment is loaded into
+the release process automatically when the current shell has not inherited it.
+
+For the one-command local alpha readiness gate, run:
 
 ```bash
 npm run alpha:check

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@easonwumac/computer-linker",
-  "version": "0.1.5",
+  "version": "0.1.6",
   "description": "One computer, one permissioned MCP linker for local workspaces.",
   "type": "module",
   "main": "dist/client.js",