changed.velopack,试试rust

This commit is contained in:
lincube
2026-04-19 12:36:14 +08:00
parent 4f9feafbbe
commit 8e21364eed
16 changed files with 615 additions and 309 deletions

View File

@@ -0,0 +1,7 @@
# Checklist
- [x] `releases.win.json` recognized by host update download flow.
- [x] Launcher pending update check supports VeloPack payload.
- [x] Launcher apply uses deployment markers (`.current/.partial/.destroy`) unchanged.
- [x] Legacy script path retained as emergency fallback.
- [ ] Staging verification report attached.

View File

@@ -0,0 +1,16 @@
# VeloPack Update Integration
## Goal
Switch incremental package generation and release assets to VeloPack native outputs while keeping Launcher as the update installer and rollback authority.
## Requirements
- CI/release pipeline produces `releases.win.json` and `*.nupkg` assets for Windows x64.
- Launcher can detect pending VeloPack payload in `.launcher/update/incoming`.
- Launcher applies update into new `app-*` deployment and preserves rollback snapshot behavior.
- Existing launcher responsibilities (OOBE/startup/plugin upgrade) remain unchanged.
## Acceptance
- Build and quality workflows pass after migration changes.
- Release workflow publishes VeloPack assets.
- Launcher `update apply` succeeds with VeloPack full package payload.
- Manual rollback still works after a VeloPack-based update.

View File

@@ -0,0 +1,9 @@
# Tasks
- [x] Fix Launcher `LoadingDetailsWindow.axaml` compile regression.
- [x] Add VeloPack feed/package model support in Launcher update engine.
- [x] Keep legacy delta flow behind disabled fallback switch.
- [x] Migrate release workflow packaging assets to VeloPack outputs.
- [x] Update host-side update workflow to download VeloPack payload files.
- [ ] Run full release workflow dry-run on GitHub and validate artifacts.
- [ ] Validate end-to-end update + rollback on a staging machine.