Setting out to `Cargo.toml` with `workspace.package.version` result in format changing.

[kareemmahlees]

Problem

I have a Rust application and I would like to pump the version in my Cargo.toml each time I make a new release.
My version field resides under workspace.package.version, every time I try to pump the version bumper seems to reformat the whole file into a different format:

• Adding indentations.
• Splitting dependencies into workspace.dependencies.serde and so on.

Desired solution

Nothing should change except for the version.

Workaround

I had to install another crate ( cargo-edit ) with an after:bump hook to update the version.

[PaulBartonADVR]

@kareemmahlees, could you try to upgrade to 7.0.0 and see if your issue has been resolved?

You will also need to upgrade your version of release-it to 18.0.0 as well

[kareemmahlees]

@pbarton-andovercos roger, I am a bit busy currently so I cannot guarantee when I will confirm this.

[jimmyn]

Having the same issue

[alex-pirogov]

having this issue with python's pyproject.toml

[VhalPurohit]

For me its also removing any comments that I left before the bump in my pyproject.toml

[dhofstetter]

@webpro the changes made in #43 lead - in case of python projects - to the situation, that in case there is a dependency within your pyproject.toml having the exact same version, that this might get bumped as well?

[alex-pirogov]

@webpro the changes made in #43 lead - in case of python projects - to the situation, that in case there is a dependency within your pyproject.toml having the exact same version, that this might get bumped as well?

try specifying path like this

"out": {
	"file": "pyproject.toml",
	"type": "text/toml",
	"path": "project.version"
}

[JamesMBarr]

@webpro the changes made in #43 lead - in case of python projects - to the situation, that in case there is a dependency within your pyproject.toml having the exact same version, that this might get bumped as well?

@dhofstetter you were absolutely right about this and I stumbled into that exact issue. This should be fixed now following #53.