KEMBAR78
Fix variable reference for release environment in pipeline by TravisEz13 · Pull Request #26012 · PowerShell/PowerShell · GitHub
Skip to content

Conversation

@TravisEz13
Copy link
Member

@TravisEz13 TravisEz13 commented Sep 8, 2025

PR Summary

This pull request makes a minor update to the .pipelines/PowerShell-Release-Official.yml file, correcting the way the ob_release_environment variable is set to ensure it uses the intended value.

  • Changed ob_release_environment assignment to reference variables.releaseEnvironment instead of parameters.releaseEnvironment for proper variable resolution.

PR Context

Found during 7.5.3 release

PR Checklist

@TravisEz13 TravisEz13 requested review from a team and jshigetomi as code owners September 8, 2025 19:24
@TravisEz13 TravisEz13 added BackPort-7.4.x-Consider BackPort-7.5.x-Consider CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log labels Sep 8, 2025
@TravisEz13
Copy link
Member Author

/azp run PowerShell-CI-linux-packaging, PowerShell-Windows-Packaging-CI

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@TravisEz13 TravisEz13 merged commit db25106 into PowerShell:master Sep 8, 2025
43 of 46 checks passed
@microsoft-github-policy-service
Copy link
Contributor

microsoft-github-policy-service bot commented Sep 8, 2025

📣 Hey @@TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️

🔗 https://aka.ms/PSRepoFeedback

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BackPort-7.4.x-Done BackPort-7.5.x-Done CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants