Rebuild for libabseil20230802_libgrpc157_libprotobuf4234

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update libabseil20230802_libgrpc157_libprotobuf4234.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase code>@<space/conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/6137074122, please use this URL for debugging.}

[conda-forge-webservices[bot]]

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) and found it was in an excellent condition.

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: failed

Thus the PR was not passing and not merged.

[hmaarrfk]

@conda-forge-admin please rerender

[github-actions[bot]]

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[hmaarrfk]

@h-vetinari was it expected to fail for this use case? I had to manually trigger a change in the recipe. LMK.

I feel like we should remove the SDK stuff from the migrator since it won't be "permanent"

[h-vetinari]

@h-vetinari was it expected to fail for this use case? I had to manually trigger a change in the recipe. LMK.

Well, the problem was that the SDK was non-empty with a value that was lower than the deployment target.

I feel like we should remove the SDK stuff from the migrator since it won't be "permanent"

I'm following @isuruf's guidance here. It's not yet clear to me if at the end of the migration, the global pinning will get bumped to 10.13 or not. Or we keep the migration open until the stdlib-jinja is in place.

[hmaarrfk]

got it.