Align diffusion bundles with metadata.json v0.2 schema#33
Merged
Conversation
Diffusion exports now produce metadata.json (same v0.2 schema as LLM and segmenter bundles) instead of the legacy pipeline.json format. The pipeline config lives under a "diffusion" key in metadata.json, alongside standard fields (kind, name, assets, source, compression, compilation) shared by all bundle types. Swift runner: reads metadata.json first. If only pipeline.json is found, prints a deprecation warning to stderr and loads it as a fallback. pipeline.json support will be removed in 30 days. Closes #TBD (deprecation tracking issue)
stikves
force-pushed
the
sukru/diffusion-metadata-alignment
branch
from
602d0cc to
b949460
Compare
kevchengcodes
approved these changes
Jun 12, 2026
carinapeng
reviewed
Jun 12, 2026
carinapeng
approved these changes
Jun 12, 2026
carinapeng
left a comment
carinapeng
left a comment
Contributor
There was a problem hiding this comment.
Happy to merge this, but some considerations for more validation as we go through different iterations of assets, would prefer to have it in this PR or a follow up
stikves
force-pushed
the
sukru/diffusion-metadata-alignment
branch
from
88b84db to
8ddbdd1
Compare
stikves
added a commit
to stikves/coreai-models
that referenced
this pull request
Jun 13, 2026
Diffusion exports now produce metadata.json (same v0.2 schema as LLM and segmenter bundles) instead of the legacy pipeline.json format. The pipeline config lives under a "diffusion" key in metadata.json, alongside standard fields (kind, name, assets, source, compression, compilation) shared by all bundle types. Swift runner: reads metadata.json first. If only pipeline.json is found, prints an error, which will be removed in upcoming weeks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Diffusion exports now produce metadata.json (same v0.2 schema as LLM and segmenter bundles) instead of the legacy pipeline.json format.
The pipeline config lives under a "diffusion" key in metadata.json, alongside standard fields (kind, name, assets, source, compression, compilation) shared by all bundle types.
Swift runner: reads metadata.json first. If only pipeline.json is found, prints a deprecation error to stderr and asks for a clean export, the message will be removed in upcoming weeks.