Part of #120 (Phase 2 — PlatyPS migration, #105). Blocked by the MAML migration — the cab pipeline consumes MAML.
Scope
Migrate PowerShellBuild/Public/Build-PSBuildUpdatableHelp.ps1 from New-ExternalHelpCab to the Microsoft.PowerShell.PlatyPS 1.x cab pipeline.
Closes #101 (Build-PSBuildUpdatableHelp tests, Windows-only) — written against the new API.
Watch for
This is the highest-risk link in the chain. Cab generation is Windows-only, depends on makecab.exe, and is the least-exercised of the three functions — it has no test coverage today and the least community usage, so breakage here is most likely to reach 1.0.0 undetected. If the 1.x cab story turns out to be materially different from 0.14.x (or absent), say so on this issue rather than working around it: dropping or reshaping updatable-help support is a scope decision for #120, not a call to make inside the PR.
Done when
Build-PSBuildUpdatableHelp uses only 1.x cmdlets, #101's Windows-only tests cover it, a cab is produced and verified, and any behavior change has a migration-guide entry.
Part of #120 (Phase 2 — PlatyPS migration, #105). Blocked by the MAML migration — the cab pipeline consumes MAML.
Scope
Migrate
PowerShellBuild/Public/Build-PSBuildUpdatableHelp.ps1fromNew-ExternalHelpCabto theMicrosoft.PowerShell.PlatyPS1.x cab pipeline.Closes #101 (
Build-PSBuildUpdatableHelptests, Windows-only) — written against the new API.Watch for
This is the highest-risk link in the chain. Cab generation is Windows-only, depends on
makecab.exe, and is the least-exercised of the three functions — it has no test coverage today and the least community usage, so breakage here is most likely to reach 1.0.0 undetected. If the 1.x cab story turns out to be materially different from 0.14.x (or absent), say so on this issue rather than working around it: dropping or reshaping updatable-help support is a scope decision for #120, not a call to make inside the PR.Done when
Build-PSBuildUpdatableHelpuses only 1.x cmdlets, #101's Windows-only tests cover it, a cab is produced and verified, and any behavior change has a migration-guide entry.