From d2ab740aced55c4b95d599d60d9fa60f9dfc2c76 Mon Sep 17 00:00:00 2001 From: Dandaedre Date: Fri, 20 Nov 2026 08:41:48 +0100 Subject: [PATCH] Define software release update command --- TASKS.md | 1 + docs/manifest-contract.md | 16 ++++++++++++++++ 2 files changed, 17 insertions(+) diff --git a/TASKS.md b/TASKS.md index 57ac554..ae10992 100644 --- a/TASKS.md +++ b/TASKS.md @@ -157,3 +157,4 @@ open until it is run on disposable machines with the required account setups. - [x] Implement portable ZIP planning, verified staging, launchers and recovery with Linux Pester tests; keep Windows acceptance below open. - [x] Add the verified PDF Presenter 0.1.33 release to the desktop profile and document updates; validate archive/executable hashes and run the Linux suite (136 passed, 5 Windows-only skips). - [ ] Validate portable installation, Start menu launch and running-app handling on disposable Windows x64. +- [ ] Add `update-software` with checksum-verified Gitea release discovery and package-only execution. diff --git a/docs/manifest-contract.md b/docs/manifest-contract.md index 73f1ddc..480f005 100644 --- a/docs/manifest-contract.md +++ b/docs/manifest-contract.md @@ -45,6 +45,7 @@ cc doctor [-Machine NAME] cc plan [-Machine NAME] [-ConfigsOnly] [-Json] cc apply [-Machine NAME] [-ConfigsOnly] [-ForceConfigs] [-Json] cc sync [-Machine NAME] [-ConfigsOnly] [-ForceConfigs] [-Json] +cc update-software [-Machine NAME] [-Json] cc status [-Machine NAME] [-Json] cc restore -Config NAME [-Machine NAME] [-Json] cc schedule [-Machine NAME] @@ -56,6 +57,10 @@ cc menu [-Machine NAME] current checkout. `sync` fetches its configured remote and runs from a staged snapshot of the resolved commit. Config conflicts require `-ForceConfigs`, which always makes a backup first. Removing a manifest entry merely stops management. +`update-software` uses the current checkout, skips every config, applies normal +WinGet policies, and resolves opted-in portable packages from their release API +before planning and installing them. A release lookup failure is an item failure +and does not prevent independent package operations. `schedule` registers a limited, interactive-user task at logon. Scheduled runs always use `sync -ConfigsOnly`; package installation and upgrades remain manual @@ -103,3 +108,14 @@ To update, review a release, verify its archive against the publisher's checksum and commit its version, exact URL, SHA-256 and executable path together. The next full sync applies that version. Pinning a preview release is explicit consent to that release, not permission to follow future prereleases automatically. + +Portable packages can opt into release discovery for `update-software` with +`releaseApi`, `releaseChannel`, `assetTemplate`, `executableTemplate`, and an +optional `checksumAsset` (default `SHA256SUMS`). The API must be an HTTPS Gitea +releases endpoint. Templates contain one `{version}` placeholder and no path +separators in the asset template. Channels are `stable` or `prerelease`; +`prerelease` follows preview and stable releases, while `stable` ignores previews. +Draft releases, malformed version tags, ambiguous assets, missing or ambiguous +checksum entries, cross-host download URLs, and versions older than the manifest +pin are rejected. Resolution produces exact URL, checksum, and executable values +in memory and never edits the repository manifest.