Missing PyPi releases for updated azure-storage-{blob,file-share,queue} #49652

Activity

1. github-actions commented on Oct 22, 2026

   

   github-actionsBot

   on Oct 22, 2026 – with GitHub Actions

   Contributor

   More actions

   Thank you for your feedback. Tagging and routing to the team member(s) best able to assist.

   //cc: Jacob Lauzon (@jalauzon-msft) vincenttran-msft Peter Wu (@weirongw23-msft) anjaliratnam-msft
2. github-actions commented on Oct 22, 2026

   

   github-actionsBot

   on Oct 22, 2026 – with GitHub Actions

   Contributor

   More actions

   🎯 Agentic Issue Triage

   Summary: The reporter notes that new git tags exist for azure-storage-blob, azure-storage-file-share, and azure-storage-queue, but corresponding releases were not published to PyPI, and asks that the missing releases be uploaded.

   📋 Issue Details

   Package: azure-storage-blob, azure-storage-file-share, azure-storage-queue (specific versions not stated by reporter)
   Affected API: N/A — packaging/release process, not a code-level API issue
   Scenarios:

   • Reporter observes new version tags in the git repository for the three storage packages
   • No matching release was found on PyPI for those tagged versions

   Root ask: Publish the missing PyPI releases for the tagged versions of azure-storage-blob, azure-storage-file-share, and azure-storage-queue.

   🔎 Debugging / Reproduction Notes

   This is a release/publishing process question rather than a code defect. No closely matching open duplicate issue was found via search (similar packaging/linting issues exist for these packages, e.g. #48139, #48140, #45377, but none report missing PyPI releases specifically).

   Suggested investigation steps:

   1. Confirm which git tags for azure-storage-blob, azure-storage-file-share, and azure-storage-queue are missing a corresponding PyPI release.
   2. Check internal release pipeline status/logs for those versions to determine whether publishing failed or is pending.
   3. If release was intentionally held back (e.g. due to a blocking issue), communicate status to the reporter; otherwise trigger/re-run the release pipeline.

   🏷️ Label Confidence

   • Category: Client — the packages involved (azure-storage-blob, azure-storage-file-share, azure-storage-queue) are data-plane SDK libraries, not azure-mgmt-* management packages.
   • Service: Storage — all three packages live under /sdk/storage and map to the Storage service area.
   • Confidence: High — the issue explicitly names the three packages, there is no ambiguity about the service area, and the category is clearly data-plane.

   👥 Owner Routing

   • Matched CODEOWNERS entry: # ServiceLabel: %Storage (line 772) — scanning bottom-to-top, this was the first entry whose service label matched "Storage".
   • AzureSdkOwners: none listed
   • ServiceOwners: @jalauzon-msft, @vincenttran-msft, @weirongw23-msft, @anjaliratnam-msft
   • Routing action: Added "Service Attention" and "needs-team-attention" labels; issue left unassigned; ServiceOwners pinged via routing comment.
   • Scan notes: No other ServiceLabel entries for "Storage" were encountered before this match during the bottom-to-top scan.

   Generated by Agentic Triage for #49652 · copilot · sonnet50 · 22 AIC · ⌖ 0.643 AIC · ⊞ 13K · ◷
3. github-actions

   added

   StorageStorage Service (Queues, Blobs, Files)Storage Service (Queues, Blobs, Files)

   questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

   Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.

   ClientThis issue points to a problem in the data-plane of the library.This issue points to a problem in the data-plane of the library.

   customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.

   needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK team

   on Oct 22, 2026
4. Jacob Lauzon (jalauzon-msft)

   self-assigned this

   on Oct 23, 2026
5. jalauzon-msft commented on Oct 23, 2026

   

   Jacob Lauzon (jalauzon-msft)

   on Oct 23, 2026

   Member

   More actions

   Hi John Paul Adrian Glaubitz (@glaubitz), there was an issue in our release process, so the release did not complete. We are working to resolve the issue and should have the new versions published soon. Please do not rely on the new versions on GitHub as they will soon be overwritten.
6. jalauzon-msft commented on Oct 30, 2026

   

   Jacob Lauzon (jalauzon-msft)

   on Oct 30, 2026

   Last edited by jalauzon-msft

   Member

   More actions

   These have been released to PyPi now. Note the previous release was deleted and re-created with a slightly different commit (no functional difference)
7. Jacob Lauzon (jalauzon-msft)

   closed this as completedon Oct 30, 2026