Release 8.3.0

[Rowlando13]

Pallets release steps

• 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 upstream 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!

[Rowlando13]

@davidism @kdeldycke Is there anything else that needs to be resolved before I start prepping the release?

[kdeldycke]

@davidism @kdeldycke Is there anything else that needs to be resolved before I start prepping the release?

I'm good with the current state of main on my side. I'm depending on it for my upcoming release of Click Extra and haven't found any issue.

I think it is time to release it before it becomes too big.

[davidism]

Seems good to me 👍

[davidism]

#2940 should probably go in