Skip to content

Release v0.7.2 - #435

Merged
roncodes merged 12 commits into
mainfrom
release/v0.7.2
Nov 19, 2026
Merged

roncodes merged 12 commits into
mainfrom
release/v0.7.2

Conversation

@roncodes

@roncodes roncodes commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Release PR for v0.7.2. Merging it into main tags v0.7.2 through release.yml.

What's in it

Merge order

  1. Merge fix(migrations): make the columns foreign keys point at unique #434 into this branch.
  2. Merge Passenger order config for every organization #433 into this branch.
  3. Release core-api 2.0.3 (Release v2.0.3 core-api#339, with Push apps: an organization's own apps send pushes with their own credentials core-api#340), then merge Push apps: Settings → Push Apps, and pushes with each app's own keys #436 into this branch.
  4. Merge this PR into main.

With #436 this needs core-api 2.0.3. Then fleetbase/fleetbase's release/v0.8.2 needs fleetbase/fleetops-api 0.7.2 in its lock (fleetbase/fleetbase#764).

MySQL 8.4 turns on restrict_fk_on_non_standard_key by default. With it on,
MySQL refuses any ALTER of a table that a foreign key points at through a
non-unique key (1553), which is how the v0.8.0 deploy failed on
order_configs. v0.7.1 worked around it for that one migration; this removes
the cause.

uuid becomes unique on devices, inspection_forms, inspection_submissions,
order_configs (also referenced from storefront's stores and networks),
telematics, warranties and work_orders, on the main and sandbox databases.
The old single-column index is dropped in favour of <table>_uuid_unique.
Columns a unique or primary key already covers are left alone, tables with
duplicate values are skipped with a message, and re-running changes nothing.
@codecov

codecov Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (c844a12) to head (9a0da1e).

Additional details and impacted files
@@             Coverage Diff              @@
##                main      #435    +/-   ##
============================================
  Coverage     100.00%   100.00%            
- Complexity     14702     14754    +52     
============================================
  Files            676       679     +3     
  Lines          51313     51439   +126     
============================================
+ Hits           51313     51439   +126     
Flag Coverage Δ
backend 100.00% <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.

- New organizations get Passenger next to Transport (CompanyObserver).
- A migration creates it for every existing organization; one that already
  ran fleetops:create-order-config passenger keeps its config.
- It is a core config like Transport: it can't be deleted and its flow is
  read-only.
…h their own keys

- Settings → Push Apps lists, adds, edits and removes the organization's push
  apps (APNs key and Firebase service account, written but never read back)
  and sends a test push to one device.
- v1/customers/register-device and v1/drivers/register-device accept
  push_app (the app's key) and environment, link the device to that app and
  refuse an unknown key.
- Every Fleet-Ops push notification also goes through core's PushAppChannel;
  Driver and Contact route push-app devices there and every other device to
  the install-wide APNs and FCM channels as before.
- Requires fleetbase/core-api ^2.0.3.
fix(migrations): make the columns foreign keys point at unique
Passenger order config for every organization
- composer accepts dev-release/v2.0.3 next to ^2.0.3, and the contract run
  links core-api's release branch
- the service account placeholder no longer has braces, which ICU read as
  an argument and failed the Ember build
- install-wide token routes are plain lists, and the tests now expect that
Push apps: Settings → Push Apps, and pushes with each app's own keys
…ch service issued their token

The console form names each field by platform and service (iOS bundle ID, Apple push key,
Firebase service account key) with help text saying where to find each value. It explains that
Android needs no package name, that the iOS bundle ID and Android package name can differ in
one push app, that a second iOS app needs its own push app, and that iOS apps using Firebase
go through the Firebase settings.

Settings are saved and checked by core-api's push providers, so the errors say exactly what
to fix, including when google-services.json or GoogleService-Info.plist is pasted instead of
a service account key. register-device accepts push_provider (apns or fcm), and the test push
takes a token type, worked out from the token when left alone.
Drops the temporary dev-release/v2.0.3 constraint and the contract job's core-api overlay now
that 2.0.3 is released.
@roncodes
roncodes merged commit f91a197 into main Nov 19, 2026
11 checks passed
@roncodes
roncodes deleted the release/v0.7.2 branch November 19, 2026 09:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant