Changes

• kor is now compatible with both pydantic v2 and v1
• pydantic v2 had significant breaking changes w/ respect to v1, so a major version bump was used in kor as a precaution to warn users about potential breaking changes.

Main things to watch out for when bumping to new pydantic version and new kor:

1. Use a default value for any Optional fields if using pydantic v2 for validation.

   :::python class MusicRequest(BaseModel): song: Optional[List[str]] = Field( default=None, description="The song(s) that the user would like to be played." )

2. Kor schema is typed checked using pydantic. Pydantic v2 is stricter, and may catch issues that were hiding in existing user code that was using the kor library.

3. Serialization has not yet been implemented with pydantic v2.

Other changes

node ids are not longer required to be valid identifiers. This helps when using node ids which are attribute names written in other languages (e.g., chinese).

What's Changed

• Update docs to use run by @eyurtsev in https://github.com/eyurtsev/kor/pull/197
• update workflow by @eyurtsev in https://github.com/eyurtsev/kor/pull/208
• Pydantic v1 and v2 support by @eyurtsev in https://github.com/eyurtsev/kor/pull/213
• Fix release workflow by @eyurtsev in https://github.com/eyurtsev/kor/pull/214
• Update notebooks by @eyurtsev in https://github.com/eyurtsev/kor/pull/215
• Update README for pydantic v2 by @eyurtsev in https://github.com/eyurtsev/kor/pull/216
• Update workflow to run pydantic compatibility by @eyurtsev in https://github.com/eyurtsev/kor/pull/217
• Update poetry lock file by @eyurtsev in https://github.com/eyurtsev/kor/pull/218
• Version 1.0.0 release by @eyurtsev in https://github.com/eyurtsev/kor/pull/223

Full Changelog: https://github.com/eyurtsev/kor/compare/0.13.0...1.0.0