Skip to content

docs: fix Windows PowerShell install + refresh version examples - #333

Merged
srikanth-bitdynamics merged 2 commits into
mainfrom
docs/windows-install-fix
Aug 25, 2026
Merged

srikanth-bitdynamics merged 2 commits into
mainfrom
docs/windows-install-fix

Conversation

@srikanth-bitdynamics

@srikanth-bitdynamics srikanth-bitdynamics commented Aug 25, 2026 •

Copy link
Copy Markdown
Collaborator

The bug (Windows install)

Following the Windows install steps in getting-started.md on a clean Windows box fails:

Move-Item : Could not find a part of the path.
+ Move-Item canton-devkit-dist\canton-devkit.exe "$env:USERPROFILE\bin\ ...
+ FullyQualifiedErrorId : MoveFileInfoItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand

The snippet moved the binary into %USERPROFILE%\bin but never created that directory (Move-Item doesn't create a missing destination → DirectoryNotFoundException), and ~\bin isn't on PATH by default, so the closing canton-devkit version wouldn't have resolved either. The macOS/Linux steps work because they use /usr/local/bin, which exists and is on PATH.

Fix: create %USERPROFILE%\bin if missing, Move-Item -Force into it, add it to PATH for the current session and persist it for future terminals, and note the Docker Desktop + WSL 2 requirement for localnet.

Also: refresh stale version examples

The macOS/Linux/APT/.deb install snippets still pinned v0.12.2 while the Windows one was current. Bumped every example to the current latest tag v0.17.4 so they agree. These remain placeholders users replace with the latest release tag.

Verification

Reproduced the original Windows failure and confirmed the corrected steps install and run canton-devkit version. Docs site builds clean (npm run build); the rendered getting-started page no longer contains the broken Move-Item and shows a consistent version across all channels.

Found while testing the Windows release package.

The Windows install snippet moved the binary into %USERPROFILE%\bin
without creating that directory or putting it on PATH, so a fresh Windows
box failed at Move-Item with "Could not find a part of the path"
(DirectoryNotFoundException), and the closing `canton-devkit version`
would not have resolved either.

Create the target dir, move with -Force, add it to PATH for the current
session and persist it for future terminals, bump the stale example tag,
and note the Docker Desktop + WSL 2 requirement for localnet. Verified by
reproducing the failure and confirming the corrected steps on Windows.
The Linux/macOS/APT install snippets still pinned the stale v0.12.2 tag
while the Windows one was current, so the examples now agree. These are
placeholders users replace with the latest release tag.
@srikanth-bitdynamics srikanth-bitdynamics changed the title docs: fix Windows PowerShell install steps (create ~\bin, set PATH) docs: fix Windows PowerShell install + refresh version examples Aug 25, 2026
@srikanth-bitdynamics
srikanth-bitdynamics merged commit 2c28092 into main Aug 25, 2026
@srikanth-bitdynamics
srikanth-bitdynamics deleted the docs/windows-install-fix branch August 25, 2026 15:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant