fix sha256sum

[akrherz]

Checklist

• [x] Used a personal fork of the feedstock to propose changes
• [x] Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• [x] Re-rendered with the latest conda-smithy (Use the phrase code>@<space/conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• [x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Present pygrib build (linux 64 at least) has jasper pinned at jasper >=1.900.1,<2.0a0, lets see if we can march this forward.

[conda-forge-linter]

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 automated conda-forge-webservice. I tried to rerender for you but ran into some issues, please ping conda-forge/core for further assistance. You can also try re-rendering locally.

[akrherz]

Erm, my guess is that I tried a closed migration. Hmmm

[akrherz]

Oh boy, the pypi release artifact got updated, so updated sha256sum and pinned jasper for all arches to 2.0.14

[akrherz]

@conda-forge-admin, please rerender

[akrherz]

This is all green now, but I have also submitted a formal jasper 2 migration to conda-forge pinning

[akrherz]

Redid this PR to remove the jasper change as bot PR should be incoming. We do need the sha256sum updated, see jswhit/pygrib#191 which is what I think happened.

[github-actions[bot]]

Hi! This is the friendly automated conda-forge-webservice. I tried to rerender for you but ran into some issues, please ping conda-forge/core for further assistance. You can also try re-rendering locally.

[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: passed

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