Repository navigation
release: v1.0.22 -- inert trigger release for v1.0.21 dot-bg-fix smoke
DEPRECATED: this release is defective. Use v1.0.27 instead.
No release from v1.0.7 through v1.0.26 produces an installable Standard-mode ISO. This version crashes the Standard-mode build at 18% -- the autounattend binding references catalog item
tweak-compact-install, which was never added tocatalog.json; v1.0.8 turned that missing id from a silent default into a hard error.v1.0.27 reverts the image-shaping build pipeline to the proven v1.0.6 code -- verified end-to-end (clean build, clean install, Compact OS on, first-boot cleanup working) -- while keeping the post-v1.0.6 UI, logging, and failed-build cleanup. Existing installs auto-update via Velopack. Core-mode builds were unaffected.
No-op smoke-trigger release for v1.0.21 dot-bg fix. Zero behavior change vs v1.0.21. Sole purpose: be the "newer release" that a v1.0.21-installed launcher detects via the v1.0.13-added window.focus re-check, so the v1.0.21 belt-and-suspenders fix (cache-bust ?v= query string + ::before pseudo-element for the visible dot) can be smoked end-to-end. Expected on v1.0.21 badge surface: resting blue pulsing dot (both themes); hover dark = solid white dot + white wave fading outward (both unified, ring AND inner circle now actually swap color); hover light = solid #3a3a3a dot + #3a3a3a wave fading outward; tooltip "Update available, click to install..." steady (no scale inheritance).
Changed
launcher/tiny11options.Launcher.csproj—<Version>1.0.21</Version>→<Version>1.0.22</Version>.launcher/app.manifest—assemblyIdentity version="1.0.21.0"→"1.0.22.0".ui/index.html—style.css?v=1.0.21→style.css?v=1.0.22. Per the v1.0.21 lesson, the cache-bust query string must be bumped in lockstep with the launcher<Version>on every release so WebView2's HTTP cache fetches the freshstyle.cssrather than serving a stale copy from%LOCALAPPDATA%\tiny11options\webview2-userdata\cached against the samehttps://app.local/style.cssURL from a prior version.
No CSS, JS, resource, or test changes. Pester 516/0 + xUnit 140/0 both expected to match v1.0.21 ship.
Note
- v1.1.0 = Microsoft Trusted Signing (still queued, unchanged).