Skip to content

[release/v7.4]PMC parse state correctly from update command's response#24860

Merged
TravisEz13 merged 1 commit intoPowerShell:release/v7.4from
anamnavi:backport-24850-74branch2
Jan 23, 2025
Merged

[release/v7.4]PMC parse state correctly from update command's response#24860
TravisEz13 merged 1 commit intoPowerShell:release/v7.4from
anamnavi:backport-24850-74branch2

Conversation

@anamnavi
Copy link
Member

Backport #24850

…24850)

* Parse Json before accessing state property for PMC

* fix typo
@TravisEz13
Copy link
Member

/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PSResourceGet ACR, 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 eb2bf0c into PowerShell:release/v7.4 Jan 23, 2025
7 checks passed
@microsoft-github-policy-service
Copy link
Contributor

microsoft-github-policy-service bot commented Jan 23, 2025

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

2 participants