Skip to content

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

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

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

Copy link

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

@TravisEz13 TravisEz13 enabled auto-merge (squash) January 23, 2025 22:22
@TravisEz13 TravisEz13 merged commit 9b34819 into PowerShell:release/v7.5 Jan 23, 2025
10 checks passed
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

@jshigetomi jshigetomi added the CL-BuildPackaging Indicates that a PR should be marked as a build or packaging change in the Change Log label Apr 17, 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