Release v3.52.0

cratis render can now render a ui profile that names a custom runtime package, with no Studio: the application approves the package with --package-set, and the rendered React application installs, loads and renders it.

Added

• cratis render --package-set <FILE> takes an approved package set (the Scene document Stage and a React host share) naming custom runtime packages beyond core, scene.web and Cratis.Components. The profile is resolved against the shipped and the approved packages together with Stage's planner (CLI-RENDER-007 to CLI-RENDER-010), a malformed set or one that reuses a shipped package name is refused before anything is published, and the published application gets approved-packages.json, one extra package.json dependency per package and a .frontend/approvedPackages.ts that loads them through Scene before the first render. See Custom runtime packages. (part of #284)
• The packed-CLI rendered-React check approves a custom package (Integration/Cli/RenderedReact/CustomPackage), renders a screen that names its component, builds and launches the application and asserts in a browser that the component rendered from the package with its style sheet and no load diagnostics. (part of #284)

Changed

• The CLI bundles Stage 4.72.0 (Scene 4.20.0). cratis run starts cratis/stage:4.72.0, which, being a built frontend, renders only the three shipped packages; the documentation says so and points at cratis render --package-set for custom packages. (part of #284)
• An unknown package in a ui profile (CLI-RENDER-007) now says a custom runtime package has to be approved with --package-set. (part of #284)