Release 2.0.7 (Libraries): exclude quoted replies#510
Conversation
Squashed merge of origin/main into releases/v2, with quoted-replies (PR #389) reverted. Keeps release branch's version.json (2.0.6); version.json will be bumped to 2.0.7 on this branch before publishing. core/ is out of scope for this release. Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
Merging via admin override — why we're not waiting for
|
| Check | Source | Status |
|---|---|---|
Teams.NET-PR (Build/Test/Pack — Legacy) |
ADO | ✅ pass |
Teams.NET-PR (Build/Test/Pack — Core) |
ADO | ✅ pass |
Local dotnet build + dotnet test on Microsoft.Teams.sln |
macOS | ✅ pass (0 errors, 146+146 + 407+407 + 63+63 + 17+17 + 9+9 + 3+3 + 25+25 tests across net8.0/net10.0) |
Local dotnet pack + consumer-install smoke test |
macOS | ✅ pass (QuotedReplyEntity ships; no AddQuote/PrependQuote symbols; ReactionClient.AddAsync/DeleteAsync present) |
Publish path
The actual release pipeline is Teams.NET-ESRP in Azure DevOps, not GitHub Actions. The env-file fragility doesn't apply there.
Summary
Brings
mainintoreleases/v2for the 2.0.7 Libraries release, with quoted-replies (PR #389) excluded. Scope is Legacy / Libraries only —core/is not in scope for this release.Single squashed commit.
What's in this release
[Experimental("ExperimentalTeamsReactions")]removed across LibrariesWhat's NOT in this release
Quoted-replies feature (PR #389) is excluded:
MessageActivity.AddQuote(),PrependQuote()builder methods — absentContext.Reply()quote-aware behavior — reverted to legacyreplyToId+ blockquoteSamples/Samples.Quoting— removedKept intentionally:
QuotedReplyEntityandQuotedReplyDatatypes stay inMicrosoft.Teams.Api.Entities(still annotated[Experimental("ExperimentalTeamsQuotedReplies")]) so inbound activities carryingquotedReplyentities still parseMessageActivity.AddTargetedMessageInforuntime strip-QR logic — preserves prompt-preview cleanupquotedReply(with existing#pragma warning disable ExperimentalTeamsQuotedReplies)Version
version.json:2.0.6→2.0.7Scope
Libraries only.
core/(thereleases/coretrack) is not affected by this PR — when this prep merges toreleases/v2, thecore/tree may appear in the branch as part of the merge, but the Legacy publish pipeline only builds and ships fromLibraries/,Samples/, andTests/.Test plan
dotnet build Microsoft.Teams.sln --configuration Release— 0 errors, 5 pre-existing warningsdotnet test Microsoft.Teams.sln --configuration Release— all suites pass across net8.0 and net10.0 (Api 407+407, Apps 136+136, Common 63+63, AI 17+17, McpClient 9+9, Graph 3+3, AspNetCore 25+25 with 1 pre-existing skip)dotnet pack— nupkgs produced; consumer install verified (fresh console project,dotnet add package Microsoft.Teams.Apps --prerelease,dotnet runconfirmsQuotedReplyEntityships,AddQuote/PrependQuoteabsent,AddTargetedMessageInfopresent,ReactionClient.AddAsync/DeleteAsyncpresent)packageSet=Legacy,publishType=Public(post-merge)🤖 Generated with Claude Code