chore(release): v2.0.14 by lilyydu · Pull Request #648 · microsoft/teams.ts

lilyydu · 2026-07-16T17:21:59Z

Release v2.0.14

Prepares the stable 2.0.14 release by merging main into release and setting version.json to the stable version (removing the -preview.{height} suffix).

Previous release: 2.0.13 (published 2026-06-15)
Only functional diff vs main is version.json: 2.0.14-preview.{height} → 2.0.14

What's in this release

After merge

Trigger the release pipeline on release with Public publish type
Bump main → 2.0.15-preview.{height}
Create the v2.0.14 git tag + GitHub Release

Co-authored-by: Copilot [email protected]

) ## Changes - Bump `version.json` to `2.0.14-preview.{height}` for next dev cycle after v2.0.13 release - Split `publish.yml` into separate build and publish stages - Use `templateContext.type: releaseJob` + `isProduction: true` for ESRP publish job (fixes 1ES PT enforcement error) - Release jobs consume pipeline artifacts via `$(Pipeline.Workspace)/...` instead of source directory This fixes the `isReleaseJob` enforcement warning from 1ES PT and ensures ESRP tasks run in a properly declared release job context. --------- Co-authored-by: Copilot <[email protected]>

Quoted replies are now GA. Removes all `ExperimentalTeamsQuotedReplies` diagnostic comments from JSDoc annotations. ## Changes - `packages/apps/src/contexts/activity.ts` - `packages/api/src/activities/message/message.ts` - `packages/api/src/models/entity/quoted-reply-entity.ts` All tests pass (774/774).

Adds 12 integration tests that make real API calls against the Teams Bot Framework service. **Tests:** - Activities: create, update, reply, delete (4) - Members: get all, get by ID, get paged (3) - Conversations: create 1:1, create group (2) - Teams: get details, get channels (2) - Reactions: add and delete (1) **Setup:** ```bash npm install cp test/integration/.env.example test/integration/.env.botid-prod # Fill in credentials npm run test:integration --workspace=@microsoft/teams.integration-tests ``` Integration tests are isolated from normal `npm test` (no `test` script in the workspace, excluded from turbo). See [cross-SDK runbook](https://github.com/microsoft/teams-sdk/blob/main/INTEGRATION-TESTS.md) for provisioning and troubleshooting. --------- Co-authored-by: Copilot <[email protected]>

Updates the integration test README runbook link to point to the internal ADO wiki. Co-authored-by: Copilot <[email protected]>

…#625) The 1ES template requires `artifactName` (not `artifact`) for `pipelineArtifact` input declarations in `templateContext`. This was causing: ``` Unexpected value 'artifactName is a required argument for pipelineArtifact input and 1ES.DownloadPipelineArtifact@1 task' ``` Co-authored-by: Copilot <[email protected]>

## Summary - Adds `'extendedmarkdown'` to the `TextFormat` union type for rich content rendering (GFM tables, LaTeX math) - Updates JSDoc comments with reference to `TextFormat` type - Adds unit test for `withTextFormat('extendedmarkdown')` - Adds new `formatted-messaging` sample demonstrating all text formats: markdown, extendedmarkdown, xml, and plain ## Test plan - [x] Unit tests pass (`message.spec.ts` — 31/31) - [x] `formatted-messaging` sample builds clean - [x] E2E validated in Teams ## Screenshots <img width="363" height="125" alt="image" src="https://github.com/user-attachments/assets/7b2ed266-c3b0-4be9-b336-cc03a0957b05" /> <img width="344" height="266" alt="image" src="https://github.com/user-attachments/assets/d39f3614-dbc3-4050-9ab9-a1e105da68d3" /> <img width="413" height="191" alt="image" src="https://github.com/user-attachments/assets/5b208d10-5d67-4c0d-b61c-69e7bdf073a7" /> <img width="630" height="297" alt="image" src="https://github.com/user-attachments/assets/ad193b43-115f-409d-9925-a5953804e064" /> --------- Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>

## Summary Internal refactor of `@microsoft/teams.apps` that converts `this: App`-bound free functions into dedicated collaborator classes and "smart" context objects, mirroring the structure of the Python SDK (`teams.py`). No intended change to end-user behavior — this is structural cleanup. ## Why the previous approach was bad The old design implemented a lot of `App`'s behavior as standalone free functions in `app.routing.ts` / `app.embed.ts` that were bound onto the class with `this: App` and assigned like `on = on; message = message; func = func; tab = tab;`. That had several problems: - **No real encapsulation.** Every one of these functions took the entire `App` as `this`, so they could reach into any field on `App` (the DI container, event manager, token manager, server, plugin array, etc.). Dependencies were implicit and untracked — you couldn't tell what a function actually needed without reading its whole body, and nothing stopped it from depending on more over time. - **`App` was a god object.** Plugin lifecycle/registration/injection, activity processing, oauth handling, and function/tab wiring were all smeared across `App` plus a grab-bag of free-function files, instead of living in cohesive units. This made the class hard to read and reason about, and changes in one concern risked touching unrelated ones. - Probably most importantly, it made things unnecessarily public so that they could be shared between files. So in interest of separating out logic in files, we polluted things in our public interface. Things like token-manager which should be implementation details were publicly leaked which made things like refactors extremely difficult. ## Changes - **`PluginManager`** (`app.plugins.ts`) — owns the plugin registry, duplicate-name check, container double-registration, dependency/event injection, and `onInit`/`onStart`/`onStop` lifecycle. `App` delegates `plugin()`/`getPlugin()` to it. The `plugins` getter returns the live array so `EventManager`/`ActivityProcessor` observe plugins added after construction. - **`FunctionContext`** class (`contexts/function.ts`) — owns `send()` and conversation-id resolution, replacing the inline closures. `getConversationIdResolver` now takes `api` instead of `app`. - **Inlined** `on`/`message`/`use`/`event`/`function`/`tab` into `App` as proper methods; **deleted** `app.routing.ts` and `app.embed.ts`. - **`app.oauth.ts`** — removed the `as TokenExchangeInvokeResponse` cast in favor of a typed `const body`. - Fully encapsulated `App` plugin state (removed the public `plugins` getter; `getPlugin(name)` remains the read path). ## Verification - `tsc` clean, eslint clean - 284/284 apps tests pass ## Reviewer note `tokenManager` visibility was narrowed from `public readonly` to `protected readonly` --------- Co-authored-by: Copilot <[email protected]>

## Summary Reduces the number of chained member accesses ("hops") needed to call the API by promoting grouped sub-client methods onto their parent clients. Common calls drop from **3 hops to 2**. The change is **additive and backward compatible** — the existing chained accessors remain as `@deprecated` aliases until officially removed. ## Flattening | Old (deprecated, kept) | New | | --- | --- | | `users.token.{get,getAad,getStatus,signOut,exchange}` | `users.{getToken,getAadTokens,getTokenStatus,signOut,exchangeToken}` | | `conversations.activities(id).{create,update,reply,delete,members,createTargeted,updateTargeted,deleteTargeted}` | `conversations.{createActivity,updateActivity,replyToActivity,deleteActivity,getActivityMembers,createTargetedActivity,updateTargetedActivity,deleteTargetedActivity}` | | `conversations.members(id).{get,getById,getPaged,delete}` | `conversations.{getMembers,getMemberById,getPagedMembers}` | | `client.reactions.{add,delete}` | `conversations.{addReaction,deleteReaction}` | `teams.*` and `meetings.*` were already 2 hops — unchanged. ## Other changes - **BotClient deprecated** — no longer used; the whole class and the `client.bots` accessor are marked `@deprecated` (not flattened). - **Reactions moved** into the conversation/activity context (`conversations.addReaction(conversationId, activityId, type)`); `client.reactions` kept as a deprecated alias. - **No internal use of deprecated members** — deprecated sub-client instances are held privately (`protected _token`/`_bots`/`_reactions`) and exposed via deprecated public accessors, so the flattened code and `Client.set http` never touch a deprecated member. - **Internal callers migrated** — `@microsoft/teams.apps` now uses the flattened API. ## Tests - New specs for the flattened methods on `UserClient` and `ConversationClient`. - Full coverage of the deprecated chained aliases, co-located with the relevant sub-client specs. ## Verification - `@microsoft/teams.api`: 20 suites / 194 tests ✓, lint ✓ - `@microsoft/teams.apps`: 19 suites / 284 tests ✓ - All essential (non-graph) packages build ✓ ## Notes - Deprecation notices intentionally omit a specific removal date ("in a future release"). Pre-existing deprecations elsewhere were left untouched. --------- Co-authored-by: lilydu <[email protected]> Co-authored-by: Copilot <[email protected]> Co-authored-by: Copilot Autofix powered by AI <[email protected]>

…ndling (#635) ## Summary Ports two merged **teams.py** PRs to TypeScript: - microsoft/teams.py#453 — streaming error handling for the 2-minute timeout & "content stream not allowed" - microsoft/teams.py#495 — support resetting response streams (reuse after `close()`) ## Streaming error handling (port of #453) - Add `TerminalStreamError`, `StreamTimedOutError`, and `StreamNotAllowedError` (in `types/streamer.ts`). - `HttpStream.send()` now inspects the `403` response body and maps it to the right error instead of always treating a `403` as canceled: - `exceeded streaming time` → `StreamTimedOutError` (marks `timedOut`) - `cancel` → `StreamCancelledError` - `not allowed` → `StreamNotAllowedError` - anything else / empty body → `TerminalStreamError` - On a 2-minute streaming timeout, the stream finalizes by **updating the original message in place** — it drops the `streaminfo` entity and stream `channelData` so the send routes through *update* (reusing the id) rather than posting a duplicate. - Chunk sends swallow a timeout mid-stream; `close()` then sends the buffered content as a plain final message. - `retry` gains a `nonRetryable` option so terminal stream errors are not retried. ## Reusable streams (port of #495) - Emitting or updating after `close()` reopens the stream on the **same instance**, starting a new streamed message. - `close()` is idempotent until the next emit/update. - `app.process.ts` close listener switched from `once` → `on` so each reused-stream close fires. ## Example Adds `examples/stream`, mirroring the teams.py example's final state: - default message → single-stream demo with suggested actions - `simple-card` → sends a minimal Adaptive Card outside the streaming flow - `multi-stream` → emits an Adaptive Card as stream 1's final message, `close()`s, then reuses `ctx.stream` for a second streamed response ## Tests - `packages/apps` http-stream spec extended: 403 message→error mapping (parametrized), empty-body 403 → terminal error, final-send timeout updates in place, mid-stream timeout updates in place, and emit-after-close stream reuse. - Full `packages/apps` suite passes (294 tests); `tsc` and eslint clean across the changed library files and the new example. ## Notes - The Python-only `uv.lock` change was not ported. - `examples/stream/.env` is gitignored (no credentials committed). --------- Co-authored-by: Copilot <[email protected]> Co-authored-by: Copilot Autofix powered by AI <[email protected]>

…637) Update the reactions, targeted-messages, and message-extensions examples to use the flattened conversations.* methods instead of the deprecated chained accessors. Co-authored-by: Copilot <[email protected]>

…638) ## What Adds an "npm Registry (Microsoft-managed devices)" section to `CONTRIBUTING.MD`. ## Why Direct access to `registry.npmjs.org` is now blocked on Microsoft-managed devices; npm/pnpm/yarn must resolve through the org's Central Feed Services (CFS) proxy. Contributors on managed devices hitting install failures had no guidance in-repo. ## Notes - Points to [aka.ms/CFS](https://aka.ms/CFS) rather than hardcoding an internal feed URL — per CFS guidance, onboarding config stays private to the build and must not be committed to a public repo. - Clarifies **external contributors are unaffected** (public npm still works for them). - Distinguishes the device-level reroute (this note) from repo-level CFS onboarding (handled in the build pipeline, tracked separately). --------- Co-authored-by: Corina Gum <> Co-authored-by: Copilot <[email protected]>

updated the `send` method to set the `replyToId` field on every streaming activity - matches v1 implementation (was automatically done through BF previously)

Currently, `MessageActivity` / `TypingActivity` are used to represent both _outbound_ AND _inbound_ activities. These classes model the full activity shape, including fields that have no meaning on an outbound call. (`from`, `conversation`, `channelId`, `serviceUrl`, `timestamp`, etc.). That creates confusing devex: callers can set fields that are ignored or overwritten by the send path, and it blurs the distinction between activities the app receives and activities the app sends. In practice, apps only send two outbound activity types: 1. Message 2. Typing This PR prototypes an outbound input model for those sendable activities: - `ActivityInput` as the outbound base class - `MessageActivityInput` - `TypingActivityInput` - `ActivityParams = IMessageActivityInput | ITypingActivityInput` The inbound activity/router model stays unchanged, but app-facing send/create surfaces are now centered around outbound activity inputs. ## Backward compatibility Now, existing code often does: ```ts ctx.send(new MessageActivity().withText("hi")) ``` To keep that working, this PR keeps accepting `MessageActivity` and `TypingActivity` on send surfaces through deprecated overloads. When those legacy builders are passed to `send`, they are converted into `MessageActivityInput` / `TypingActivityInput` before sending. That gives users migration guidance without breaking existing code: So now, this is the more correct code: ```ts ctx.send(new MessageActivityInput().withText("hi")) ``` But this continues to work: <img width="889" height="248" alt="image" src="https://github.com/user-attachments/assets/c9f0184e-acd7-4ae5-831f-834e780473b6" /> The conversion intentionally drops server-populated fields like `from`, `conversation`, `channelId`, and `serviceUrl` so the wire payload matches what the app is actually allowed to send. ## Non-sendable activity cleanup `ActivityParams` remains the outbound input union. Non-sendable activity types such as `messageUpdate`, `messageDelete`, `messageReaction`, and invoke feedback are not accepted by activity create/send APIs, so we removed those. Call sites that previously tried to create those activity types were updated to use the appropriate APIs instead, such as update, delete, and reaction endpoints. --------- Co-authored-by: Copilot App <[email protected]>

Merge origin/main into release and set version.json to stable 2.0.14 Co-authored-by: Copilot <[email protected]>

dependabot Bot and others added 17 commits June 15, 2026 20:45

docs: update integration test runbook link to ADO wiki (#624)

96dd82a

Updates the integration test README runbook link to point to the internal ADO wiki. Co-authored-by: Copilot <[email protected]>

set replyToId for all streaming activities (#646)

b424913

updated the `send` method to set the `replyToId` field on every streaming activity - matches v1 implementation (was automatically done through BF previously)

chore(release): prepare v2.0.14

2866411

Merge origin/main into release and set version.json to stable 2.0.14 Co-authored-by: Copilot <[email protected]>

heyitsaamir approved these changes Jul 16, 2026

View reviewed changes

lilyydu merged commit b2572d3 into release Jul 16, 2026
6 checks passed

lilyydu deleted the prep-release/2.0.14 branch July 16, 2026 17:37

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

chore(release): v2.0.14#648

chore(release): v2.0.14#648
lilyydu merged 17 commits into
releasefrom
prep-release/2.0.14

lilyydu commented Jul 16, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Uh oh!

Conversation

lilyydu commented Jul 16, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release v2.0.14

What's in this release

🚀 Features

🐛 Fixes

♻️ Refactors

🧪 Tests

📚 Docs & Examples

🔧 Chores & Dependencies

After merge

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

lilyydu commented Jul 16, 2026 •

edited

Loading