Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 673fb3496d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| @@ -402,7 +401,7 @@ def create_lti_configuration( | |||
| _content_type: Optional[StrictStr] = None, | |||
| _headers: Optional[Dict[StrictStr, Any]] = None, | |||
| _host_index: Annotated[StrictInt, Field(ge=0, le=0)] = 0, | |||
| ) -> CreateLtiConfiguration200Response: | |||
| ) -> LtiConfiguration: | |||
There was a problem hiding this comment.
Keep the old response model importable in the patch release
When a 2.0.1 consumer imports CreateLtiConfiguration200Response—as the generated documentation instructed—or uses it in annotations, upgrading to 2.0.2 now raises ModuleNotFoundError or ImportError because this commit deletes both the model module and its package exports while changing the operation to return LtiConfiguration. Since this is a patch release, retain a compatibility alias for the old public model name while using LtiConfiguration for deserialization.
Useful? React with 👍 / 👎.
Automated regeneration from
FlatIO/api-reference@v2.26.2.Non-breaking: auto-merges once the required checks pass (FR-007e).