Branding to 6.2.0

[nohwnd]

Prerelease is empty and ReleaseNotes points at the 6.2.0 tag, so the manifest that gets packaged says 6.2.0 and not 6.2.0-alpha2.

docs/NEXT-RELEASE.md gets its last pass: the title, the prerelease install line, and the compare link. Nothing user facing merged since the alpha2 notes pass in pester/Pester#3037 — Write the 6.2.0-alpha2 release notes pass. The two that came after it, pester/Pester#3039 — Skip the build and the test matrix on a documentation-only pull request and pester/Pester#3040 — Reset the exit code when the test harness finishes a passing run, touch the CI lane and test.ps1, so there is nothing new to write up.

The examples

I built this branch and ran every example in the notes against it, and compared the output to what the notes claim.

The Should-BeString diffs (both of them), the three stack trace failures, the BeforeAll that throws, the three strict configuration errors, the unknown key warning and the timing assertion message all print exactly what the notes say. The folder cascade repro passes: root, tests, tests/unit, tests/integration, and a tests/docs marked #pester:no-inherit, and the docs file gets only its own setup.

One example was wrong. The block showing which setup files applied to a container was a rendering of the data with no code that produces it, so a reader had no way to get to it. The list is BeforeContainerFile on the container in the result object, and the notes now show the loop that prints it, next to the output that loop actually produced:

$result = Invoke-Pester -Path ./tests -PassThru
foreach ($container in $result.Containers) {
    "$($container.Item.Name):"
    $container.BeforeContainerFile | ForEach-Object { "    $_" }
}

Two things the notes did not say and now do. A block can have more than one BeforeAll, which was only a bullet in the behavior changes at the bottom, and it is a feature people asked for, so it is in the summary paragraph too. And the setup files run before every container, so what they do has to be safe to run more than once. That one is in the Run.RepoRoot help text and was nowhere in the notes.

Order

Publishing the draft release is what creates the tag, so this has to be merged before that happens, otherwise the tagged commit still carries Prerelease = 'alpha2' and that manifest is what ships to the gallery.

docs/NEXT-RELEASE.md is emptied for the 6.3.0 line after the release is out, in its own PR, not here. The notes have to stay in the file until they are copied into the release body.

🤖