fix: Installed CLI now self-updates to a dispatcher release with V2 project support

Merged
HA
3mo ago
+6-6

Summary

  • Raise the dispatcher minimum version pin from 3.0.1-beta.6 to 3.1.0-beta.16 so installed CLIs self-update to a release that understands V2 Unity projects.

User Impact

  • Before: the pin floor had been stuck at 3.0.1-beta.6 since #1794, and dispatchers never self-update above the floor. Every project therefore kept running a dispatcher that predates all V2 project support — V2 delegation (#1807), the V2 launch hang fix (#1826), and detection of V2 projects referenced via file:/embedded packages (#1847).
  • After: once a project picks up this pin, an installed 3.0.1-beta.6 dispatcher detects it is below the floor and force-updates to 3.1.0-beta.16, which includes the full V2 handling above.

Changes

  • Packages/src/project-runner-pin.json: minimumDispatcherVersion raised by hand (the only manually maintained minimum declaration); dispatcherReleaseTag and dispatcherArchiveManifest stamped by stamp-dispatcher-pin, which verifies the release's sigstore attestation before recording the asset digests.
  • .uloop/project-runner-pin.json: byte-identical mirror of the package pin.

Verification

  • go run ./cmd/check-dispatcher-pin --network — passed (manifest matches the attested release assets)
  • go run ./cmd/check-dispatcher-minimum-version — passed (pins consistent, release tag exists)
  • go run ./cmd/check-release-triggers --base origin/v3-beta --head HEAD — passed