test pydantic v2

[mikemhenry]

Developers certificate of origin

• I certify that this contribution is covered by the MIT License here and the Developer Certificate of Origin at https://developercertificate.org/.

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.01% 🎉

Comparison is base (ab271ba) 90.99% compared to head (5c311d2) 91.00%.
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #541      +/-   ##
==========================================
+ Coverage   90.99%   91.00%   +0.01%     
==========================================
  Files         114      114              
  Lines        6882     6891       +9     
==========================================
+ Hits         6262     6271       +9     
  Misses        620      620              

Files Changed	Coverage Δ
openfe/protocols/openmm_rfe/equil_rfe_settings.py	100.00% <100.00%> (ø)
openfe/protocols/openmm_utils/omm_settings.py	84.48% <100.00%> (ø)
openfe/setup/ligand_network_planning.py	100.00% <100.00%> (ø)
openfe/tests/setup/test_network_planning.py	100.00% <100.00%> (ø)

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mikemhenry]

This PR now actually sets us to pull in pydantic v2, but we use a pydantic.v1 import so we can support either. Do we want to add one CI job that checks to make sure things pass with pydantic <2? I was thinking that I could add a linux python 3.11 test for that

[richardjgowers]

@mikemhenry yeah a single job for v1 sounds good

[mikemhenry]

Cool I will add that then!

[mikemhenry]

@richardjgowers that worked, it messed up the names of the jobs a bit, is that okay?

[mikemhenry]

I'll do the same for gufe whatever we decide here

[richardjgowers]

@mikemhenry yeah I can't remember if there was a nice way to label what "<2" meant in the build matrix but it's functionally great right now at least