Skip to content

Changelog

FOSSBilling publishes release notes and tagged versions on GitHub. Use the links below to review new features, fixes, and upgrade notes before you update.

GitHub Releases

View all FOSSBilling releases with detailed changelogs on GitHub Releases.

Version History

Browse the complete commit history to see all changes.

For the latest changes, start with the most recent release.

AreaSummary
PHPMinimum version raised to 8.3
DatabaseCharset migrated to utf8mb4; DB config key renamed from db.type to db.driver
ConfigurationNew rate_limiter block replaces old api.rate_* keys; new trusted_proxies and auto_detect_locale settings
ModulesAntispam replaces Spamchecker; Servicemembership, Paidsupport, Wysiwyg removed; new Widgets module
TemplatesAll module templates moved from html_* to templates/{admin,client,email}/
BuildFront-end asset build migrated from Webpack Encore to esbuild; jQuery removed; shared frontend source now lives in /frontend; assets built into /src/public/assets
RoutingCustom HTTP layer replaced with Symfony HttpKernel, HttpFoundation, and Routing components
ThemesAsset loading (encore_entry_* → direct tags), Twig filter removals (alink, link, gravatar, library_url, markdown, size, legacy money* filters), DebugBar_renderHead()debug_bar_render_head(), new public_asset_url filter, new url filter with area parameter
APIGuest API hardened: system_version endpoint removed, public company data can be restricted with hide_company_public, rate limiting on guest ticket creation
LibraryNew Doctrine ORM layer alongside RedBean; Symfony Rate Limiter, Uid, Sanitizer, Serializer, PropertyAccess components added; Box_Mod, Box_Paginator, Box_TwigExtensions removed; Gravatar replaced with DiceBear
PatcherExtended through patch 64 (was 43)
Uploads & Public AssetsUploads moved from /uploads to /data/uploads; gateway and default branding assets moved to /public

View the full 0.8.0 release notes for the complete list of changes.

Before updating, review the release notes for any breaking changes or manual follow-up steps. We call these out in each release whenever they apply.

Security-related changes are also published through our GitHub security advisories. If you run FOSSBilling in production, subscribe to release notifications and security alerts.