Update pins for Azure Storage January 2026 release

[jdblischak]

xref: Azure/azure-sdk-for-cpp#6895, conda-forge/azure-storage-common-cpp-feedstock#28, conda-forge/azure-storage-blobs-cpp-feedstock#25, conda-forge/azure-storage-files-shares-cpp-feedstock#23, conda-forge/azure-storage-files-datalake-cpp-feedstock#24, conda-forge/azure-storage-queues-cpp-feedstock#17, #7856, #6471

cc: @jjerphan, @h-vetinari, @teo-tsirpanis, @conda-forge/azure-storage-common-cpp

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/20962260311. Examine the logs at this URL for more detail.}

[jjerphan]

Thank you, @jdblischak.

LGTM (I did not see #7856 initally).

I left comments and approval on feedstocks' PRs, I let you proceed with merging them first.

[jdblischak]

I left comments and approval on feedstocks' PRs, I let you proceed with merging them first.

This time I was going to try and combine the version bumps and the migration PRs

[jjerphan]

Hum, mustn't we first have merged all the PRs of feedstocks which have been linked? :)

[h-vetinari]

Hum, mustn't we first have merged all the PRs of feedstocks which have been linked? :)

Nope, because of exclude_pinned_pkgs: false, those feedstocks will get a migration PR themselves; also you had 👍'd the comment how @jdblischak is planning to combine the migration (PRs) with the version bumps.

[jjerphan]

Nevermind, I misunderstood #8132 (comment) (I thought it meant waiting for all feedstocks to have their version bumped before starting the migration, and I did not know that starting the migration before was possible).

[jdblischak]

As I see it, there are two main strategies for pushing through the updates and migrations for these azure feedstocks:

1. Merge each update PR as it comes. AFAIU as long as it compiles, it is fine (even if the upstream devs have bumped the minimum required version in the vcpkg.json). Then the combined migration PR needs to designate all the auto-opened single migration PRs to close. I see two main downsides to this approach: 1) it won't work if indeed one of the packages can't be built without updated dependencies, 2) it unnecessarily builds and uploads what are essentially unusable conda binaries (since they are pinned to the previous versions of all its dependencies). This is what I did last time in Migrate azure_core_cpp 1.16.1 and latest storage packages #7856

2. Delay merging each update PR. Instead allow the combined migration to send migration PRs to each feedstock (because we set exclude_pinned_pkgs: false), and then combine the bot update PR with the bot migration PR. I like this approach because it is cleaner (ie uploads fewer conda binaries). However, it is admittedly more work. Combining the two bot PRs manually is tedious since they both bump the build number and rerender. Depending on how it goes this time, I may decide to switch back to the other strategy to save time.

[jdblischak]

Depending on how it goes this time, I may decide to switch back to the other strategy to save time.

So far it is off to a bad start. The migration is blocked because the bot can't bot can't solve the environment:

linux_64_: Cannot solve the request because of: No candidates were found for azure-storage-common-cpp 12.12.0.*.

At minimum I'll need to merge the azure-storage-common-cpp 12.12.0 update PR first. Then we'll see if the migration can continue.

[h-vetinari]

Yeah, the migrator needs at least one library to have been successfully built to solve a child feedstock.

[jdblischak]

While I like that my current strategy avoids uploading unnecessary conda binaries, everything else about it is decidedly worse. Combining the version bump and migration PRs requires more manual intervention, we still have to merge the first package in the dependency network (in this case it was storage-common but would typically be core), and individual PRs to update the pins are still opened (and thus will need to be manually closed).

So going forward, as long as the CI passes, I think we should follow the strategy of #7856: merge all the version bump PRs, create a combined migration PR, list all the independent version bump PRs to be auto-closed.

[jdblischak]

as long as the CI passes

Note that for this migration, the datalake 12.14.0 version bump PR failed without its updated dependencies, so it would have had to have waited for the combined migration regardless (conda-forge/azure-storage-files-datalake-cpp-feedstock#24 (comment), conda-forge/azure-storage-files-datalake-cpp-feedstock#25)

[h-vetinari]

@jdblischak, I think the synthesis here is that the optimum is somewhere in the middle, and may not be the same from migration to migration. Personally, I think it'd be viable to merge the version updates that pass, and leave the ones open that don't, before starting the migration (for example).

[jdblischak]

Quick status update on the azure storage migration:

• The migration PR for arrow-cpp-feedstock (Rebuild for Azure Storage January 2026 release arrow-cpp-feedstock#1909) is stalled until the feedstock CI is fixed (Fix CI arrow-cpp-feedstock#1913)
• As luck would have it, new versions of azure-core-cpp (azure-core-cpp v1.16.2 azure-core-cpp-feedstock#34) and azure-identity-cpp (azure-identity-cpp v1.13.3 azure-identity-cpp-feedstock#23) were released. I will combine these into a single migration, but only after this current one is completed

[jdblischak]

Status updates:

• The arrow-cpp-feedstock CI was fixed (Fix CI arrow-cpp-feedstock#1913) and azure migration PR merged (Rebuild for Azure Storage January 2026 release arrow-cpp-feedstock#1909)
• Only arcticdb-feedstock remains (Rebuild for Azure Storage January 2026 release arcticdb-feedstock#554)
• The migration has been closed (Close out migration for azure_storage_2026_01 #8163)
• I'll send a PR for the core/identity migration next week

Thanks @h-vetinari and @jjerphan!