Skip to content

[release/v7.4]Fix V-Pack download package name #25078

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 our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 24, 2025

Conversation

TravisEz13
Copy link
Member

Backport #24866

This pull request includes a small change to the .pipelines/PowerShell-vPack-Official.yml file. The change updates the packageArtifactName variable to include a more specific identifier for the Windows architecture.

  • .pipelines/PowerShell-vPack-Official.yml: Changed packageArtifactName from 'drop_windows_package_package_${{ parameters.architecture }}' to 'drop_windows_package_package_win_${{ parameters.architecture }}' to better specify the Windows architecture.

Co-authored-by: Justin Chung <[email protected]>
Co-authored-by: Travis Plunk <[email protected]>
@TravisEz13
Copy link
Member Author

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

Copy link

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

@TravisEz13 TravisEz13 merged commit 5ea9308 into PowerShell:release/v7.4 Feb 24, 2025
31 checks passed
@TravisEz13 TravisEz13 deleted the backport-24866-74 branch February 24, 2025 23:02
Copy link
Contributor

microsoft-github-policy-service bot commented Feb 24, 2025

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

🔗 https://aka.ms/PSRepoFeedback

@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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