"Extension discovery, driver vehicle validation, and CLI search"
This release includes two bug fixes and one new feature: a corrected public extension discovery endpoint in the Registry Bridge, a driver vehicle validation patch in FleetOps, and a new flb search command in the Fleetbase CLI.
The public extensions listing endpoint (~registry/v1/extensions) has been corrected and hardened. A dedicated PublicRegistryExtension API resource now sanitizes the response, stripping all sensitive fields before they leave the server. The install_count aggregation has been fixed to use withCount('installs') and the incorrect author relationship has been replaced with the proper company relationship. The endpoint returns a clean, flat array.
A TypeError that occurred when creating a driver with a vehicle object sent from the frontend has been resolved. A new ResolvableVehicle validation rule accepts a public_id string (e.g., vehicle_abc123), a UUID string, or an object/array containing an id, public_id, or uuid key. Vehicle normalization has been added to both createRecord() and updateRecord() in DriverController so the correct vehicle UUID is always resolved before persistence.
A new flb search [query] command (alias: flb list-extensions) lets developers and administrators browse all available extensions directly from the terminal. Results are displayed in a formatted, colour-coded table showing the extension name, category, publisher, version, price, and supported install formats. Filtering options include --category, --free, --json, --simple, and --host.
- [fleetbase-cli] Added
flb search [query]command (alias:flb list-extensions) for browsing available extensions - [fleetbase-cli]
--categoryfilter to narrow results by extension category - [fleetbase-cli]
--freeflag to list only free extensions - [fleetbase-cli]
--jsonflag for machine-readable JSON output - [fleetbase-cli]
--simpleflag for plain-text terminal output - [fleetbase-cli]
--hostoption to target self-hosted registry instances
- [fleetops] Fixed
TypeErrorwhen creating a driver with a vehicle object sent from the frontend - [fleetops] Added
ResolvableVehiclevalidation rule acceptingpublic_id, UUID, or object withid/public_id/uuid - [fleetops] Added vehicle normalization in
DriverController::createRecord()andupdateRecord()
- [registry-bridge] Fixed
install_countcolumn error by switching towithCount('installs')eager load - [registry-bridge] Removed incorrect
authorrelationship; replaced with correctcompanyrelationship - [registry-bridge] Removed sensitive data (internal UUIDs, Stripe IDs, private relationships) from public endpoint response
- [registry-bridge] Public extensions endpoint now returns a plain array without a wrapping key
- [fleetbase-cli] Price display correctly converts cents to dollars in search results
- [fleetbase-cli] Search results show both install formats:
flb install fleetbase/<slug>andflb install <extension_id> - [registry-bridge] Extension listing response is a clean, flat array for easier consumption by CLI and third-party tools
- None 🙂
# 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"- fleetops: v0.6.37
- registry-bridge: v0.1.7
- fleetbase-cli: v0.0.5
Join the discussion on GitHub Discussions or drop by #fleetbase on Discord