You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Done, in tests/Build-PSBuildHelp.tests.ps1. Closing late for the same reason as #99: this should
have closed with #151 in #173, and the map said it would, but that pull request's description named
only the parent issues.
Asked for
Covered by
MAML generated from markdown source
writes the MAML help file into a locale directory under the destination, produces MAML describing the exported commands
Depends on the shared fixture module
the context builds markdown from PSBuildTestFixture first, then converts it
The MAML context deliberately runs the markdown step first rather than using checked-in fixture
markdown, so it exercises the real hand-off between the two functions — which is where the PlatyPS
1.x schema change would have broken it.
As with #99, "Requires platyPS" now means Microsoft.PowerShell.PlatyPS 1.x, which is no longer a
required module.
Activity
fix: Make the script analysis severity threshold fail the build (#143)
tablackburn commentedon Aug 27, 2026
Done, in
tests/Build-PSBuildHelp.tests.ps1. Closing late for the same reason as #99: this shouldhave closed with #151 in #173, and the map said it would, but that pull request's description named
only the parent issues.
writes the MAML help file into a locale directory under the destination,produces MAML describing the exported commandsPSBuildTestFixturefirst, then converts itThe MAML context deliberately runs the markdown step first rather than using checked-in fixture
markdown, so it exercises the real hand-off between the two functions — which is where the PlatyPS
1.x schema change would have broken it.
As with #99, "Requires platyPS" now means
Microsoft.PowerShell.PlatyPS1.x, which is no longer arequired module.