ray-packages v2.49.1

[regro-cf-autotick-bot]

It is very likely that the current package version for this feedstock is out of date.

Checklist before merging this PR:

• Dependencies have been updated if changed: see upstream
• Tests have passed
• Updated license if changed and license_file is packaged

Information about this PR:

1. Feel free to push to the bot's branch to update this PR if needed.
2. The bot will almost always only open one PR per version.
3. The bot will stop issuing PRs if more than 3 version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
4. If you want these PRs to be merged automatically, make an issue with @conda-forge-admin,please add bot automerge in the title and merge the resulting PR. This command will add our bot automerge feature to your feedstock.
5. 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 @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

Pending Dependency Version Updates

Here is a list of all the pending dependency version updates for this repo. Please double check all dependencies before merging.

Name	Upstream Version	Current Version
protobuf	32.0

_{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/17425773275 - please use this URL for debugging.}

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

[mattip]

Closing/reopening to try to clear the hung agents: one hung while uploading, the other while building.

[h-vetinari]

You don't need to restart the whole PR, you can just restart the failed jobs if you go to the Checks tab

[mattip]

I tried that, they then hung again [edit: or did not restart]. I am not sure what is going on so i restarted the whole thing

[mattip]

Looking at the failed build log of osx_arm64_python3.12: it started at 8:49, by 14:39 it finished the compilation (i.e. 5h50min). A successful build, say osx_arm64_python3.11 also started at 8:49 and finished compilation at 13:04 (i.e. 4h15m). I wonder why one build took 33% more?

[h-vetinari]

I wonder why one build took 33% more?

Some agents have more powerful CPUs than others, and we have no control over this

[apmorton]

Everything is green; merging