increment_version_number_in_xcodeproj results in unwanted project file changes

[matrejek]

I'm on fastlane-plugin-versioning (0.7.0) and fastlane 2.225.0.

I have defined a a simple lane to automate bumping patch version in my project. It's a part of an automated routine I would like to use to bump version, commit and create PR.

The lane looks like that:

  lane :patch_version_bump do |options|

    increment_version_number_in_xcodeproj(
      xcodeproj: projectFileName,
      bump_type: 'patch'
    )
end

However, the invocation results not only in changing the MARKETING_VERSION value but also changes comments on build plugins included from:

		FB44616F2C5A0D7600F86045 /* PBXTargetDependency */ = {
			isa = PBXTargetDependency;
			productRef = FB44616E2C5A0D7600F86045 /* SwiftLintPlugin */;
		};

to

		FB44616F2C5A0D7600F86045 /* PBXTargetDependency */ = {
			isa = PBXTargetDependency;
			productRef = FB44616E2C5A0D7600F86045 /* plugin:SwiftLintPlugin */;
		};

Is there a way to prevent that?

[jdouglas-nz]

hey @matrejek,
that is annoying!
as this gem doesn't do the actual project 'manipulation', it's preferable to wait until the 'upstream' Xcodeproj gem is fixed. Looks like someone else is removing that weird prefix in a PR here. I'll update this gem ASAP when it is fixed