Skip to content

Conversation

@flavienSindou
Copy link
Contributor

@flavienSindou flavienSindou commented Feb 14, 2025

Proposed changes

  • Loose pydantic versions in dependencies

Related issues

Checklist

  • I consider the submitted work as finished
  • I tested the code for its functionality
  • I wrote test cases for the relevant uses case
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality

Further comments

Notion page with tests procedure and results:
https://www.notion.so/filigran/Loose-Pydantic-requirements-in-opencti-python-client-19a8fce17f2a801788d1d593c4c2549b?pvs=4#19a8fce17f2a8112b3a4c74af830df8a

@flavienSindou flavienSindou self-assigned this Feb 14, 2025
@flavienSindou flavienSindou linked an issue Feb 14, 2025 that may be closed by this pull request
@flavienSindou flavienSindou added this to the Bugs Backlog milestone Feb 14, 2025
@flavienSindou flavienSindou added the filigran team use to identify PR from the Filigran team label Feb 14, 2025
@aHenryJard aHenryJard self-assigned this Feb 14, 2025
@flavienSindou flavienSindou merged commit 4dd8af6 into master Feb 17, 2025
6 checks passed
@SamuelHassine SamuelHassine removed this from the Bugs Backlog milestone Feb 17, 2025
@aHenryJard aHenryJard changed the title [deps]: Loose pydantic versions [deps]: Loose pydantic versions (#840) Feb 18, 2025
@labo-flg labo-flg modified the milestone: Release 6.5.3 Feb 20, 2025
@SamuelHassine SamuelHassine deleted the issue/840-pydantic-requirements-too-strict branch April 12, 2025 21:57
aHenryJard pushed a commit to OpenCTI-Platform/opencti that referenced this pull request Nov 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

filigran team use to identify PR from the Filigran team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Pydantic requirements too strict

6 participants