I suppose there is also could be point like "produce correct semver-value for generated config" and should be decided what it should be - exact strict with =, or range or just ^.

My preferred path would be, if 1.34 is on the required_version, should return true to any version above 1.35, as this is the default behavior for rust-version, as described on The Cargo Book

rust-version — The minimal supported Rust version.

But as currently the required_version key compares equality (any different version, above or below will throw error), we can keep as it is for plain version, but allow different comparison strings, e.g.: as 1.34 breaks for 1.35, but ^1.34/>=1.34/>1.34 not.

produce correct semver-value for generated config

Agree totally, but not sure how this would differentiate from typing --version and copy/paste it, and not sure if this should be done in this issue. I didn't find any kind of init command (something like cargo fmt init) to generate the config file, but if we have so, then by default this could add the required version.
One possibility to it'd generate a ><current_version> <<next_major>, so user can use any minor/patch above the current version, but can't use a major version above

I didn't find any kind of init command (something like cargo fmt init) to generate the config file, but if we have so, then by default this could add the required version.

@ologbonowiwi you can run rustfmt --print-config default, and rustfmt will write a default toml file to stdout.

and not sure if this should be done in this issue.

Agreed. Deciding that can likely wait till later.

#6066 addressing it. Needed to change the behavior as semver by default, consider that a ^ exists. If we want to consider a =$VERSION when the value is $VERSION, I give it a shot here: 73e75ad, but I've deleted it as it looked pretty ugly.

Please let me know if you have any thoughts/feedbacks on the PR. And thanks for the opportunity of contributing to this fantastic project 😄