Draft: GeneralUpdate.Core documentation#56
Conversation
|
Expanded the Core draft into an API-focused component reference: bootstrap methods, UpdateRequest/Builder properties, options, events, lifecycle hooks, reporting, auth/SSL, download source/policy/executor/pipeline/orchestrator, strategy extension, silent update options, and Tools relationship. Docusaurus build passed with |
|
Added a detailed Core manifest section covering generalupdate.manifest.json: its purpose, generated schema, GeneralUpdate.Tools generation flow, Core loading APIs (ManifestInfo, AppMetadataDiscoverer), recommended configuration pattern, and version write-back behavior. The zh-Hans and en docs were updated and the Docusaurus build passes. |
1 similar comment
|
Added a detailed Core manifest section covering generalupdate.manifest.json: its purpose, generated schema, GeneralUpdate.Tools generation flow, Core loading APIs (ManifestInfo, AppMetadataDiscoverer), recommended configuration pattern, and version write-back behavior. The zh-Hans and en docs were updated and the Docusaurus build passes. |
|
Added hook guidance for Linux/macOS permission scenarios: the Hooks section now explains using IUpdateHooks as an open extension point for chmod +x, permission repair, signature/authorization scripts, with examples for UnixPermissionHooks and a custom script adapter. |
1 similar comment
|
Added hook guidance for Linux/macOS permission scenarios: the Hooks section now explains using IUpdateHooks as an open extension point for chmod +x, permission repair, signature/authorization scripts, with examples for UnixPermissionHooks and a custom script adapter. |
|
Removed the remaining driver-related DriverDirectory references from the GeneralUpdate.Core documentation so the Core page no longer implies driver update support. Disk-space DriveInfo code remains because it is only a precheck example, not driver functionality. |
1 similar comment
|
Removed the remaining driver-related DriverDirectory references from the GeneralUpdate.Core documentation so the Core page no longer implies driver update support. Disk-space DriveInfo code remains because it is only a precheck example, not driver functionality. |
|
Clarified the manifest version write-back section: generalupdate.manifest.json now explains that Core treats the manifest as the local version state file and automatically updates ClientVersion / UpgradeClientVersion after successful updates, so developers do not need to write application code to maintain local version numbers. |
1 similar comment
|
Clarified the manifest version write-back section: generalupdate.manifest.json now explains that Core treats the manifest as the local version state file and automatically updates ClientVersion / UpgradeClientVersion after successful updates, so developers do not need to write application code to maintain local version numbers. |
|
Updated the draft Core documentation with the latest component-level details:
Validation: Docusaurus build passes for zh-Hans and en. |
|
Updated the event callback section to clarify
|
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
f6dc5f1 to
2147892
Compare
There was a problem hiding this comment.
Pull request overview
This PR drafts a new, significantly expanded documentation page for GeneralUpdate.Core and syncs that content across the base docs plus English and Chinese i18n copies, aligning the page with the “non-firmware component docs” plan (Core as the first component page).
Changes:
- Rewrites the
GeneralUpdate.Corepage structure with a topic map, strategy overview (standard/OSS/silent), and a deeper API/extension-point walkthrough. - Adds detailed sections for
UpdateRequest,generalupdate.manifest.json, events, logging controls, differential pipeline concepts, and tooling relationship. - Updates both
website/i18n/en/...andwebsite/i18n/zh-Hans/...copies to mirror the new base content.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 9 comments.
| File | Description |
|---|---|
| website/docs/doc/GeneralUpdate.Core.md | New Core component draft: strategies, configuration, diff pipeline, events, and extension points. |
| website/i18n/en/docusaurus-plugin-content-docs/current/doc/GeneralUpdate.Core.md | English i18n draft synced to the new Core page content. |
| website/i18n/zh-Hans/docusaurus-plugin-content-docs/current/doc/GeneralUpdate.Core.md | Chinese i18n draft synced to the new Core page content. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| .WithStopOnFirstError(true) | ||
| .WithProgress(new Progress<DiffProgress>(p => | ||
| { | ||
| Console.WriteLine($"{p.Completed}/{p.Total}: {p.FileName}"); |
| - [Upgrade sample](https://github.com/GeneralLibrary/GeneralUpdate-Samples/blob/main/src/Upgrade/Program.cs) | ||
| - [OSS upgrade sample](https://github.com/GeneralLibrary/GeneralUpdate-Samples/tree/main/src/OSS/OSSUpgradeSample) |
|
|
||
| Core 主要消费 Dirty 阶段;差分包生成建议交给 `GeneralUpdate.Tools` 或发布流水线完成。标准更新中,下载完成后升级程序会先解压包,再在 `PatchEnabled = true` 时通过 `PatchMiddleware` 调用 `DiffPipeline.DirtyAsync(...)` 应用补丁。 |
| .WithStopOnFirstError(true) | ||
| .WithProgress(new Progress<DiffProgress>(p => | ||
| { | ||
| Console.WriteLine($"{p.Completed}/{p.Total}: {p.FileName}"); |
| - [Upgrade sample](https://github.com/GeneralLibrary/GeneralUpdate-Samples/blob/main/src/Upgrade/Program.cs) | ||
| - [OSS upgrade sample](https://github.com/GeneralLibrary/GeneralUpdate-Samples/tree/main/src/OSS/OSSUpgradeSample) |
|
|
||
| Core mainly consumes the Dirty phase; patch generation should normally be handled by `GeneralUpdate.Tools` or your release pipeline. In standard update, after downloads finish, the updater extracts packages and calls `DiffPipeline.DirtyAsync(...)` through `PatchMiddleware` when `PatchEnabled = true`. |
| .WithStopOnFirstError(true) | ||
| .WithProgress(new Progress<DiffProgress>(p => | ||
| { | ||
| Console.WriteLine($"{p.Completed}/{p.Total}: {p.FileName}"); |
| - [Upgrade sample](https://github.com/GeneralLibrary/GeneralUpdate-Samples/blob/main/src/Upgrade/Program.cs) | ||
| - [OSS upgrade sample](https://github.com/GeneralLibrary/GeneralUpdate-Samples/tree/main/src/OSS/OSSUpgradeSample) |
|
|
||
| Core 主要消费 Dirty 阶段;差分包生成建议交给 `GeneralUpdate.Tools` 或发布流水线完成。标准更新中,下载完成后升级程序会先解压包,再在 `PatchEnabled = true` 时通过 `PatchMiddleware` 调用 `DiffPipeline.DirtyAsync(...)` 应用补丁。 |
Summary
Draft documentation for
GeneralUpdate.Coreas the first component page in the non-firmware documentation plan.Scope
GeneralUpdateBootstrap, runtime roles, main updater samples, options, events, silent update, extension points, Tools relationship, and troubleshooting.Related issues
Validation
git diff --check