deno_install

Summary Both and always print this line at the end of a successful install: There is currently no way to suppress it. Motivation Some downstream projects invoke the official installer programmatically (e.g. during their own bootstrap/init flow) and want clean, product-branded output without third-party community links. Concrete example: fount depends on Deno but is, in a sense, a competing chat/community platform. Showing a Discord invite during fount's first-run install is confusing at best and unwelcome for users who deliberately avoid Discord. This is not about removing Discord support from Deno itself — only about making the installer script output configurable, similar to the existing flag in . Proposed behavior Add an opt-out, for example: Shell (): PowerShell (): Or a single env var honored by both scripts, e.g. , if you prefer fewer flags. When set, skip the final Discord line; keep the useful lines (, ). Context already documents flags like and / . has no equivalent flags today; an env var may be the least invasive addition there. Thanks for considering this.

Summary Makes the official Deno installers select the native Windows ARM64 build. Previously both and hardcoded , so a Windows ARM64 machine downloaded the x64 binary and ran it under emulation. This is §2 of denoland/deno#36045, and closes #347. After installing on Windows ARM64, now reports . Changes Native architecture detection : calls and uses its native-machine result — robust even when x64 PowerShell (including Windows PowerShell 5.1 on .NET Framework) runs under emulation. is a guarded fallback for hosts where the P/Invoke is unavailable. (MSYS/Git-Bash path): reads (set to the native arch under WOW64 emulation) falling back to . Native ARM64 → , native AMD64 → . x64 Windows behavior is unchanged. Version guard Native Windows ARM64 artifacts are first published in v2.6.8. Requesting an older version on ARM64 now fails with a clear error rather than silently installing the emulated x64 build. Checksum verification () Downloads and verifies before extraction, removing temp files on any failure. The parser accepts both canonical and legacy PowerShell checksum files. Verification is fatal on ARM64 (a checksum is always expected there); on x64 it is applied when a checksum is present, so pre-2.6.7 releases that predate published checksums still install. CI New job on runs : 1. Native ARM64 install (latest) asserts . 2. A pinned ARM64-capable version () installs native. 3. A pre-2.6.8 request () is rejected. 4. An emulated x86 PowerShell (SysWOW64) install still selects the native ARM64 build — exercising the path (skipped if that host is absent on the image). Legacy v1.x installs remain on the x64 runner because those releases have no ARM64 artifacts. Verified locally , , , , and all pass. was regenerated for the updated scripts. Not in this PR checksum verification for all platforms (Linux/macOS have none today) — separate concern. Publishing a new tag and updating the redirect — release infra, tracked in #36045.

Replaces: #302 #321 #326 #333 Fixes: fix #172 fix #266 fix #322 fix #325 Closes: close #260