[release/v7.6] Fix ConvertFrom-ClearlyDefinedCoordinates to handle API object coordinates#26986
Merged
jshigetomi merged 1 commit intoPowerShell:release/v7.6from Mar 10, 2026
Conversation
…nates (PowerShell#26893) Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: TravisEz13 <10873629+TravisEz13@users.noreply.github.com> Co-authored-by: Travis Plunk <travis.plunk@microsoft.com> Co-authored-by: PowerShell Team Bot <69177312+pwshBot@users.noreply.github.com> Co-authored-by: Dongbo Wang <dongbow@microsoft.com>
daxian-dbw
added
the
CL-BuildPackaging
Contributor
There was a problem hiding this comment.
Pull request overview
Backport to release/v7.6 that fixes ClearlyDefined license-generation tooling by making ConvertFrom-ClearlyDefinedCoordinates handle the coordinates value returned as an API object (in addition to the existing string form), preventing downstream harvest failures.
Changes:
- Broaden
ConvertFrom-ClearlyDefinedCoordinatesinput from[string]to[object]. - Add branching logic to parse either a coordinate string (
type/provider/namespace/name/revision) or a PSCustomObject withtype/provider/namespace/name/revisionproperties.
jshigetomi
approved these changes
Mar 10, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Backport of #26893 to release/v7.6
Triggered by @daxian-dbw on behalf of @app/copilot-swe-agent
Original CL Label: CL-BuildPackaging
/cc @PowerShell/powershell-maintainers
Impact
REQUIRED: Choose either Tooling Impact or Customer Impact (or both). At least one checkbox must be selected.
Tooling Impact
Fixes ClearlyDefined license generation tooling. The ConvertFrom-ClearlyDefinedCoordinates function only accepted string input, but Get-ClearlyDefinedData returns PSCustomObject from the API. This caused Start-ClearlyDefinedHarvest to fail. Backporting only the ClearlyDefined.psm1 fix (reverted all dependency updates).
Customer Impact
Regression
REQUIRED: Check exactly one box.
This is not a regression.
Testing
Original PR tested with ClearlyDefined API responses. Backport verified by reviewing diff shows only ClearlyDefined.psm1 changes.
Risk
REQUIRED: Check exactly one box.
Low risk - isolated change to a single tooling script used for license generation. Only affects ClearlyDefined coordinate parsing logic. Does not impact runtime or user-facing features. Change adds conditional logic to handle both input types without breaking existing string input handling.
Merge Conflicts
6 files had conflicts (dependency version updates). Resolved by reverting all changes except ClearlyDefined.psm1 to keep only the tooling fix without pulling in dependency updates.