numba 0.55.0 on `defaults` doesn't constrain numpy as expected

When using Conda to create an environment with both Numba and NumPy, I notice that the linux-64 numba 0.55.0 package hosted on defaults doesn’t respect the max version constraint for NumPy like the conda-forge package does; this means it is possible to create an environment with numba 0.55 and numpy 1.22, which results in an ImportError when trying to import numba:

$ mamba create -n test numba=0.55 numpy=1.22
...
  + numba                0.55.0  py310h00e6091_0      pkgs/main/linux-64       Cached
  + numpy                1.22.1  py310h454958d_0      conda-forge/linux-64     Cached

If we limit the environment creation to only use conda-forge, this constraint is properly respected:

$ mamba create --override-channels -c conda-forge -n test numba=0.55 numpy=1.22
...
Encountered problems while solving:
  - package numba-0.55.0-py37h2d894fd_0 has constraint numpy >=1.18,<1.22 conflicting with numpy-1.22.0-py310h454958d_0

Is this different behavior between the two packages expected? I notice that before, the defaults hosted packages seemed to respect this constraint:

$ mamba create --override-channels -c defaults -n test numba=0.54 numpy=1.21
...
Encountered problems while solving:
  - package numba-0.54.1-py37h51133e4_0 has constraint numpy >=1.17,<1.21 conflicting with numpy-1.21.2-py310h20f2e39_0

For context, I observed this issue in https://github.com/dask-contrib/dask-sql/pull/383 - here is an example of potential downstream failures that can occur as a result of this.

[esc]

@charlesbluca thank you, I can confirm this, but I do need to add -c conda-forge for it to resolve as 1.22 isn’t available from defaults at the time of writing:

conda create -c conda-forge -n testxyz numba=0.55 numpy=1.22

[esc]

@charlesbluca I have forwarded this to the team that does defaults.