Skip to content

Release notes and branding for 6.2.1 - #3046

Open
nohwnd wants to merge 2 commits into
mainfrom
nohwnd-release-621
Open

nohwnd wants to merge 2 commits into
mainfrom
nohwnd-release-621

Conversation

@nohwnd

@nohwnd nohwnd commented Sep 24, 2026 •

Copy link
Copy Markdown
Member

6.2.1 carries one change, pester/Pester#3045 - Make a parallel run print what a sequential run prints, so the notes are short and there is no table of contents. The 6.2.0 notes are replaced rather than emptied first, the anchor prefix is 6.2.1-.

The manifest says 6.2.1 and ReleaseNotes points at the 6.2.1 tag. Prerelease was already empty, there is no prerelease cycle for a patch this size.

Merge this after pester/Pester#3045, then publish the draft release to create the tag.

pester/Pester#3043 - Empty docs/NEXT-RELEASE.md for the 6.3.0 line still applies, it just belongs after 6.2.1 ships instead of before, and it will need a rebase because this PR rewrites the same file.

🤖

One fix, so the notes are short and there is no table of contents. The manifest
says 6.2.1 and `ReleaseNotes` points at the 6.2.1 tag, `Prerelease` was already
empty.

Merge this after #3045, it is the only change 6.2.1 carries.

🤖
#3045 grew a second commit, the workers now take the caller's preference
variables as well. The notes said only that the duplicate warnings were gone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant