Skip to content

Add curl installer and release workflow - #6

Merged
kiranscript merged 1 commit into
mainfrom
website
Nov 17, 2026
Merged

kiranscript merged 1 commit into
mainfrom
website

Conversation

@kiranscript

Copy link
Copy Markdown
Owner

Summary

curl.exe .../install.ps1 -o %TEMP%\zipxp-get.ps1 ; powershell -File zipxp-get.ps1
  get.ps1
    download ZipXP-win-x64.zip + .sha256   (GitHub release, latest or -Version)
    verify SHA-256                         (abort on mismatch)
    gh attestation verify                  (if gh signed in; -RequireAttestation makes it mandatory)
    extract to temp
    install.ps1                            (existing per-user install)
    delete temp
 .github/workflows/
+├── release.yml     # v* tag: build, check, package, attest, publish release
 └── pages.yml       # also copies scripts/get.ps1 -> website/install.ps1
 scripts/
+├── get.ps1         # the curl installer

Also updates README, docs/install.md, the website quickstart/FAQ and the changelog. Corrects the earlier SmartScreen claim: curl.exe downloads carry no Mark-of-the-Web, so no prompt is expected on this path.

Evidence

  • Before: no installer; build from source only.
    After (tested from WSL, Windows PowerShell 5.1, local fake release):
get.ps1 -> Downloading ... SHA-256 verified ... Installed for this user
bad .sha256            -> "SHA-256 mismatch ... Nothing was installed."  (no files, temp cleaned)
-Version 0.0.1         -> installs from /download/v0.0.1
no such release        -> "Could not download ZipXP from ..."
curl.exe -o file ; powershell -File   -> installs, no temp left behind

Not tested: the attestation step and gh attestation verify (needs a real release). release.yml has not run.

Merge Danger

Door: two-way

Nothing runs until a v* tag is pushed. Reverting removes the script, workflow and docs.

Blast Radius: docs

  • After merge, Pages serves /install.ps1, and the docs advertise a command that fails with a 404 until the first release (v0.2.0) is tagged. Tag soon after merging.
  • The release must not be marked pre-release, or latest/download 404s.
  • Attestations need the repo to be public.
  • The first tag run is the real test of release.yml and the attestation flow.

- scripts/get.ps1: downloads the release ZIP, verifies SHA-256 and (when
  gh is signed in) the build attestation, then runs install.ps1
- release workflow: v* tags build, check, package, attest and publish
- pages workflow serves get.ps1 at /install.ps1
- docs, README, website and changelog updated

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@kiranscript
kiranscript merged commit b668204 into main Nov 17, 2026
1 check passed
@kiranscript
kiranscript deleted the website branch November 17, 2026 12:18
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