chore: Updated to 1.76.0

[MartinHoloubekQC]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[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-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ 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/19963614309. Examine the logs at this URL for more detail.}

[h-vetinari]

What do you need 1.76 for? We're currently waiting for grpc to finally become compatible with contemporary protobuf (we couple abseil/grpc/protobuf migrations, because otherwise we have to keep migrating all the time). See #411 & grpc/grpc#40639

IF there's a strong need for newer grpc we can probably make an exception and migrate only abseil+grpc, but I'm not a big fan of that idea, because it's a lot of work that usually I end up doing (like shepherding the still-open migration to completion).

[MartinHoloubekQC]

What do you need 1.76 for? We're currently waiting for grpc to finally become compatible with contemporary protobuf (we couple abseil/grpc/protobuf migrations, because otherwise we have to keep migrating all the time). See #411 & grpc/grpc#40639

IF there's a strong need for newer grpc we can probably make an exception and migrate only abseil+grpc, but I'm not a big fan of that idea, because it's a lot of work that usually I end up doing (like shepherding the still-open migration to completion).

Thanks for your comment @h-vetinari. We need a more recent version (>= 1.75.1) both for google-cloud-documentai and other 3.14+ compatible deps. Naturally, I assumed we can skip 1.75 and move straight on to 1.76. Let me know what you think about this. But having 1.75.1 would be greatly appreciated.

[xhochy]

IF there's a strong need for newer grpc we can probably make an exception and migrate only abseil+grpc, but I'm not a big fan of that idea, because it's a lot of work that usually I end up doing (like shepherding the still-open migration to completion).

We need that, so I would also volunteer shepherding. I will take a look at the build here and look after the old migration.

[h-vetinari]

It looks like grpc 1.77 will have the required fix for newer protobuf: grpc/grpc@e153b5a. Normally grpc releases is on a 6-8 weeks schedule, and 1.77 is already overdue. I'd suggest to wait for 1.77 and then migrate this together with protobuf v33 and newest abseil.

[h-vetinari]

I will take a look at the build here and look after the old migration.

In any case, thanks a lot for fixing up the stragglers of the existing migration! 🙏

[h-vetinari]

In the meantime we can get this back to green. In #413 there were some remaining windows issues (almost certainly due to missing DLL exports) that need fixing. This PR should be rebased on that.