dotnet format makes no changes, but --check reports encoding issues

After upgrading to the latest release of this package, version 3.2.107702, when I ran dotnet format for the first time it modified the encoding of some files. After that, running dotnet format makes no changes, but when I run dotnet format --check --dry-run it returns a non zero exit code and prints and message about the encoding of almost every file in my project.

MyProject/Whatever.cs(1,1): Fix file encoding.

When I run with or without the check flags, it prints a message saying it formatted every file in my project, which is also new, but nothing has changed, at least that git can detect.

Formatted code file 'Whatever.cs'.

I am using the editorconfig option charset = utf-8, and have observed this issue on MacOS and linux.

[JoeRobich]

@schmitch I just published 3.3.111304 to NuGet. Thanks for using dotnet-format!

[schmitch]

@JoeRobich will there be a new 3.2 release soon? I accidently installed the latest dotnet-format on our ci servers and needed to downgrade the tool afterwards since we use dotnet-format --check their, which failed because of this.