Version Packages#58
Merged
Merged
Conversation
gitsad
approved these changes
Jul 21, 2026
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@mobile-reality/mdma-parser@0.3.0
Minor Changes
cb3cf95: Add the
customcomponent type — a host-extensible escape hatch for components the built-in typesdo not cover. It is a stable envelope rather than a new type per component:
nameselects a variantthe host registered,
propscarries its inputs, andactionswires its events. This keeps the specintent-level while all rendering lives in the host, and — unlike the existing custom-type path — it
is authorable by an LLM, because the envelope is part of the spec every prompt already teaches. A
model cannot invent
type: timer, but it can emittype: customwithname: timeronce the variantappears in the catalog the host passes to
buildSystemPrompt({ customComponents }).CustomComponentSchema(idrequired,namerequired, openpropsrecord, optionalactionsmap), added to the component union,COMPONENT_TYPES, and the schema registry.nameprops validation: the envelope is validated by the union, thenpropsarevalidated against the matching entry in
customSchemas, with errors prefixedprops.*. Anunregistered
namepasses through rather than failing the parse, so a document authored against aricher host still renders elsewhere.
registerCustomComponent()registers a variant's handler and schema together.CustomVariantProvider/useCustomVariants()and aCustomRendererthatfalls back to an inline notice when a
namehas no registered variant, so an unknown variantdegrades visibly instead of rendering nothing.
buildSystemPrompt({ customComponents })renders an## Available Custom Componentscatalog; author, fixer, and agent prompts document the envelopeand the standalone-not-a-form-field rule. Adds prompt variants for gpt-5.6 (sol/terra/luna),
claude-opus-4.8, claude-fable-5, gemini-3.5-flash, and grok-4.5.
The agent prompts also gain an other-tools clause so
generate_mdmadefers to a host's own toolswhen it is imported into an existing tool set, rather than answering requests those tools own.
@mobile-reality/mdma-renderer-react-nativedoes not yet render thecustomtype — documents usingit fall back to the unknown-component path on React Native.
Patch Changes
@mobile-reality/mdma-prompt-pack@0.5.0
Minor Changes
cb3cf95: Add the
customcomponent type — a host-extensible escape hatch for components the built-in typesdo not cover. It is a stable envelope rather than a new type per component:
nameselects a variantthe host registered,
propscarries its inputs, andactionswires its events. This keeps the specintent-level while all rendering lives in the host, and — unlike the existing custom-type path — it
is authorable by an LLM, because the envelope is part of the spec every prompt already teaches. A
model cannot invent
type: timer, but it can emittype: customwithname: timeronce the variantappears in the catalog the host passes to
buildSystemPrompt({ customComponents }).CustomComponentSchema(idrequired,namerequired, openpropsrecord, optionalactionsmap), added to the component union,COMPONENT_TYPES, and the schema registry.nameprops validation: the envelope is validated by the union, thenpropsarevalidated against the matching entry in
customSchemas, with errors prefixedprops.*. Anunregistered
namepasses through rather than failing the parse, so a document authored against aricher host still renders elsewhere.
registerCustomComponent()registers a variant's handler and schema together.CustomVariantProvider/useCustomVariants()and aCustomRendererthatfalls back to an inline notice when a
namehas no registered variant, so an unknown variantdegrades visibly instead of rendering nothing.
buildSystemPrompt({ customComponents })renders an## Available Custom Componentscatalog; author, fixer, and agent prompts document the envelopeand the standalone-not-a-form-field rule. Adds prompt variants for gpt-5.6 (sol/terra/luna),
claude-opus-4.8, claude-fable-5, gemini-3.5-flash, and grok-4.5.
The agent prompts also gain an other-tools clause so
generate_mdmadefers to a host's own toolswhen it is imported into an existing tool set, rather than answering requests those tools own.
@mobile-reality/mdma-renderer-react-nativedoes not yet render thecustomtype — documents usingit fall back to the unknown-component path on React Native.
Patch Changes
@mobile-reality/mdma-renderer-react@0.6.0
Minor Changes
cb3cf95: Add the
customcomponent type — a host-extensible escape hatch for components the built-in typesdo not cover. It is a stable envelope rather than a new type per component:
nameselects a variantthe host registered,
propscarries its inputs, andactionswires its events. This keeps the specintent-level while all rendering lives in the host, and — unlike the existing custom-type path — it
is authorable by an LLM, because the envelope is part of the spec every prompt already teaches. A
model cannot invent
type: timer, but it can emittype: customwithname: timeronce the variantappears in the catalog the host passes to
buildSystemPrompt({ customComponents }).CustomComponentSchema(idrequired,namerequired, openpropsrecord, optionalactionsmap), added to the component union,COMPONENT_TYPES, and the schema registry.nameprops validation: the envelope is validated by the union, thenpropsarevalidated against the matching entry in
customSchemas, with errors prefixedprops.*. Anunregistered
namepasses through rather than failing the parse, so a document authored against aricher host still renders elsewhere.
registerCustomComponent()registers a variant's handler and schema together.CustomVariantProvider/useCustomVariants()and aCustomRendererthatfalls back to an inline notice when a
namehas no registered variant, so an unknown variantdegrades visibly instead of rendering nothing.
buildSystemPrompt({ customComponents })renders an## Available Custom Componentscatalog; author, fixer, and agent prompts document the envelopeand the standalone-not-a-form-field rule. Adds prompt variants for gpt-5.6 (sol/terra/luna),
claude-opus-4.8, claude-fable-5, gemini-3.5-flash, and grok-4.5.
The agent prompts also gain an other-tools clause so
generate_mdmadefers to a host's own toolswhen it is imported into an existing tool set, rather than answering requests those tools own.
@mobile-reality/mdma-renderer-react-nativedoes not yet render thecustomtype — documents usingit fall back to the unknown-component path on React Native.
Patch Changes
@mobile-reality/mdma-runtime@0.4.0
Minor Changes
cb3cf95: Add the
customcomponent type — a host-extensible escape hatch for components the built-in typesdo not cover. It is a stable envelope rather than a new type per component:
nameselects a variantthe host registered,
propscarries its inputs, andactionswires its events. This keeps the specintent-level while all rendering lives in the host, and — unlike the existing custom-type path — it
is authorable by an LLM, because the envelope is part of the spec every prompt already teaches. A
model cannot invent
type: timer, but it can emittype: customwithname: timeronce the variantappears in the catalog the host passes to
buildSystemPrompt({ customComponents }).CustomComponentSchema(idrequired,namerequired, openpropsrecord, optionalactionsmap), added to the component union,COMPONENT_TYPES, and the schema registry.nameprops validation: the envelope is validated by the union, thenpropsarevalidated against the matching entry in
customSchemas, with errors prefixedprops.*. Anunregistered
namepasses through rather than failing the parse, so a document authored against aricher host still renders elsewhere.
registerCustomComponent()registers a variant's handler and schema together.CustomVariantProvider/useCustomVariants()and aCustomRendererthatfalls back to an inline notice when a
namehas no registered variant, so an unknown variantdegrades visibly instead of rendering nothing.
buildSystemPrompt({ customComponents })renders an## Available Custom Componentscatalog; author, fixer, and agent prompts document the envelopeand the standalone-not-a-form-field rule. Adds prompt variants for gpt-5.6 (sol/terra/luna),
claude-opus-4.8, claude-fable-5, gemini-3.5-flash, and grok-4.5.
The agent prompts also gain an other-tools clause so
generate_mdmadefers to a host's own toolswhen it is imported into an existing tool set, rather than answering requests those tools own.
@mobile-reality/mdma-renderer-react-nativedoes not yet render thecustomtype — documents usingit fall back to the unknown-component path on React Native.
Patch Changes
@mobile-reality/mdma-spec@0.4.0
Minor Changes
cb3cf95: Add the
customcomponent type — a host-extensible escape hatch for components the built-in typesdo not cover. It is a stable envelope rather than a new type per component:
nameselects a variantthe host registered,
propscarries its inputs, andactionswires its events. This keeps the specintent-level while all rendering lives in the host, and — unlike the existing custom-type path — it
is authorable by an LLM, because the envelope is part of the spec every prompt already teaches. A
model cannot invent
type: timer, but it can emittype: customwithname: timeronce the variantappears in the catalog the host passes to
buildSystemPrompt({ customComponents }).CustomComponentSchema(idrequired,namerequired, openpropsrecord, optionalactionsmap), added to the component union,COMPONENT_TYPES, and the schema registry.nameprops validation: the envelope is validated by the union, thenpropsarevalidated against the matching entry in
customSchemas, with errors prefixedprops.*. Anunregistered
namepasses through rather than failing the parse, so a document authored against aricher host still renders elsewhere.
registerCustomComponent()registers a variant's handler and schema together.CustomVariantProvider/useCustomVariants()and aCustomRendererthatfalls back to an inline notice when a
namehas no registered variant, so an unknown variantdegrades visibly instead of rendering nothing.
buildSystemPrompt({ customComponents })renders an## Available Custom Componentscatalog; author, fixer, and agent prompts document the envelopeand the standalone-not-a-form-field rule. Adds prompt variants for gpt-5.6 (sol/terra/luna),
claude-opus-4.8, claude-fable-5, gemini-3.5-flash, and grok-4.5.
The agent prompts also gain an other-tools clause so
generate_mdmadefers to a host's own toolswhen it is imported into an existing tool set, rather than answering requests those tools own.
@mobile-reality/mdma-renderer-react-nativedoes not yet render thecustomtype — documents usingit fall back to the unknown-component path on React Native.
@mobile-reality/mdma-attachables-core@0.2.6
Patch Changes
@mobile-reality/mdma-cli@0.2.10
Patch Changes
@mobile-reality/mdma-mcp@0.2.13
Patch Changes
@mobile-reality/mdma-renderer-react-native@0.3.1
Patch Changes
@mobile-reality/mdma-validator@0.3.3
Patch Changes
@mobile-reality/mdma-demo@0.0.16
Patch Changes
@mobile-reality/mdma-demo-native@0.0.6
Patch Changes
mdma-example-agui@0.0.4
Patch Changes