release: v0.6.62

[roncodes]

Release branch for v0.6.62. Versions bumped in composer.json, package.json and extension.json via flb version-bump --patch, and RELEASE.md written for the tag body.

Included

PR
#311	Expand public Fleet, Vehicle, and Driver API contracts

Retargeted onto this branch and merges here before this PR merges to main.

Its companion specification and contract-test PR is fleetbase/postman#59, which documents and tests the API changes shipping here. It merges in fleetbase/postman on its own.

Also in this branch

The three check workflows learned the release branch name.

v0.6.61's follow-up (#308) taught release.yml to tag a release/v* branch, but server.yml, ember.yml and postman.yml still only ran on pull requests targeting main and dev-v*. Retargeting #311 onto this branch would therefore have run no PHP CI, Ember CI or Postman contract check on it — the rename would have silently switched off every check on exactly the branch the convention exists to validate. All three now also trigger on release/v*.

push stays limited to main, which is what keeps a release branch from running each workflow twice (the reason for ci avoid duplicate release branch runs in v0.6.61).

Release gate

The reusable release-tag.yml refuses the tag unless the branch name, the three manifests and RELEASE.md all agree. Checked against this branch:

ok   composer.json = 0.6.62
ok   package.json = 0.6.62
ok   extension.json = 0.6.62
ok   RELEASE.md first line names v0.6.62
ok   no template placeholder
ok   tag v0.6.62 does not exist yet

On merge, release.yml tags v0.6.62 on this PR's merge commit; create-release.yml and the publish jobs chain off push: tags: v* as they already do.

Validation

Nothing in this branch is executable — three manifest versions, the release notes, and three workflow trigger lists. The work being released carries its own validation on #311:

• php scripts/pest-file-runner.php — 434 files, exit 0
• Coverage gate — 100.00% on all three metrics (34670/34670 statements, 4428/4428 methods, 530/530 classes)
• PHP CI green on run 33869029161

Live contract run

The API Contract (Postman) job boots a stack with this branch's Fleet-Ops source overlaid and runs fleetbase/postman@main against it. On #311's head it passes:

requests    218 executed, 0 failed
assertions  221 executed, 0 failed

An earlier run of that job — and a run on main at the same time — failed with Error: Unable to find request or folder. Both were transient; the job has since passed on an unchanged collection.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (825d060) to head (71e2e8a).

Additional details and impacted files

@@             Coverage Diff             @@
##                main      #312   +/-   ##
===========================================
  Coverage     100.00%   100.00%           
  Complexity      9899      9899           
===========================================
  Files            526       526           
  Lines          38163     38163           
===========================================
  Hits           38163     38163           

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.