[release/v7.5] Make the AssemblyVersion does not change for servicing releases
#24783
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.


Backport #24667
This pull request includes changes to the build configuration files to improve versioning and tagging for release builds. The most important changes include adding a
ReleaseTagparameter to theStart-PSBuildcommands and explicitly settingFileVersionandAssemblyVersionin thePowerShell.Common.propsfile.Changes to build configuration:
.pipelines/templates/nupkg.yml: Added-ReleaseTag $(ReleaseTagVar)parameter toStart-PSBuildcommands for bothlinux-x64andwin7-x64runtimes. [1] [2]Changes to versioning:
PowerShell.Common.props: Added explicit settings forFileVersionandAssemblyVersionto ensure consistent versioning for servicing releases.PowerShell.Common.props: Updated comment to clarify whenFileVersionandAssemblyVersionare set explicitly.