* Normalize newlines

* Fix tired mistakes

* Add changelog entry

* Update documentation

* Move changes to preview

* Fix test formatting

* Update schema

* Fix typo in CHANGES.md

Co-authored-by: Jelle Zijlstra <[email protected]>

* Fix typo in docs/the_black_code_style/future_style.md

Co-authored-by: Jelle Zijlstra <[email protected]>

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---------

Co-authored-by: Jelle Zijlstra <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

* Fix schema generation error caused by new click version
Not sure on the policy for updating versions, so to cope with the new click 8.3.0 version I used some code from psf#4577 for version conditional behavior. When >= 8.3.0, unset defaults are now the special UNSET sentinal instead of None.
Hopefully nothing breaks on the click._utils usage since it's an _ module, might have to find a different solution if it does.

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* Add ignore for mypy error

* Actually fix mypy errors with ignore

* Add explanation for ignores

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

* Prepare docs for release 25.9.0

* Remove unreleased changelog section

Git by default uses utf-8 file encodings, so these files will always be utf-8. On a windows system without PYTHONUTF8 set, these opens will fail (normal black doesn't have this issue because it detects file encodings automatically).

This PR makes it so that the opens always use utf-8 mode, so the script will always work on windows systems.

When making these previously I forgot to add the multiline flag that makes them work.

I prefer using (?m) instead of re.Multiline for flags, since when reading a regex it's a lot more obvious, being placed at the begining instead of the end.

When originally making the change, I assumed we were having a release in Feb, so I put the number as 25.2.0. Since that didn't happen, the number needs to be changed to 25.9.0.

* Improvements for release_process.md

While cutting 25.9.0, I ran into a few snags, so this PR smooths out the issues I ran into in the docs:

- Minor typo fix
- Since the stable branch is updated by the release workflow, `git diff origin/stable CHANGES.md` should always work, which is much easier than having to find a commit hash
- The example PR given had the new template already applied, which confused me. I eventually used the 25.1.0 pr as a template instead
- GitHub appears to now use the last commit message as the release message instead of the tag name, so it will need to be entered manually going forwards

* Update release_process.md

There is now a check to prevent any direct pushes to main, so a PR has to be made

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

After talking for a bit on the click discord, I was pointed to the `to_info_dict` function.

Since the functionality of `to_info_dict` was preserved between 8.2.0 and 8.3.0, using it makes the code much cleaner while having the same effect.

Theoretically, the entirety of the function could re-use `to_info_dict`, but there are two problems: No `is_eager` detection, and it's currently untyped besides `dict[str, Any]`, so I decided against it and just did the one improvement.