chore: prevent deprecated packages from being published#614
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR prevents deprecated packages in the monorepo from being included in publish artifacts by marking them private: true and adding a publish-pipeline safeguard to skip any package that has a deprecated field.
Changes:
- Marked deprecated packages as
"private": trueto exclude them from the packing/publishing process. - Added a missing
deprecatedmessage to@microsoft/teams.dev. - Updated the Azure DevOps publish pipeline to skip packages with a
deprecatedfield (in addition toprivate: true).
Reviewed changes
Copilot reviewed 7 out of 7 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| packages/openai/package.json | Marks @microsoft/teams.openai as private to prevent publishing. |
| packages/dev/package.json | Marks @microsoft/teams.dev as private and adds a deprecation message. |
| packages/ai/package.json | Marks @microsoft/teams.ai as private to prevent publishing. |
| external/mcpclient/package.json | Marks @microsoft/teams.mcpclient as private to prevent publishing. |
| external/mcp/package.json | Marks @microsoft/teams.mcp as private to prevent publishing. |
| external/a2a/package.json | Marks @microsoft/teams.a2a as private to prevent publishing. |
| .azdo/publish.yml | Skips packing deprecated packages during publish runs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Mark all deprecated packages as private to prevent npm pack from including them in releases: - @microsoft/teams.ai - @microsoft/teams.openai - @microsoft/teams.dev - @microsoft/teams.mcp - @microsoft/teams.mcpclient - @microsoft/teams.a2a Also add a deprecated field check in the publish pipeline as a secondary safeguard so any package with a "deprecated" field is skipped even without the private flag. Co-authored-by: Copilot <[email protected]>
corinagum
force-pushed
the
cg/deprecation
branch
from
June 11, 2026 20:07
98bd246 to
a20a768
Compare
MehakBindra
approved these changes
Jun 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Mark all deprecated packages as
private: trueso they are excluded fromnpm packduring publish runs. Also adds adeprecatedfield check in the publish pipeline as a secondary safeguard.Packages affected
@microsoft/teams.ai@microsoft/teams.openai@microsoft/teams.dev@microsoft/teams.mcp@microsoft/teams.mcpclient@microsoft/teams.a2aChanges
"private": trueto each deprecated package'spackage.json"deprecated"field to@microsoft/teams.dev(was missing).azdo/publish.ymlto skip packages with adeprecatedfieldNote
All packages except
@microsoft/teams.devare already marked deprecated on npm.teams.devneeds an org admin to runnpm deprecate.