release(nesdoctor): point the installers at v0.3.0

Flipped after publishing, so there was never a window where the live installer
named a tag that did not exist.

Verified before committing: all five assets under the new tag return 200, and
the installer was run end to end — it fetched the published binary, checked it
against SHA256SUMS, and the thing it ran reported 0.3.0.
This commit is contained in:
Wanjohi
2026-09-03 22:40:26 +03:00
parent 29a826d9f9
commit d8e5c19181
2 changed files with 2 additions and 2 deletions

View File

@@ -24,7 +24,7 @@ $Repo = 'nestrilabs/nestri'
# product release goes out it would move again and every install here would
# 404. Bump this line when cutting a nesdoctor release; NESDOCTOR_TAG overrides
# it for testing.
$DefaultTag = 'nesdoctor-v0.2.2'
$DefaultTag = 'nesdoctor-v0.3.0'
$Tag = if ($env:NESDOCTOR_TAG) { $env:NESDOCTOR_TAG } else { $DefaultTag }
# TLS 1.2 explicitly: Windows PowerShell 5.1 still defaults to older protocols

View File

@@ -23,7 +23,7 @@ REPO="nestrilabs/nestri"
# product release goes out it would move again and every install here would
# 404. Bump this line when cutting a nesdoctor release; `NESDOCTOR_TAG`
# overrides it for testing.
DEFAULT_TAG="nesdoctor-v0.2.2"
DEFAULT_TAG="nesdoctor-v0.3.0"
TAG="${NESDOCTOR_TAG:-$DEFAULT_TAG}"
TMP="$(mktemp -d)"
trap 'rm -rf "$TMP"' EXIT INT TERM