ENV: fix conda-forge name for myst-parser

There was a typo introduced in !1324 (merged).

This MR fixes it, we should probably add a test that the containers can build properly from the environment file. I wonder if it's possible to verify that the yaml file can be resolved.

This is the feedstock for this package, https://github.com/conda-forge/myst-parser-feedstock.

added <10 lines Bug CI Infrastructure labels

changed the description

changed milestone to %2.3.0

There is a --dry-run option in conda/mamba, we might be able to use that to check the file. It seems to return 127 when it fails and 0 when it can resolve all the dependencies.

approved this merge request

added 1 commit

• 8c862943 - MAINT: try adding mamba dry run test

Compare with previous version

reset approvals from @michael.williams by pushing to the branch

added 1 commit

• 03e385d4 - CI: fix environment file

Compare with previous version

added 1 commit

• 7ace528a - CI: fix python version

Compare with previous version

resolved all threads

approved this merge request

approved this merge request

added 5 commits

• 6d833562 - 1 commit from branch master
• 00b51088 - ENV: fix conda-forge name for myst-parser
• b694fb80 - MAINT: try adding mamba dry run test
• 58558571 - CI: fix environment file
• 960a288b - CI: fix python version

Compare with previous version

merged