Use script to update version SHA

[AchimGaedkeLynker]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• 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.

Fixes #236, Would wish there was an automated way doing this...
Maybe this could help? https://rattler.build/latest/build_options/#post-processing-of-the-package-contents-experimental

[AchimGaedkeLynker]

@conda-forge-admin, please rerender

[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]

I took the liberty of changing the patch to a script, following @apmorton's idea of getting the SHA.

[achimgaedke]

@conda-forge-admin, please rerender

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-webservice.

I tried to rerender for you, but it looks like there was nothing to do.

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

[AchimGaedkeLynker]

Ok, I've tried exponential backup - no success, so we might want:

• https://docs.github.com/en/rest/using-the-rest-api/rate-limits-for-the-rest-api?apiVersion=2022-11-28#exceeding-the-rate-limit or
• https://docs.github.com/en/rest/using-the-rest-api/best-practices-for-using-the-rest-api?apiVersion=2022-11-28#make-authenticated-requests

[AchimGaedkeLynker]

I'm a little confused about the flakiness of the azure build machines. Initially I thought the github rate limiting is the only problem, so I addressed it.

In an early iteration I printed a rate limiting header:

2025-09-27T03:08:01.6021470Z  │ │ X-RateLimit-Limit: 60
2025-09-27T03:08:01.6032830Z  │ │ X-RateLimit-Remaining: 0
2025-09-27T03:08:01.6038990Z  │ │ X-RateLimit-Reset: 1758942812
2025-09-27T03:08:01.6040680Z  │ │ X-RateLimit-Resource: core
2025-09-27T03:08:01.6055410Z  │ │ X-RateLimit-Used: 60

indicating that only 60 calls per hour are allowed. That's daunting.

Maybe we can find some github tokens/credentials to use? I've looked at the environment keys, nothing obvious here.
Might be worth checking the git config.

[mattip]

I'm not seeing failures due to rate-limited timeouts. I see a single failure on windows with python3.10

Installing test environment
 │  Successfully updated the test environment
 │ Testing commands:
 │ (ray-packages-feedstock) (ray-packages-feedstock) %SRC_DIR%>IF "" == "" (
 │  
 │  call "%SRC_DIR%\build_env.bat" 
 │ ) 
 │ (ray-packages-feedstock) (ray-packages-feedstock) %SRC_DIR%>python -c "import ray; ray.init(include_dashboard=False)" 
 │ 2025-09-28 01:54:09,167	INFO worker.py:1951 -- Started a local Ray instance.
 │ [2025-09-28 01:54:10,470 E 4840 7992] core_worker_process.cc:232: Failed to register worker to Raylet: IOError: Unknown error worker_id=01000000ffffffffffffffffffffffffffffffffffffffffffffffff

Does the rate limiting only happen when I push a commit to allow the github CIrun runners to proceed? I cannot see the azure CI run log from bf1bfb8.

[AchimGaedkeLynker]

I'm not seeing failures due to rate-limited timeouts.

Yeah, I found them appear in an "all or nothing" fashion. Sounds like a "noisy neighbor".

[mattip]

Gahh. Rerendering updated action/checkout to v5, which does not yet work on the cirun images. Reverting.

[AchimGaedkeLynker]

🎉 - thanks a lot! This was definitely much more laborious than I imagined.