Bump flatted from 3.2.7 to 3.4.2 (#985)

Bumps [flatted](https://github.com/WebReflection/flatted) from 3.2.7 to 3.4.2.
- [Commits](WebReflection/flatted@v3.2.7...v3.4.2)

---
updated-dependencies:
- dependency-name: flatted
  dependency-version: 3.4.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bump @tootallnate/once, applicationinsights and @vscode/test-electron (…

…#972)

Removes [@tootallnate/once](https://github.com/TooTallNate/once). It's no longer used after updating ancestor dependencies [@tootallnate/once](https://github.com/TooTallNate/once), [applicationinsights](https://github.com/microsoft/ApplicationInsights-node.js) and [@vscode/test-electron](https://github.com/Microsoft/vscode-test). These dependencies need to be updated together.


Removes `@tootallnate/once`

Updates `applicationinsights` from 2.9.5 to 2.9.8
- [Release notes](https://github.com/microsoft/ApplicationInsights-node.js/releases)
- [Changelog](https://github.com/microsoft/ApplicationInsights-node.js/blob/main/CHANGELOG.md)
- [Commits](https://github.com/microsoft/ApplicationInsights-node.js/commits)

Updates `@vscode/test-electron` from 2.3.9 to 2.5.2
- [Changelog](https://github.com/microsoft/vscode-test/blob/main/CHANGELOG.md)
- [Commits](microsoft/vscode-test@v2.3.9...v2.5.2)

---
updated-dependencies:
- dependency-name: "@tootallnate/once"
  dependency-version: 
  dependency-type: indirect
- dependency-name: applicationinsights
  dependency-version: 2.9.8
  dependency-type: indirect
- dependency-name: "@vscode/test-electron"
  dependency-version: 2.5.2
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Add PR creation skill for Copilot (#962)

Add .github/instructions/pr.instructions.md to ensure PRs always include a bug or debt label.

Co-authored-by: Copilot <[email protected]>

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