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

v0.1.1 is published, so the pin moves. Flipped after publishing rather than
with the version bump, so there was never a moment where the live installer
pointed at a tag that did not exist yet.

v0.1.0's added-latency grade cannot be trusted -- it measured bloat against a
median that goes unstable on a bimodally routed link -- so nothing should be
installing it.
This commit is contained in:
Wanjohi
2026-09-02 13:39:45 +03:00
parent f0e65b9738
commit d6c5eafe9e
2 changed files with 2 additions and 2 deletions

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.1.0"
DEFAULT_TAG="nesdoctor-v0.1.1"
TAG="${NESDOCTOR_TAG:-$DEFAULT_TAG}"
TMP="$(mktemp -d)"
trap 'rm -rf "$TMP"' EXIT INT TERM