Update generated docs to 6.1.0 - #441
Merged
Merged
Conversation
Regenerated the command reference and the configuration table against Pester 6.1.0. Adds the New-ShouldAssertion page, which also clears the two broken links that #440 left behind. Picks up -NormalizeLineEnding on Should-BeString and Should-NotBeString, the Should-Throw wildcard hint, and in the configuration table Run.Shuffle, Run.ShuffleSeed, Output.ShowTags and Mock.Global. Drops the removed Run.BeforeContainer row. Generated with -DocusaurusVersion 1.0.37. Alt3.Docusaurus.PowerShell 2.0.0 is out now, and the unpinned script picks it up and then fails on a YamlDotNet assembly conflict with PlatyPS, so it needs pinning until #418 lands. 🤖
The v5 command reference and configuration section were still generated from 5.8.0. 5.9.1 changed no help text, so this is only the version stamp, but it keeps the versioned docs honest about which release they describe. 🤖
nohwnd
added a commit
to fflaten/docs
that referenced
this pull request
Aug 11, 2026
Most conflicts were generated command pages. Main regenerated them for 6.1.0 in pester#441 with the old generator while this branch has them from the v2 generator at the same version, so resolved by keeping this branch and dropping the old-generator output. Two real resolutions: - versioned_docs/version-v5/usage/configuration.mdx, that section is generated separately and was still on 5.9.0 here, took 5.9.1 from main. - versioned_sidebars/version-v4-sidebars.json, main restructured the whole v4 sidebar while this branch only changed one id in the old structure. Kept main structure and re-applied the id, commands/Add-ShouldOperator, to match the docId the v2 generator writes for Add-AssertionOperator. Without it the build fails with "Invalid sidebar file". Verified: yarn build passes. 🤖
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Regenerated the command reference and the configuration table against Pester 6.1.0, the follow-up to #440 that we kept separate until the release was out.
New-ShouldAssertionpage. That also clears the two broken links Document 6.1.0 features and drop removed Run.BeforeContainer #440 knowingly left behind,yarn buildnow reports none.-NormalizeLineEndingonShould-BeStringandShould-NotBeString, and theShould-Throwwildcard hint.Run.Shuffle,Run.ShuffleSeed,Output.ShowTagsandMock.Global, and drops the removedRun.BeforeContainerrow.Two things worth knowing:
The generator needs a pinned Alt3 version.
Alt3.Docusaurus.PowerShell2.0.0 is out, andgenerate-command-reference.ps1asks for the latest stable, so it installs 2.0.0 and then dies on aYamlDotNetassembly conflict with PlatyPS. Worse, it deletes the existing MDX files before it fails, so the failure is not a no-op. I generated with-DocusaurusVersion 1.0.37. Until #418 lands it is probably worth defaulting the script to the 1.0.x line rather than latest.Run.Parallelstill describes a stale fallback. Its description says it falls back to sequential "when CodeCoverage is enabled", which stopped being true in pester/Pester#2860. The text comes fromRunConfiguration.csin the Pester repo, so it cannot be fixed here, it needs a fix there and then another regen. I left the generated output faithful to the module.Verified with
yarn build.🤖