Removed all --allow-proposed-apis logic (and the EnabledApiProposalsJ…

…son env wiring) from publish.yml. (#938)

Updated both publish paths to use --no-verify (correct flag name; --noVerify won’t work):
Pre-release: adds --no-verify --pre-release
Stable: adds --no-verify
This should avoid the unknown option '--allow-proposed-apis …' failure entirely by no longer passing that option.

Fix passing parameter enabledApiProposalsJson (#937)

* Added template parameter enabledApiProposalsJson.
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.

* disable publish

* The System.Object[] happened later, inside the publish step, because 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

* uncomment publish

The System.Object[] happened later, inside the publish step, because …

…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

The System.Object[] happened later, inside the publish step, because …

…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

disable publish

append proposed flags to publish (#936)

Remove scripts folder add logic back to yml (#935)

* remove scripts due to releaseJob

* disable publish for testing

* re-enable publish

disable publish for testing

fix regex

clean Microbuild plugins temp dir (#929)