Un-pin Pydantic

[SimonBoothroyd]

Checklist

• Used a personal fork of the feedstock to propose changes
• Bumped the build number (if the version is unchanged)
• Reset the build number to 0 (if the version changed)
• Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
• Ensured the license file is being packaged.

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• No valid build backend found for Python recipe for package openff-bespokefit using pip. Python recipes using pip need to explicitly specify a build backend in the host section. If your recipe has built with only pip in the host section in the past, you likely should add setuptools to the host section of your recipe.

[SimonBoothroyd]

@mattwthompson I think 0.3.0 has the try / catch to handle v1 and v2 right?

[SimonBoothroyd]

@conda-forge-admin, please rerender

[j-wags]

Checking pydantic 2 compatibility here openforcefield/openff-bespokefit#357

[j-wags]

The compatibility checks above raise a bunch of errors, even when trying a range of versions of OpenFF ecosystem packages. So I don't think this is ready for release.

[mattwthompson]

This should work in 0.3.0, yeah: openforcefield/openff-bespokefit@3611f36

[j-wags]

@mattwthompson - It's possible I'm overlooking something, but bespokefit CI fails if I bring in pydantic 2. Could you clarify?

[mattwthompson]

Something unexpected is going on: openforcefield/openff-bespokefit#358