feat(definitions): reject publish when allowedAssemblies don't resolve

feat(definitions): reject publish when allowedAssemblies don't resolveburgan-tech/vnext #1069 · 3 diagrams

◈ Rendered by PR Lens · crafted with ❤️ by the Coldtea team

100%

01 / 05Publish now rejects unresolvable assembliesPublishing a component with unknown assemblies returns 400 instead of failing during workflow execution. calls and rejects unresolvable entries in +103 −0.
02 / 05Assembly catalog added to resolve referencesA new catalog interface checks names against framework libraries and mounted plugin directories. checks assembly availability via SandboxedReferenceSet in +12 −0.
03 / 05Validator processor now calls catalog checkThe processor runs the publish check for flows, tasks, functions, and extensions. checks allowed assemblies on definitions in +12 −2.
04 / 05Migration rule added for assembly validationDocuments that publishing fails with 400 when an allowed assembly name does not resolve. records the new publish validation behavior in +11 −0.
05 / 05Everything this change touchedValidation rules, the assembly catalog, and migration guidance in one view.

esc to leave