Foundry CLI 0.2.3 – Single-tenancy auth & release artifacts · Latest

Boilerplate single-tenancy (React + API)

This release updates the single-tenancy boilerplate around sign-in and onboarding: the login experience now supports email delivery and verification with a code, so users can confirm their address as part of the flow. Self-service registration is supported end to end—you no longer need invites; signing up is enough to get started.

Note: Executors and the templates.zip package are no longer stored in the repository. They had grown large and were making the CLI heavy to clone and ship. From this version onward, those assets are attached only to GitHub Releases; the CLI downloads templates at runtime when needed (nothing is embedded in the executable). A local templates.zip is still produced on dotnet build of Foundry.CLI so you can upload it to the matching release tag.

• Single-tenancy auth: Email sending and code-based verification in the login/register flow; link-only confirm-email removed from the template.
• Register without invites—open registration instead of invite-only onboarding for the single-tenant app.
• Lighter repo: executors and templates.zip live as release attachments; the CLI fetches from releases instead of bundling everything in the tree.
• API: user-facing messages in English where it matters (auth, forgot/reset password, etc.) in both single and multi templates for consistency.
• Backend hygiene: Boilerplate.Application.Dtos namespaces aligned; stray NewLevel.* DTO namespaces removed in multi; duplicate EmailDto under Auth removed.
• CLI UX: after download/prepare you see “Templates ready.” and prompts continue without a misleading “press any key” pause; successful runs exit immediately; on errors, an optional key wait runs only when the console is interactive (not when stdin is redirected).
• CLI rename pass: Boilerplate → project name also applies to .bat, .sh, .yml / .yaml (migration helpers and docker-compose), not only .cs / .json; files without the placeholder are skipped.
• React (single): locale JSON trimmed to keys the app uses; notifications.* aligned with CreateNotificationModal / NotificationCenter; apiClient import and dead helper cleanup.

Multi-tenancy is unchanged as a product: invites, tenant, and confirm-email by link remain where they already existed; it benefits from the same English API messages and Dtos cleanup.

Operators: publish templates.zip on the GitHub Release whose tag matches the version string in Program.cs. Users with an existing cache under %LocalAppData%\BoilerplateCustomizer\<version>\extracted only re-download if they delete that folder or you ship a new templates release tag.

Upgrading an old generated single-tenant app: prefer scaffolding a new project with the current CLI, or manually adopt the code-only email verification flow (no link confirm endpoint), English API strings, and the React locale / apiClient updates if you copied the boilerplate frontend.

For day-to-day use, install or run the Foundry CLI and scaffold a project as usual; rely on GitHub Releases for packaged templates and executors rather than copying files from the repository.