Skip to content

Conversation

@yankinmax
Copy link
Contributor

@yankinmax
Copy link
Contributor Author

@lmignon Can you pls approve the running workflow to finish with the checks?

@yankinmax yankinmax force-pushed the 15.0-mig-pydantic branch 5 times, most recently from c04a900 to 13cc09d Compare December 1, 2021 13:53
@gurneyalex
Copy link
Member

@yankinmax can you rebase?

@gurneyalex
Copy link
Member

@yankinmax I pushed the last fix from 14.0 on your branch

@yankinmax
Copy link
Contributor Author

@yankinmax I pushed the last fix from 14.0 on your branch

thanks

@yankinmax
Copy link
Contributor Author

@gurneyalex as I correctly understand we're waiting till pydantic will land into V14, yes?

@lmignon
Copy link
Contributor

lmignon commented Feb 2, 2022

@yankinmax @gurneyalex The initial PR is now closed. See #218 (comment) for the motivations. Don't be afraid, the current approach is replaced by a more generic one.

@github-actions
Copy link

github-actions bot commented Jun 5, 2022

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 5, 2022
@lmignon
Copy link
Contributor

lmignon commented Jun 15, 2022

pydantic is now available into 15.0 based on python lib extendable_pydantic

@lmignon lmignon closed this Jun 15, 2022
@yankinmax
Copy link
Contributor Author

thanks a lot @lmignon

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants