Repository navigation
chore(models): regenerate against pinned spec for media variants - #102
sakinaroufid wants to merge 1 commit into
Conversation
release/2026-08-25 picked up the media variant schemas in 87dd4b1, so regenerating against the pin produces 232 modules where 227 are committed, and the drift check in tests.yml fails. Regenerated with ./generate_models.sh 2026-08-25. Generated output only, nothing hand-edited.
|
Hi @damaz91, tagging you because Universal-Commerce-Protocol/ucp#941 is what moved the pinned branch, so you'll have the most context on whether this output looks right. Quick summary of what happened: Nothing in this repo changed, and I haven't hand-edited anything here; it's purely the generator's output. It comes to six files: If you get a chance, a quick look to confirm they match what you modeled in Universal-Commerce-Protocol/ucp#690 would be great. Thanks! |
Description
CI regenerates the models against the pinned spec and fails if the committed tree differs.
That check is failing on
main.release/2026-08-25picked up the media variant schemas in 87dd4b1 ("feat(media): modelimage, video, external video, and 3D variants (#690) (#941)"), so regenerating against the
pin now produces 232 modules where 227 are committed:
This commit is that output, unedited:
media.pygains thePreviewmodel and the current descriptions. The committed copypredates the backport.
media_image.py,media_video.py,media_external_video.py,media_model_3d.pyandmedia_source.pyare new.Post-processing patched its usual 36 modules, so the generated constraints are intact.
Category (Required)
ucp-schematool (resolver, linter, validator). (Requires Maintainer approval)Generated output only. No pipeline, schema or public API changes.
Related Issues
None.
Checklist
!for breaking changes).No new test or docs: the assertion this restores is the existing model-drift job in
tests.yml, which compares the committed tree against a fresh regeneration.