Fleetbase 0.7.45 is a release about flexibility and operational clarity. It opens up SMS delivery to a wide range of providers, reshapes the Fleet-Ops navigation into a more operations-focused workspace, introduces shared reporting components, and hardens the telematics and device-management layers that fleets depend on every day.
Here's what's new.
Multi-provider SMS
The headline change in 0.7.45 is configurable multi-provider SMS. Core API now supports Vonage, AWS SNS, MessageBird, SMPP, custom HTTP providers, and the existing CallPro path, so you can route verification codes and notifications through whichever provider fits your region, cost model, or carrier relationships.
This is backed by protocol and provider configuration support, meaning SMS delivery can be driven from settings and environment mapping rather than hard-coded assumptions. We've also improved the SMS service's fallback behavior and added test coverage across the new provider selection paths, so switching or layering providers is dependable rather than fragile.
A refreshed Fleet-Ops workspace
Fleet-Ops navigation has been refactored around a clearer, operations-focused workspace. The sidebar has been reworked and a new operations monitor gives teams a more direct view of what's happening across their fleet.
Alongside the navigation refresh, we've added hub and search support across Fleet-Ops management, maintenance, analytics, and settings landing surfaces. Finding the right screen and the right record is faster, and the landing surfaces now give each area of Fleet-Ops a proper home rather than a flat list of links.
Telematics and device-management hardening
This release does meaningful work under the hood on connectivity reliability. We've hardened device attachment morph types and added repair support for invalid polymorphic relation namespaces, which resolves a class of subtle data-integrity issues around how devices attach to other records.
Telematics also gets a round of reliability improvements: better device sync, clearer attach error handling, improved Afaqy provider behavior, and better device and vehicle filtering. Together these make tracing and fixing connectivity problems less of a guessing game.
Shared reporting and UI
Reporting becomes more modular in 0.7.45. We've added shared report find and select components, a report widget, and report widget registration, so reports can be surfaced consistently across the platform. New dashboard outlets let engines contribute content around the shared dashboard layouts, making dashboards extensible rather than fixed.
On the shared UI side, the sidebar navigator has been refined and Fleetbase attribution styling and behavior simplified. A wave of new tests now covers report selection, report widgets, sidebar navigation, dashboard registration, and attribution behavior.
Facilitator-driver data support
Fleet-Ops Data gains a new facilitator-driver model, with an application re-export and driver subtype support on facilitators. This lets maintenance and assignment workflows correctly identify facilitator drivers, and it comes with regression coverage for facilitator-driver data and maintenance schedule normalization.
Bug fixes worth noting
This release also clears out several rough edges, including fixes to reports empty-state documentation links, the Fleet-Ops draft order entity edit modal, device attach errors and telematics sync feedback paths, facilitator-driver assignee restoration in maintenance schedules, and shared sidebar navigator edge behavior now covered by new Ember UI tests.
What's in this release
Version 0.7.45 updates Console to 0.7.45, Core API to 1.6.52, Fleet-Ops to 0.6.53, Fleet-Ops Data to 0.1.38, and Ember UI to 0.3.35. New API surfaces include configurable SMS provider support in Core API settings and environment mapping, internal Fleet-Ops hub and search routes for management, maintenance, analytics, and settings surfaces, device and vehicle hardening around attachable types and telematics sync, the Fleet-Ops Data facilitator-driver model, and shared Ember UI report selection and report widget components.
Upgrading
bash
# Pull latest version
git pull origin main --no-rebase
# Update docker
docker compose pull
docker compose down && docker compose up -d
# Run deploy script
docker compose exec application bash -c "./deploy.sh"As always, if you run into anything, join us on GitHub Discussions or drop by #fleetbase on Discord.
