Release v16.34.2
Summary
Two things the last releases left broken for anyone running the development images or opening the Workbench: the *-development / *-development-slim containers refuse to start without an encryption certificate, and the Workbench — moved to PrimeReact 11 in #3717 — lost the lara-dark-blue look every screen was designed against. The Workbench comes back through @cratis/components 3.4.0's styled mode (Cratis/Components#148) and its PrimeReact 10 palette.
Fixed
- The
*-developmentand*-development-slimcontainer images start again without an encryption certificate. Since 16.33.1 they aborted at startup withAn encryption certificate is required in production for OpenIddict key security, because the check for a development build had regressed to theDOTNET_ENVIRONMENT/ASPNETCORE_ENVIRONMENTvariables the images never set; it is a compile-timeDEVELOPMENTcheck again, matching how the development TLS certificate is decided. - The Workbench renders with its PrimeReact 10 look again — text-style toolbar buttons, the sidebar and namespace selector surfaces, bold table heads, styled inputs and the password field on the sign-in page — through PrimeReact 11's styled mode instead of the baseline theme.
🤖 Generated with Claude Code