fix: patch rubin-sim 2.2.0 for numpy 2

[beckermr]

Checklist

• Used a static YAML file for the patch if possible (instructions).
• Only wrote code directly into generate_patch_json.py if absolutely necessary.
• Ran pre-commit run -a and ensured all files pass the linting checks.
• Ran python show_diff.py and posted the output as part of the PR.
• Modifications won't affect packages built in the future.

xref: conda-forge/rubin-sim-feedstock#59

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

[jakirkham]

Thanks Matt! 🙏

It looks like PR ( conda-forge/rubin-sim-feedstock#59 ) is still open. Do you plan to merge that?

Recall we have usually made the fix in the latest build and repodata patched older ones

[beckermr]

diff is correct

noarch::rubin-sim-2.2.0-pyhd8ed1ab_0.conda
-    "numpy",
+    "numpy >=2",

[conda-forge-admin]

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

I considered the following status checks when analyzing this PR:

• linter: passed
• github-actions: passed

Thus the PR was passing and merged! Have a great day!

[beckermr]

I will leave the merging of that PR up to @rhiannonlynne. The next version of this package doesn't need the numpy >=2 constraint and so unless we need another build of 2.2.0, there is no reason to merge it.

[jakirkham]

Ok at least my understanding of why we add the pin to the recipe is in the event the same version of the package needs to be rebuilt for another reason. Having the pin there ensures we don't forget this constraint when addressing a different issue. Something that is especially helpful if there is time pressure

[beckermr]

Right except that for the next version of the code, this pin will be wrong and we'll need to remove it again. IDK what is best to do here. It is a one-time case I think.

[jakirkham]

It would be ok to drop it then

Would Grayskull pick up this change for you?