The monthly Oqtane Core Contributor Meeting was held on May 7, 2025.
Status Updates
6.1.2 released on April 10, 2025
- 41 Pull Requests (2925 Total)
- 86 Commits (6551 Total)
- 4 Contributors (58 Total)
Contributors: @sbwalker, @zyhfish, @leigh-pointer, @ADefWebserver
6.1.2 Release Highlights
- Updated to .NET 9.0.4
- Fixed "Deploy to Azure" ARM template
- Customization of robots.txt (per site)
- New Azure SQL Database Provider
- Fixes for MySQL and PostgreSQL database providers
- External Login support for Host role
- Response Caching support for ImageUrl (thumbnails)
- Prevent Scheduled Jobs from blocking startup
Roadmap
The next Oqtane release will be version 6.1.3 and is expected to be released in mid-April.
6.1.3 Release Highlights
- Update to .NET 9.0.5
- Added time zone support for sites and users
- Added support for module header and footer content
- Url Mapping enhancements
- Ability to specify custom Register Url and Profile Url in User Settings
- Fixed .NET MAUI cross origin IP address which was changed in .NET 9
6.2 Release Themes
- Integration of Microsoft.Extensions.AI to allow sites to configure their preferred LLM
- IChatClient integration into the RichTextEditor provider to improve content generation (text and images)
- Model Context Protocol (MCP) Server for accessing Oqtane's headless API via AI
- Semantic Search enhancements to existing content search engine
- Folder Providers to allow content to be stored externally
- Content Localization synchronization across sites
Oqtane Marketplace
The Oqtane Marketplace was originally designed using an "App Store" approach where all interactions were expected to occur through the Oqtane Framework. This model works well however there is a need to support other user flows as well. As a result, the Marketplace will be receiving a number of enhancements which will result in the following benefits:
- Installation Id not required when ordering
- License creation independent from order process
- Allow multiple users per company/organization
- More product licensing options
- Support for traditional online payment and procurement flows
Oqtane Events
- Apr 11 - Open Source Friday with GitHub - Focus On Oqtane (virtual)
- Apr 17 - Micro-frontends with Blazor (virtual)
- May 9 - Open Source Friday with GitHub - Who Pays For Open Source? (virtual)
- May 17 - SoFlo DevCon 2025 (Davie, Florida)
- May 19-22 - Microsoft BUILD (Seattle, WA)
- Jun 26 - TrailBlazor Conference (virtual)
Discussion
In the prior meeting there had been a discussion about whether the location of the module and theme template files could be considered problematic from a security perspective (ie. they are stored in the wwwroot folder). Clarification was provided that the template files are NOT included in Release packages - they are only intended for use in a Development environment. @iJungleBoy mentioned that there could still be a risk if someone published Oqtane directly from Visual Studio. @sbwalker indicated that it is not possible to publish directly from Visual Studio as some customizations are required - which is why Oqtane is packaged using the release.cmd in the Oqtane.Package folder. Installations created from unofficial release processes are not supported and should be considered "use at your own risk".
@iJungleBoy suggested that if Oqtane's major version number corresponded to the .NET version it was targeted for, the version scheme would be more intuitive for developers and users. This makes sense... and since a new major version of Oqtane has been released with every new major .NET version since 2019, there is consistency in major release schedules. Therefore, when .NET 10 is released in November 2025, Oqtane will move to version 10 as well.
The next Oqtane Core Contributor Meeting will be on Jun 4, 2025.