feat: Command Line SDK 20.2.0-rc.1#312
Conversation
Greptile SummaryThis PR bumps the CLI SDK from
Confidence Score: 4/5Safe to merge — the signing pipeline is well-structured with explicit error checking, and all version strings are updated consistently. The core changes (version bump, install scripts, lockfile, formatting) are mechanical and low-risk. The new SignPath signing workflow is carefully implemented with
Important Files Changed
Reviews (1): Last reviewed commit: "chore: update Command Line SDK to 20.2.0..." | Re-trigger Greptile |
| @@ -15,7 +15,7 @@ | |||
| ] | |||
There was a problem hiding this comment.
Missing
hash fields for Scoop manifest entries
The Scoop manifest has no hash fields for either the 64-bit or arm64 download URLs. Without hashes, Scoop skips integrity verification and simply trusts HTTPS — a hash per architecture (e.g. "hash": "sha256:<hex>") lets Scoop catch a corrupted or substituted download before execution. Now that the binaries are code-signed via SignPath, computing and committing SHA-256 hashes for both appwrite-cli-win-x64.exe and appwrite-cli-win-arm64.exe would give Scoop users a second, independent integrity check.
This PR contains updates to the SDK for version 20.2.0-rc.1.
What's Changed
appwrite-cli-win-x64.exeandappwrite-cli-win-arm64.exe) via SignPathNotes
nextorrc) rather thanlatestso existingappwrite-cliusers aren't auto-upgraded.appwrite/specs:main/specs/1.9.x/swagger2-1.9.x-console.json(info.version1.9.3). No API surface change vs20.1.0.