proto: Add version 0.52.5#16157
Conversation
WalkthroughAdds a new Scoop manifest Changes
Sequence Diagram(s)sequenceDiagram
participant Scoop
participant Manifest as bucket/proto.json
participant Download
participant Extract
participant Env
note right of Manifest `#F0F8FF`: New manifest for Proto v0.52.5 (win64)
Scoop->>Manifest: read manifest (version, urls, shas, bins)
Scoop->>Download: fetch archive at templated URL
Download->>Scoop: archive + .sha256
Scoop->>Extract: extract files (includes proto.exe, proto-shim.exe)
Extract->>Env: set PROTO\_HOME = persist_dir
Extract->>Env: add persist_dir to PATH
note right of Scoop: checkver queries GitHub releases\nautoupdate uses version-templated URL + sha source
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
All changes look good. Wait for review from human collaborators. proto
|
There was a problem hiding this comment.
Actionable comments posted: 2
🧹 Nitpick comments (1)
bucket/proto.json (1)
19-21: Minor: simplify checkver syntax.Short form is conventional in Scoop manifests.
Apply this diff:
- "checkver": { - "github": "https://github.com/moonrepo/proto" - }, + "checkver": { + "github": "moonrepo/proto" + },
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
bucket/proto.json(1 hunks)
🔇 Additional comments (2)
bucket/proto.json (2)
22-31: Keep per-asset .sha256 — no change required.
Releases include per‑asset .sha256 files for the Windows zips (and also a consolidated dist-manifest.json), so the current hash URL ($baseurl/proto_cli-x86_64-pc-windows-msvc.zip.sha256) is valid — leave as-is.
6-11: Optional: add Windows ARM64 if upstream ships it — not applicable for v0.52.5The v0.52.5 release only includes proto_cli-x86_64-pc-windows-msvc.zip; there is no aarch64-pc-windows-msvc asset, so do not add an arm64 block.
…tive install script.
|
|
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
bucket/proto.json (4)
16-25: Simplify installer; prefer Scoop “bin” shims instead of moving EXEs.Current flow moves EXEs into $persist_dir and relies on PATH. Scoop can create shims and avoid PATH edits and custom moves.
Option A — keep persisted bin but make PATH explicit (see next comment).
Option B — simpler, shim-based install (recommended):
"installer": { - "script": [ - "# Create bin directory", - "New-Item -ItemType Directory -Force -Path \"$persist_dir\\bin\" | Out-Null", - "", - "# Move proto binaries into bin", - "Move-Item \"$dir\\proto.exe\" \"$persist_dir\\bin\\proto.exe\" -Force", - "if (Test-Path \"$dir\\proto-shim.exe\") {", - " Move-Item \"$dir\\proto-shim.exe\" \"$persist_dir\\bin\\proto-shim.exe\" -Force", - "}", - ] + "script": [] }, + "bin": [ + "proto.exe", + "proto-shim.exe" + ], - "persist": [ - "bin" - ], + "persist": [],PROTO_HOME can remain set to $persist_dir to keep toolchains/config persistent.
27-31: Make PATH target unambiguous; point directly at the persisted bin.If you keep the current “move-to-persist” approach, ensure PATH targets the persisted location to avoid any ordering/symlink surprises.
- "env_add_path": "bin", + "env_add_path": "$persist_dir\\bin",
12-14: Persist entry may be redundant with the current installer.Since you’re moving binaries to $persist_dir\bin manually, persisting "bin" is not needed unless you also want a $dir\bin junction. Consider removing it, or keep it only if you rely on the junction.
40-42: Harden autoupdate hash retrieval.Point hash to $url.sha256 (tied to the exact asset) and add a regex in case the file includes filenames or prefixes.
- "hash": { - "url": "$baseurl/proto_cli-x86_64-pc-windows-msvc.zip.sha256" - } + "hash": { + "url": "$url.sha256", + "regex": "([A-Fa-f0-9]{64})" + }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
bucket/proto.json(1 hunks)
🔇 Additional comments (3)
bucket/proto.json (3)
1-5: Metadata looks good.Version, description, homepage, and license are aligned with upstream.
8-9: SHA-256 verified — matches upstream.
Upstream .sha256 equals the manifest hash in bucket/proto.json (lines 8–9).
6-11: Do not add Windows ARM64 for v0.52.5 — asset not published.
v0.52.5 only contains proto_cli-x86_64-pc-windows-msvc.zip; there is no proto_cli-aarch64-pc-windows-msvc.zip or SHA‑256 to add.
|
Close #16990 |
Proto: Add version 0.52.5
Close #16990
<manifest-name[@version]|chore>: <general summary of the pull request>Summary by CodeRabbit