Add native Windows installer and documentation - #676
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: e306c830e5
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| $release = Invoke-RestMethod ` | ||
| -Headers @{ "User-Agent" = "codedb-installer" } ` | ||
| "https://api.github.com/repos/$repo/releases/latest" |
There was a problem hiding this comment.
In Windows PowerShell 5.1 environments where ServicePointManager.SecurityProtocol does not already include TLS 1.2, this first Invoke-RestMethod still negotiates with the obsolete default because the TLS 1.2 setup runs later at lines 50-56. That means both the GitHub release lookup and the latest.json fallback can fail before the installer reaches the download step, so the documented PowerShell one-liner exits without installing; move the TLS-enabling block above this first network call.
Useful? React with 👍 / 👎.
|
@justrach Closed? Is there a different plan for windows install? |
1 participant
Summary
Why
codedb now publishes
codedb-windows-x86_64.exe, but the primary installation documentation still described codedb as macOS/Linux-only or directed Windows users to WSL. This made the shipped native binary difficult to discover and install safely.Follow-up documentation and distribution work for #621.
User impact
Windows x86_64 users get a one-command native installation with automatic checksum verification. Existing macOS/Linux installation behavior is unchanged.
Validation
0.2.5830, verified SHA256, installed, and returnedcodedb 0.2.5830irm ... | iexexecution shape validated against the checked-out installercodedeebee0.2.5830 package installed and ran the Windows binarygit diff --checkpassedNotes
latesttag was still 0.2.5823 during validation, so the root README does not yet recommend npm for Windows; the npm-specific README states Windows support begins with 0.2.5830.website/distoutputs are updated alongside their website sources.release/0.2.5829and the submission followsCONTRIBUTING.md.