parcels: zarr<3

[VeckoTheGecko]

conda-forge/parcels-feedstock#129 (comment)

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.

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

[VeckoTheGecko]

@ocefpaf Is it an issue that this doesn't also target earlier versions of parcels? Or is it a necessary evil (i.e., that you cant retrospectively add upperbounds for everything as the software sphere moves forward).

[ocefpaf]

@ocefpaf Is it an issue that this doesn't also target earlier versions of parcels? Or is it a necessary evil (i.e., that you cant retrospectively add upperbounds for everything as the software sphere moves forward).

This is kind of a choice of how much patching you want. IMO, patching the latest/most used version is essential, anything beyond that may be too much. Sure, those old version may be broken, but the promise of support is probably long gone, people who really need them can figure out how to downgrade zarr, etc.