Skip to content

Conversation

@JennyPng
Copy link
Member

@JennyPng JennyPng commented Jan 15, 2026

related to #44592

  • adds a new section to pyproject.tomls specifying if the package should be released as part of a bundle or individually to Conda

updates pyproject.tomls for packages that

  • are not mgmt (as all mgmt packages are by default bundled)
  • have a stable release on pypi

for individually released packages:

[tool.azure-sdk-conda]
in_bundle = false

example of bundle:

[tool.azure-sdk-conda]
in_bundle = true
bundle_name="azure-communication"

all stable release packages will be expected to set this metadata in their pyproject.toml, and it will be enforced in CI

summary of pyproject.toml updates:

[UPDATED] sdk/ai/azure-ai-agents
[UPDATED] sdk/appconfiguration/azure-appconfiguration
[UPDATED] sdk/appconfiguration/azure-appconfiguration-provider
[UPDATED] sdk/communication/azure-communication-callautomation
[UPDATED] sdk/communication/azure-communication-chat
[UPDATED] sdk/communication/azure-communication-email
[UPDATED] sdk/communication/azure-communication-identity
[UPDATED] sdk/communication/azure-communication-jobrouter
[UPDATED] sdk/communication/azure-communication-messages
[UPDATED] sdk/communication/azure-communication-phonenumbers
[UPDATED] sdk/communication/azure-communication-rooms
[UPDATED] sdk/communication/azure-communication-sms
[UPDATED] sdk/containerregistry/azure-containerregistry
[CREATED] sdk/contentsafety/azure-ai-contentsafety
[UPDATED] sdk/core/azure
[UPDATED] sdk/core/azure-common
[UPDATED] sdk/core/azure-core
[UPDATED] sdk/cosmos/azure-cosmos
[UPDATED] sdk/devcenter/azure-developer-devcenter
[UPDATED] sdk/deviceupdate/azure-iot-deviceupdate
[UPDATED] sdk/digitaltwins/azure-digitaltwins-core
[UPDATED] sdk/documentintelligence/azure-ai-documentintelligence
[UPDATED] sdk/evaluation/azure-ai-evaluation
[UPDATED] sdk/eventgrid/azure-eventgrid
[UPDATED] sdk/formrecognizer/azure-ai-formrecognizer
[UPDATED] sdk/healthdataaiservices/azure-health-deidentification
[CREATED] sdk/healthinsights/azure-healthinsights-radiologyinsights
[UPDATED] sdk/keyvault/azure-keyvault
[UPDATED] sdk/keyvault/azure-keyvault-administration
[UPDATED] sdk/keyvault/azure-keyvault-certificates
[UPDATED] sdk/keyvault/azure-keyvault-secrets
[UPDATED] sdk/loadtesting/azure-developer-loadtesting
[UPDATED] sdk/ml/azure-ai-ml
[CREATED] sdk/monitor/azure-monitor
[CREATED] sdk/monitor/azure-monitor-ingestion
[UPDATED] sdk/monitor/azure-monitor-opentelemetry
[CREATED] sdk/monitor/azure-monitor-query
[CREATED] sdk/monitor/azure-monitor-querymetrics
[UPDATED] sdk/schemaregistry/azure-schemaregistry
[UPDATED] sdk/schemaregistry/azure-schemaregistry-avroencoder
[UPDATED] sdk/search/azure-search-documents
[UPDATED] sdk/servicefabric/azure-servicefabric
[CREATED] sdk/storage/azure-storage
[UPDATED] sdk/storage/azure-storage-blob
[UPDATED] sdk/storage/azure-storage-file-datalake
[UPDATED] sdk/storage/azure-storage-file-share
[UPDATED] sdk/storage/azure-storage-queue
[UPDATED] sdk/synapse/azure-synapse-accesscontrol
[UPDATED] sdk/synapse/azure-synapse-artifacts
[UPDATED] sdk/synapse/azure-synapse-managedprivateendpoints
[UPDATED] sdk/synapse/azure-synapse-monitoring
[UPDATED] sdk/synapse/azure-synapse-spark
[UPDATED] sdk/tables/azure-data-tables
[UPDATED] sdk/textanalytics/azure-ai-textanalytics
[UPDATED] sdk/translation/azure-ai-translation-document
[CREATED] sdk/vision/azure-ai-vision-imageanalysis
[UPDATED] sdk/webpubsub/azure-messaging-webpubsubservice

------------------------------------------------------------
Summary:
  Created: 8
  Updated: 49

edge case notes:

  • azure-healthinsights and azure-ai-vision are specified as bundles as an edge case, since their release name does not match the individual package name

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR adds Conda release metadata to pyproject.toml files for all stable (non-management) SDK packages to specify whether they should be released to Conda individually or as part of a bundle. The metadata will be enforced by CI to ensure all stable packages have this configuration.

Changes:

  • Added [tool.azure-sdk-conda] sections to 57 pyproject.toml files
  • Packages are configured as either individual releases (in_bundle = false) or bundle releases (in_bundle = true with bundle_name specified)
  • Created new pyproject.toml files for 8 packages that didn't previously have them

Reviewed changes

Copilot reviewed 62 out of 62 changed files in this pull request and generated no comments.

File Description
sdk/*/pyproject.toml (49 updated) Added Conda metadata section to existing pyproject.toml files
sdk/*/pyproject.toml (8 created) Created new pyproject.toml files with Conda metadata for packages without existing configuration

@xiangyan99
Copy link
Member

What's this PR for?

@scbedd
Copy link
Member

scbedd commented Jan 16, 2026

To any codeowners of the affected packages. These pyproject.toml changes are will not change any function of your package. They are purely leaning on the customizable nature of pyproject.toml to add some build metadata for our conda-shippping packages.

Going to bypass review requirements and merge on "EngSys needs this" basis here.

@JennyPng
Copy link
Member Author

@xiangyan99 I'm working on entirely automating the conda release process. this lets us make service teams tell us whether their packages should be released in a bundle or individually, which is necessary info for the automation

@xiangyan99
Copy link
Member

xiangyan99 commented Jan 16, 2026

@xiangyan99 I'm working on entirely automating the conda release process. this lets us make service teams tell us whether their packages should be released in a bundle or individually, which is necessary info for the automation

Conda packages have their own packaging/versioning strategies and release timelines compared to the individual libraries. How are you thinking about handling that?

@xiangyan99
Copy link
Member

@xiangyan99 I'm working on entirely automating the conda release process. this lets us make service teams tell us whether their packages should be released in a bundle or individually, which is necessary info for the automation

Conda packages have their own packaging/versioning strategies and release timelines compared to the individual libraries. How are you thinking about handling that?

Took offline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Untriaged
Status: No status

Development

Successfully merging this pull request may close these issues.

3 participants