commit 8129feb383c4d21a59dd37b2453e43e6d8bd943a
parent df50af1add048523cb133e042942308f0a49c318
Author: Jack Mordaunt <jackmordaunt.dev@gmail.com>
Date: Thu, 17 Sep 2026 08:14:28 -0400
docs: give the GOWORK override as a PowerShell command
The prose said "with GOWORK=off", which readers on Windows translate to
cmd's set syntax; that keeps a trailing space in the value and Go rejects
it as an invalid path. Spell out the form that works.
Diffstat:
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/readme.md b/readme.md
@@ -139,7 +139,11 @@ go test ./... ./cmd/preview/... ./cmd/shell-extension/...
The two command modules require the library at its latest tag; the versioned `replace` in `go.work` resolves that tag to the working tree inside the checkout, which is also what lets the tree build before the tag exists.
-Releasing: tag the root module (`vX.Y.Z`), which releases the library and `icnsify` together. Then run `go mod tidy` in `cmd/preview` and `cmd/shell-extension` with `GOWORK=off` so their `go.sum` files learn the new version, and bump the `replace` line in `go.work` to match.
+Releasing: tag the root module (`vX.Y.Z`), which releases the library and `icnsify` together. Then tidy the two command modules outside the workspace so their `go.sum` files learn the new version, and bump the `replace` line in `go.work` to match:
+
+```powershell
+$env:GOWORK = 'off'; go mod tidy; Remove-Item Env:GOWORK # in cmd/preview, then cmd/shell-extension
+```
## Roadmap
