Repository navigation

v0.7.0: deployed — execute-skill shipped, stale binary PATH cleaned #17

	# Hand-authored (unlike release.yml, which is cargo-dist-generated and must not
	# be hand-edited). Exercises the real Windows rename-aside swap that the
	# `upgrade` fixture test performs — the-loop's own dev machines have no
	# Windows box, so this is the only place that leg runs.
	#
	# Pinned fact (design-time, cargo-dist 0.32.0): the PowerShell installer
	# performs no checksum verification at all (the-loop-installer.ps1) — only
	# the shell installer does. `upgrade` therefore verifies the downloaded
	# archive against its published .sha256 sidecar itself, before the Windows
	# rename-aside displaces anything, so the corrupt-archive case in
	# upgrade_fixture.rs asserts the same checksum refusal on both platforms.
	# Until that landed, a corrupt archive unpacked over the install path here and
	# the installer still reported success — this job is the only place that
	# regression can be caught.
	#
	# This job's greenness is a release-gate ready check (see the Release
	# runbook in docs/architecture.md), not a validate-time assertion — it only
	# runs at workflow_dispatch or on push to main, never on feature-branch
	# pushes or pull requests.
	name: upgrade-windows

	on:
	workflow_dispatch:
	push:
	branches:
	- main

	jobs:
	upgrade-fixture-windows:
	runs-on: windows-latest
	steps:
	- uses: actions/checkout@v6
	- uses: dtolnay/rust-toolchain@stable
	- run: cargo test --package the-loop --features upgrade --test upgrade_fixture