Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maintenance: Bump pydantic to v2 and adapt breaking changes #8

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

josumoreno-BP
Copy link

@josumoreno-BP josumoreno-BP commented Apr 26, 2024

Hello,

We were using this project but recently we migrated some other project to use pydantic v2 so I'm forced to do so on this one.

The most "controversial" ones could be the change of ref_block_num and ref_block_prefix types to int on LinkedTransaction because it seems they were wrong and Array model validator raising ValueError instead of TypeError (pydantic v1 was allowing it but v2 does not)

I also seized the opportunity to group pyproject's dev dependencies into a single group.

Hope you can release a new version with these changes soon.

Thanks

@josumoreno-BP josumoreno-BP force-pushed the migrate/pydantic branch 2 times, most recently from 51562a5 to 48c4201 Compare April 26, 2024 09:47
@robrigo
Copy link

robrigo commented Jul 15, 2024

Thanks for the updates, I will look into testing and cutting a release for this soon.

@heckad
Copy link

heckad commented Dec 4, 2024

@robrigo, any news?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants