Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

[release/v7.5] Use GitHubReleaseTask#25402

Merged
TravisEz13 merged 2 commits into
PowerShell:release/v7.5PowerShell/PowerShell:release/v7.5from
pwshBot:backport/release/v7.5/25398-536a43fc6pwshBot/PowerShell:backport/release/v7.5/25398-536a43fc6Copy head branch name to clipboard
Apr 21, 2025
Merged

[release/v7.5] Use GitHubReleaseTask#25402
TravisEz13 merged 2 commits into
PowerShell:release/v7.5PowerShell/PowerShell:release/v7.5from
pwshBot:backport/release/v7.5/25398-536a43fc6pwshBot/PowerShell:backport/release/v7.5/25398-536a43fc6Copy head branch name to clipboard

Conversation

@pwshBot

@pwshBot pwshBot commented Apr 21, 2025

Copy link
Copy Markdown
Collaborator

Backport of #25398 to release/v7.5

Triggered by @TravisEz13 on behalf of @jshigetomi

Original CL Label: CL-BuildPackaging

/cc @PowerShell/powershell-maintainers

Impact

Choose either tooling or Customer impact.

Tooling Impact

  • Required tooling change
  • Optional tooling change (include reasoning)

Customer Impact

  • Customer reported
  • Found internally

[Select one or both of the boxes. Describe how this issue impacts customers, citing the expected and actual behaviors and scope of the issue. If customer-reported, provide the issue number.]

Regression

  • Yes
  • No

[If yes, specify when the regression was introduced. Provide the PR or commit if known.]

Testing

[How was the fix verified? How was the issue missed previously? What tests were added?]

Risk

  • High
  • Medium
  • Low

[High/Medium/Low. Justify the indication by mentioning how risks were measured and addressed.]

@pwshBot pwshBot requested a review from a team as a code owner April 21, 2025 21:46
@TravisEz13 TravisEz13 changed the title [release/v7.5]!!!MERGE_CONFLICT!!! Use GitHubReleaseTask [release/v7.5] Use GitHubReleaseTask Apr 21, 2025
@TravisEz13 TravisEz13 added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Apr 21, 2025
@TravisEz13

Copy link
Copy Markdown
Member

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

@azure-pipelines

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

@TravisEz13 TravisEz13 merged commit 6187484 into PowerShell:release/v7.5 Apr 21, 2025
@microsoft-github-policy-service

microsoft-github-policy-service Bot commented Apr 21, 2025

Copy link
Copy Markdown
Contributor

📣 Hey @@pwshBot, 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

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

Morty Proxy This is a proxified and sanitized view of the page, visit original site.