-
Notifications
You must be signed in to change notification settings - Fork 421
docs(bedrock_agents): remove Pydantic v1 recommendation #6468
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
docs(bedrock_agents): remove Pydantic v1 recommendation #6468
Conversation
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
Hey @konokenj! Thanks a lot for fixing the documentation! Hey @anafalcao, can you please open an issue and link it here? Also, please review the PR. |
Hey @konokenj and @leandrodamascena ! Thanks for the contribution here. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! Thanks again
b5f6bec
into
aws-powertools:develop
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |
|
* docs: Remove recommend for Pydantic v1 which not supported in v3 * remove pydantic v1 from rest api doc --------- Co-authored-by: Ana Falcão <[email protected]> Co-authored-by: Ana Falcao <[email protected]> Co-authored-by: Leandro Damascena <[email protected]>
Issue number: #6476
Summary
Remove the statement recommending Pydantic v1 from the Bedrock Agents documentation. Lambda PowerTools is now able to generate OpenAPI schemas for Bedrock Agents using Pydantic v2 by #5156.
Changes
User experience
Users will be able to avoid wasting time by installing Pydantic v1 according to the documentation.
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.