release version 8.2.0

[AndreasBackx]

• Decide to make a release.
• Ensure the change log has entries for each user-facing non-docs change, with links to the related issue reports.
• Ensure each issue and PR is in the milestone.
• Create a release-A.B.C branch.
• Change "Unreleased" to "Released YYYY-MM-DD" in CHANGES.md.
• Remove the ".dev" suffix from the version in pyproject.toml.
• Commit git commit -am 'release version A.B.C' and create a PR.
• Tag git tag -am 'release version A.B.C' A.B.C and push git push origin A.B.C.
• Watch the tests pass and build jobs begin.
• Edit the generated draft release page with our standard message template.
• Approve the upload job.
• Merge the PR. Use "create a merge commit", not "squash" or "rebase"!
• Close the milestone.
• Publish the draft release page.
• Start the next version(s), creating a change log section, bumping the version in pyproject.toml with the .dev suffix.
• Done!

Resolves #2789.

[MeggyCal]

Hi, I tested the 8.2.0 tag in my project and tests in many other packages fail with TypeError: CliRunner.__init__() got an unexpected keyword argument 'mix_stderr' (for instance black or Flask). Just so you are aware of it. Is there any recommended fix/workaround for this issue?

[MeggyCal]

Hi, I tested the 8.2.0 tag in my project and tests in many other packages fail with TypeError: CliRunner.__init__() got an unexpected keyword argument 'mix_stderr' (for instance black or Flask). Just so you are aware of it. Is there any recommended fix/workaround for this issue?

Sorry, now I noticed:

Keep stdout and stderr streams independent in CliRunner. Always collect stderr output and never raise an exception. Add a new output stream to simulate what the user sees in its terminal. Removes the mix_stderr parameter in CliRunner.

Everything is clear now, thank you.

[Rowlando13]

@AndreasBackx Is this where you stopped?

[AndreasBackx]

@Rowlando13 yes, though there needs to be some decision on #2832.

[Rowlando13]

@davidism Could you review this when you get a chance? I can do the administrative stuff after the merge the PR step.

[kdeldycke]

Merge of stable into main has reveled a lots of conflicts, which I fixed in #2873. From there 8.2.0 can be released.

[kdeldycke]

This PR can be closed, and the release-8.2.0 branch removed, now that everything has been reconciled in main thanks to #2873.