morozovsa/launcher-next
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat: verify last-known-good local packages

Browse Source
This commit is contained in:
codex
2026-08-05 09:17:21 +03:00
parent c66f0485dc
commit 2298fac8cd
4 changed files with 92 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/architecture/package-activation.md
+10
View File
@@ -3,3 +3,13 @@
Before changing package pointers, Launcher Next writes an activation snapshot containing exact previous `current.json` and `previous.json` contents and their SHA-256 values. Files are copied to a unique staging directory and rehashed. Only then is staging moved to `packages/<package>/versions/<version>` and the package-local pointer updated atomically.
Rollback restores the exact pointers, deletes the pilot version and startup script, and removes incomplete staging. Autodesk assemblies, PDBs, executables, test assemblies and legacy files are rejected from the pilot package.
## Last-known-good resolution
Each activated version retains its validated package manifest alongside its payload.
`LocalPackageStore.ResolveAsync` revalidates the manifest, package identity/product
compatibility, entry payload and every payload SHA-256 before returning a local
version. It returns current first. Only when current is invalid and the caller
explicitly permits offline fallback can it return previous. It never reads or
executes a package from DFS, and a failed or corrupted update never becomes
last-known-good.