release: Fleet-Ops v0.6.63

[roncodes]

Summary

• render driver vendor names from the vendor_name accessor returned by the driver list response
• use the Fleet model relationship method names for internal fleet index, edit, and details requests
• bump Fleet-Ops package, Composer, and extension metadata to 0.6.63

Root cause

The Drivers table dereferenced vendor.name even though the list response does not eager load the vendor relationship; it already provides vendor_name. Fleet console routes sent public API relation aliases such as parent_fleet and service_area directly to the internal Eloquent resource loader, which expects parentFleet and serviceArea.

Testing

• targeted ESLint for all changed JavaScript files
• JSON parsing for package.json, composer.json, and extension.json
• git diff --check
• Drivers vendor column regression assertion: passed
• Fleet index, edit, and details relation expansion regression: passed

The focused Ember assertions complete successfully in Chrome. The local Ember test process remains open after reporting results and was interrupted after completion.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (aea2f71) to head (94c33fa).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##                main      #315   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity     10003     10003           
===========================================
  Files            531       531           
  Lines          38585     38585           
===========================================
  Hits           38585     38585           

Flag	Coverage Δ
backend	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.