Update deps

[dhirschfeld]

Checklist

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

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

[dhirschfeld]

@conda-forge-admin, please rerender

[dhirschfeld]

xref:

• https://github.com/arviz-devs/arviz/blame/v0.12.1/requirements.txt
• Unpin typing_extensions arviz-devs/arviz#1948

[dhirschfeld]

Ping @conda-forge/arviz! It would be great to get this merged as it's preventing me from installing pymc.

[dhirschfeld]

Hi @canyon289 👋,
When you publish a new package with the same version you need to bump the build number:

I'm not entirely sure that's the reason that the package didn't upload:
https://anaconda.org/conda-forge/arviz/files

...but even if it did upload, mamba/conda wouldn't necessarily choose to install it as (IIUC) the resolution between two packages with the same version and build number would resort to alphabetical which would depend on the random build string.