Skip to content

chore: regenerate SDK from updated platform schemas - #4

Closed
github-actions[bot] wants to merge 1 commit into
masterfrom
chore/regenerate-sdk
Closed

github-actions[bot] wants to merge 1 commit into
masterfrom
chore/regenerate-sdk

Conversation

@github-actions

@github-actions github-actions Bot commented Oct 7, 2026

Copy link
Copy Markdown

Auto-generated SDK regeneration

This PR was opened automatically by the Regenerate SDK workflow
(regenerate_sdk.yml).

What triggered this?

The workflow ran against the latest commit of
openedx/openedx-platform.

Platform commit the schemas were taken from:
532c1af404da1e6aba4c1748cfc34c77a9645a5d

What changed?

The SDK was regenerated from docs/lms-openapi.yaml and docs/cms-openapi.yaml
using openapi-python-client. Ruff was then run to
auto-fix any lint issues introduced by the generator.

Review checklist

  • Review the diff carefully — auto-applied bug fixes are in
    postprocess_sdk.py. Make sure the regeneration did not
    accidentally revert intentional post-processing patches.
  • Confirm the schema versions look correct (check file
    headers).
  • Run the test suite locally if the diff is large.

@Faraz32123

Copy link
Copy Markdown
Collaborator

I had just run the SDK workflow manually to test the PR generation. It is working as expected!

Closing this PR for now!
As openedx/openedx-platform#39192 isn't merged yet. Once that is merged. We will manually regenerate openedx-platform schema through this platform workflow Link. Then merge that schema update PR in openedx-platform. And then we can retirgger this SDK workflow to regenerate SDK.

@Faraz32123 Faraz32123 closed this Oct 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant