conda install creates wrong env entry

I recently upgraded from Orekit 10 to 11, and noticed that when I export the environment to a yml file, conda places Orekit under the "pip" section (rather than as a conda package). As a result, when trying to recreate the environment from the yml, conda fails. To reproduce:

$ conda create --name orekit
$ conda activate orekit
$ conda install -c conda-forge orekit
$ conda env export > orekit_env.yml

When examining the yml, "orekit==11.3.2" is listed under "pip"

$ conda activate base
$ conda env remove --name orekit
$ conda env create -f orekit_env.yml

=> Pip subprocess error:
ERROR: Could not find a version that satisfies the requirement orekit==11.3.2
ERROR: No matching distribution found for orekit==11.3.2

Editing the yml to move "orekit==11.3.2" from "pip" to the "conda" section fixes the problem, and the setup completes successfully. Is this a problem with how orekit is packaged/distributed on conda-forge?