Skip to content

Bump Teams SDK to 2.0.8, use User-Agent header#415

Merged
dancer merged 2 commits intovercel:mainfrom
heyitsaamir:chore/bump-teams-sdk-user-agent
Apr 23, 2026
Merged

Bump Teams SDK to 2.0.8, use User-Agent header#415
dancer merged 2 commits intovercel:mainfrom
heyitsaamir:chore/bump-teams-sdk-user-agent

Conversation

@heyitsaamir
Copy link
Copy Markdown
Contributor

Summary

  • Bumps all @microsoft/teams.* packages from 2.0.6 → 2.0.8
  • Switches X-User-Agent header to standard User-Agent in the Teams adapter client config

Test plan

  • Verify Teams adapter builds cleanly (pnpm --filter @chat-adapter/teams build)
  • Confirm bot messages still go through in a Teams environment

@vercel
Copy link
Copy Markdown
Contributor

vercel Bot commented Apr 23, 2026

@heyitsaamir is attempting to deploy a commit to the Vercel Team on Vercel.

A member of the Team first needs to authorize it.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Apr 23, 2026

Co-Authored-By: Claude <noreply@anthropic.com>
@dancer dancer merged commit 885a471 into vercel:main Apr 23, 2026
6 of 8 checks passed
dancer pushed a commit that referenced this pull request Apr 24, 2026
Co-authored-by: Ben Sabic <bensabic@users.noreply.github.com>
patrick-chinchill pushed a commit to Chinchill-AI/chat-sdk-python that referenced this pull request May 10, 2026
Final upstream-coverage audit before merging the 7 sync PRs (#84-#90)
identified one undocumented N/A item:

vercel/chat#415 (Teams SDK 2.0.8 + User-Agent) is a JS-only botbuilder
dependency bump. The Python Teams adapter uses raw aiohttp (no
botbuilder), so there is no equivalent dependency to bump. The optional
User-Agent: Vercel.ChatSDK header on the ~9 outbound aiohttp call sites
is a defense-in-depth nice-to-have; deferred as a follow-up rather than
landed in this sync.

Updates:
- CHANGELOG.md: tick all completed items and link them to their PRs
  (#84, #85, #86, #87, #88, #89, #90, plus already-merged PR #74).
  Document #415 inline as N/A.
- docs/UPSTREAM_SYNC.md non-parity table: add row for Teams User-Agent
  header divergence so future syncers don't try to "port" the JS bump.

Item #6 (concurrency.maxConcurrent) is already implementation-covered
in the Python port (existing divergence row at L492). The 4 new TS
concurrency tests in chat.test.ts have Python-specific equivalents at
test_chat_faithful.py L2969-3055 that don't name-match — leaving as
deferred fidelity-baseline polish since the behavior is verified.

Verdict from the coverage audit: all 18 substantive ports across PRs
#84-#90 are upstream-verified. No commits in chat@4.26.0..f55378a were
missed. Ready to start merging.

https://claude.ai/code/session_01FyMxQn2BEAzmwKS1GZczKj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants