only run dev with newest python version

[mikemhenry]

Description

To save some compute time/carbon, we are only going to test dev with the latest python version.

Motivation and context

Resolves #???

How has this been tested?

Change log

[ijpulidos]

In this case we are not using the dev versions from OpenMM, since we currently rely on the matrix.openmm option to install them in

perses/.github/workflows/CI.yaml

Line 55 in c7971db

case ${{ matrix.openmm }} in

[ijpulidos]

I just double checked that this is indeed the case for example in https://github.com/choderalab/perses/actions/runs/4295333336/jobs/7485595343#step:7:236

[ijpulidos]

Oh, but according to documentation using include should work for this, exactly as you proposed it. Not sure why it isn't working as expected then.

[mikemhenry]

I think I fixed it, the problem (I think) was the lack of telling micromamba to reinstall if the package is in the env. It would be faster and better to use this kind of syntax to install openmm:

extra-specs: |
  python=${{ matrix.python-version }}

but that would then crash on "dev" but would work for the other openmm version strings... but I have an idea!

[codecov]

Codecov Report

Merging #1165 (24423b9) into main (c7971db) will not change coverage.
The diff coverage is n/a.

[ijpulidos]

This looks good, thanks!

I think eventually we do want to think about not having to manually change the openmm dev version every time there's a new build.