26.1 Public Preview 1
The first release candidate for Clinimatix Caravel.
26.1.0-rc1 brings the 26.1 foundation together for public evaluation and integration. It establishes our first release-candidate baseline, built on .NET 10 LTS. It is not a stable release.
The framework in this preview
- Application foundations: expressive ASP.NET Core routing, configuration, service providers, validation and HTTP defaults.
- Clarion data access: models, queries, timestamps, soft deletes, factories and seeders on EF Core, with SQL Server, PostgreSQL and SQLite.
- Bosun tooling: Razor/API starters, development sessions, route inspection, generators, migrations and seeding.
- Optional application services: local accounts and authentication, events, durable queues, fixed-interval scheduling, local storage, mail and SMS notifications.
Development highlights in Preview 1
Alongside the core foundation, this first candidate includes:
- Account flows for opt-in registration, email confirmation, password recovery, authenticator-app MFA and recovery codes. Applications provide the account screens.
- Renewable queue leases and a transactional outbox for durable work alongside application data. External side effects remain at least once.
- Transactional SMTP mail with templates, attachments, development capture and queued delivery.
- Replaceable mail/SMS channels, independent queued retries and a Twilio adapter. SMS delivery is not SMS MFA.
Read the full version changelog for the complete baseline and known limitations.
Install the public preview
Requires the .NET 10 SDK. All twelve 26.1.0-rc1 packages are now available on nuget.org. Install Bosun, then create and run an app:
dotnet tool install --global Clinimatix.Caravel.Bosun --version 26.1.0-rc1
caravel new MyApp
caravel serve --project MyAppPin the exact version and select “Include prerelease” when browsing in Visual Studio. Follow the installation guide to add libraries to an existing app.
The GitHub package ZIP and checksums remain available for local-feed installation. NuGet publication distributes the same RC1 packages; it is not another release.
Evaluation and next steps
The release commit passed Windows, Linux and macOS checks, plus SQL Server, PostgreSQL and SQLite coverage. This verifies the framework’s tested paths; your deployment and chosen mail/SMS provider still need application-specific verification.
Keep a rollback plan and report reproducible issues. Work toward stable 26.1 focuses on integration feedback, fixes and upgrade validation. Passkeys and account screens, calendar scheduling, cloud storage, more notification providers and AI/MCP remain future work; see the roadmap.