- Notifications
You must be signed in to change notification settings - Fork7.7k
[release/v7.5] Make theAssemblyVersion does not change for servicing releases#24783
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PowerShell-CI-static-analysis, PSResourceGet ACR, PowerShell-Windows-Packaging-CI |
| Azure Pipelines successfully started running 5 pipeline(s). |
f4c17e4 intorelease/v7.5Uh oh!
There was an error while loading.Please reload this page.
microsoft-github-policy-servicebot commentedJan 15, 2025 • edited by unfurl-linksbot
Loading Uh oh!
There was an error while loading.Please reload this page.
edited by unfurl-linksbot
Uh oh!
There was an error while loading.Please reload this page.
📣 Hey@TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗https://aka.ms/PSRepoFeedback |
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.