Skip to content

Conversation

@bschnurr
Copy link
Member

  • publish was failing complaining '--allow-proposed-apis' flags still missing.

Added env: EnabledApiProposalsJson: ${{ parameters.enabledApiProposalsJson }} on the PowerShell@2 step.
Script continues to read $env:EnabledApiProposalsJson (safe for JSON with quotes).
publish-extension.yml
Wired it up: enabledApiProposalsJson: $(EnabledApiProposalsJson) when calling the publish template.
This should fully eliminate the PowerShell parser failure you hit while still allowing the --allow-proposed-apis ... list to be applied when present.
…the publish script was turning the JSON into a nested array and then joining/printing it poorly — which then produced an invalid CLI arg: --allow-proposed-apis System.Object[].

I’ve fixed that parsing/flattening in publish.yml, so the publish log should now show:

enabledApiProposals (from EnabledApiProposalsJson): portsAttributes, debugVisualization, contribViewsWelcome
and the npx ... publish command should include: --allow-proposed-apis portsAttributes debugVisualization contribViewsWelcome
@bschnurr bschnurr added the debt Covers everything internal: CI, testing, refactoring of the codebase, etc. label Jan 23, 2026
@bschnurr bschnurr merged commit f0a8a66 into main Jan 23, 2026
18 of 19 checks passed
@bschnurr bschnurr deleted the test-proposed branch January 23, 2026 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

debt Covers everything internal: CI, testing, refactoring of the codebase, etc.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants