PackRelay Launcher v0.1.7

v0.1.7 — Honor server-pinned versions

Hotfix. v0.1.6 silently substituted the publisher's latest for any server-pinned version when the user clicked through ServerDetailView → InstallView. A server pinned to v0.2.0 with a player on local v0.3.0 would correctly say "Update to v0.2.0 & connect" on the server card — then install v0.4.0 (latest) instead and get the player kicked again.

This release threads the pin through end-to-end and adds a hard "thicc check" so a silent fallback to latest cannot happen.

What changed

• Pinned manifest fetch — new /api/v1/packs/<slug>/manifest/<version> route on the install/update path. The cloud already exposed it; the launcher just wasn't calling it.
• Pin survives the dock — ActiveInstall carries targetVersion, so jumping back to InstallView mid-download via the bottom-of-LeftRail dock no longer loses the pin context.
• Honest UI — InstallView's cover-version stamp, the vX → vY chip, and the primary-button label all key off the pinned version. No more "Update to v0.4.0" when the server pinned v0.2.0.
• Thicc check — three layers now refuse to install a mismatched version:
  • fetch_manifest_at asserts the returned manifest's version field equals the requested version. A cloud-side bug serving the wrong row errors loudly instead of downloading several GB of the wrong pack.
  • After install/update completes, the launcher asserts report.version === targetVersion. Mismatch produces a hard error instead of letting the player click "Connect" into an instant kick.
  • When a pinned version doesn't exist on the cloud, the error message is human-readable and tells the player the likely fix ("ask the server admin to refresh the pin").

Who this affects

Anyone playing on a server that pins to a specific pack version (servers.attachedVersion set on the cloud). If your servers all auto-track latest, v0.1.6's behavior was identical to v0.1.7's behavior for you.

Auto-update

v0.1.6 installs see the update toast on next launch.

Installation

Windows: SmartScreen flags this unsigned binary as an "unrecognized app" on first run. Click More info → Run anyway. Every binary on this release is built by GitHub Actions directly from the repo's source.

macOS: the .dmg is signed + notarized — open normally.