Skip to content

Fix Rush linking for YAML parser - #26

Open
Ramses Sanchez-Hernandez (ramsessanchez) wants to merge 1 commit into
powershell-v2from
fix/js-yaml-alias-bin
Open

Ramses Sanchez-Hernandez (ramsessanchez) wants to merge 1 commit into
powershell-v2from
fix/js-yaml-alias-bin

Conversation

@ramsessanchez

Copy link
Copy Markdown

Summary

  • remove the direct js-yaml v4 alias that collides with the legacy js-yaml CLI shim on Windows
  • parse code-model YAML with the existing js-yaml 3.15.1 dependency, which has no 100-level default depth limit
  • retain js-yaml 4.3.2 for transitive consumers through the existing pnpm overrides

Validation

  • frozen Rush install
  • Rush rebuild for @autorest/powershell
  • generator tests (3 passing)
  • synthetic 150-level YAML parse

Remove the direct js-yaml v4 alias whose CLI shim collides with the legacy js-yaml dependency during Rush linking. Parse generator input with js-yaml 3.15.1, which supports deeply nested models without the v4 maxDepth default.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 1e7f85c5-be3d-4b8e-9f44-4f18b55da093
Ramses Sanchez-Hernandez (ramsessanchez) pushed a commit to microsoftgraph/msgraph-sdk-powershell that referenced this pull request Sep 15, 2026
Point the SDK at microsoftgraph/autorest.powershell#26 to avoid the js-yaml alias CLI collision during Rush linking.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 1e7f85c5-be3d-4b8e-9f44-4f18b55da093
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant