fix: da template ts version mismatch for node 22

[qinzhouxu]

https://dev.azure.com/msazure/Microsoft%20Teams%20Extensibility/_workitems/edit/38615095

[github-actions]

❌ VscUse Test Plan — Tests unknown

Why these tests: Changed files are TypeScript declarative agent templates (bearer/oauth/scratch variants under templates/vsc/ts/declarative-agent-with-action-from-scratch-), matching rule 5 (DA_ plans) with ts language suffix, covering the auth variants affected by the node 22 version fix.

Branch diff: qinzhouxu/ts → dev

Plans run:

• DA_Api_Key_ts_Remote_Debug
• DA_Microsoft_Entra_ts_Remote_Debug
• DA_Oauth_ts_Remote_Debug
• DA_None_ts_Remote_Debug
• DA_No_Action_Remote_Debug

---

Step	Status
1️⃣ Build VSIX (CD)	✅ Done
2️⃣ Build Docker image	✅ Done
3️⃣ Run UI tests	❌ Tests unknown

ℹ️ How were these tests selected?

GitHub Copilot (Claude Sonnet 4.6, high reasoning) analysed the PR title, description, and the diff between
qinzhouxu/ts and dev
to pick the most relevant test plans from packages/tests/vscuse/Index.md.

[github-actions]

E2E Test Selection — AI Selected

Why these tests: All changed files target declarative agent API plugin creation scenarios (bearer, OAuth, no-auth) via fx-core unit tests and DA/VSC templates, so all declarativeAgent/* tests are included (rules 1 and 6); feature/multienv is added for the fx-core package coverage from rule 1.

Cases selected (14):

• ./declarativeAgent/DeclarativeAgentBasic.tests.ts
• ./declarativeAgent/DeclarativeAgentWithApiKeyAuth.tests.ts
• ./declarativeAgent/DeclarativeAgentWithOAuth.tests.ts
• ./declarativeAgent/DeclarativeAgentWithNoneAuth.tests.ts
• ./declarativeAgent/DeclarativeAgentInvalidManifestShape.tests.ts
• ./declarativeAgent/DeclarativeAgentWithEntra.tests.ts
• ./declarativeAgent/typespec/typespec.withoutAction.tests.ts
• ./declarativeAgent/typespec/typespec.withAction.tests.ts
• ./declarativeAgent/mcp/DeclarativeAgentMCPNoAuth.tests.ts
• ./declarativeAgent/mcp/DeclarativeAgentMCPAuthEdgeCases.tests.ts
• ./declarativeAgent/mcp/DeclarativeAgentMCPWithAuth.tests.ts
• ./declarativeAgent/addKnowledge/AddWebSearchByAll.tests.ts
• ./declarativeAgent/addKnowledge/AddWebSearchByUrl.tests.ts
• ./feature/multienv.tests.ts

---

View pipeline run

Need to run more tests?

Comment on this PR:

• /e2e-run ./path/to/test.tests.ts — add specific cases to AI selection
• /e2e-run-all — run all e2e cases

Then re-run the workflow.

[github-actions]

❌ VscUse Test Plan — Tests failure

Why these tests: PR fixes TypeScript version mismatch in declarative agent templates (api-plugin-from-scratch, bearer, oauth variants under templates/vsc/ts/declarative-agent-), mapping to DA_ ts Remote_Debug plans covering the affected auth types.

Branch diff: qinzhouxu/ts → dev

Plans run:

• DA_Api_Key_ts_Remote_Debug
• DA_Oauth_ts_Remote_Debug
• DA_None_ts_Remote_Debug

---

Step	Status
1️⃣ Build VSIX (CD)	✅ Done
2️⃣ Build Docker image	✅ Done
3️⃣ Run UI tests	❌ Tests failure

🎯 Actual UI test run
🔗 Full pipeline results
📊 Detailed test report

ℹ️ How were these tests selected?

GitHub Copilot (Claude Sonnet 4.6, high reasoning) analysed the PR title, description, and the diff between
qinzhouxu/ts and dev
to pick the most relevant test plans from packages/tests/vscuse/Index.md.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.46%. Comparing base (c7420a1) to head (935c99b).
⚠️ Report is 2 commits behind head on dev.

Additional details and impacted files

@@           Coverage Diff           @@
##              dev   #16231   +/-   ##
=======================================
  Coverage   86.45%   86.46%           
=======================================
  Files         624      624           
  Lines       31815    31816    +1     
  Branches     7437     7437           
=======================================
+ Hits        27505    27509    +4     
+ Misses       2481     2479    -2     
+ Partials     1829     1828    -1     

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.