GitAuto: [FEATURE] Use GitVersion

[gitauto-ai]

Resolves #56

What is the feature

The feature involves integrating GitVersion into the project to automate Semantic Versioning (SemVer) based on Git history.

Why we need the feature

Implementing GitVersion will streamline the versioning process by automatically generating version numbers based on the commit history. This ensures consistency and accuracy in versioning, which is crucial for release management and dependency tracking.

How to implement and why

1. Remove MSBuild.Version.Target Package:

   • This package is currently used for versioning. We will replace it with GitVersion, which offers more comprehensive and automated versioning capabilities.

2. Delete Properties\\version.txt Files:

   • These files are manually maintained and will become redundant with GitVersion. Removing them will prevent conflicts and reduce maintenance overhead.

3. Create GitVersion.yml:

   • Add a GitVersion.yml file at the root level with mode: Mainline. This configuration will guide GitVersion to use the mainline development mode, which is suitable for projects with a continuous delivery workflow.

4. Update deploy.yml:

   • Modify the deployment pipeline to include steps for running GitVersion. This ensures that the versioning is integrated into the CI/CD process, providing automated version updates with each deployment.

About backward compatibility

The transition to GitVersion will not maintain backward compatibility with the previous versioning system. However, this change is necessary to adopt a more robust and automated versioning strategy. The benefits of improved version management outweigh the need for backward compatibility in this context.

Test these changes locally

git checkout -b gitauto/issue-#56-63af8b1c-766d-4748-a7d6-83b223f7ee76
git pull origin gitauto/issue-#56-63af8b1c-766d-4748-a7d6-83b223f7ee76

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[github-actions]

Infisical secrets check: ✅ No secrets leaked!

Scan results:

11:37PM INF scanning for exposed secrets...
11:37PM INF 56 commits scanned.
11:37PM INF scan completed in 733ms
11:37PM INF no leaks found