Skip to content

v0.1.52-beta.4

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 13 Nov 14:44
· 13 commits to main since this release

This is a prerelease for testing. Do not run it in production. The stable v0.1.52 follows after its test cycle.

Breaking changes

None. Since v0.1.52-beta.3 no API route, field, error code, permission, setting key, environment variable, Helm or CDK value was removed or renamed. New fields (driverChargers in the portal location reply, chargingUnits and hasStationUnits in the dashboard stats reply, serialNumber and ipAddress on station units) and the new route POST /v1/portal/support-cases/:id/close are additive. Renamed tabs keep their URL keys.

Behavior change: a driver's reply now reopens any resolved or closed support case. Before, the reply was stored and the case stayed resolved or closed unless the automatic answer had resolved it. The request and its reply are unchanged, so no client stops working (Support Cases, Reopen a Case).

Upgrade notes

  • Unchanged from v0.1.52-beta.1: migration 0490_release_0_1_52.sql replaces the per-station unique indexes idx_driver_favorite_stations_unique and idx_station_watches_unique with unique indexes on driver, station and unit. During a rolling upgrade, an API pod of v0.1.51 or earlier that still runs after the migration answers 500 when a driver turns on Notify Me When Free (its insert names the dropped index in ON CONFLICT). Favorites keep working. The error ends once every API pod runs v0.1.52. To avoid it, upgrade the API pods right after the migration job, or scale the API to the new release before drivers use station watches.
  • Migration 0490_release_0_1_52.sql changed since v0.1.52-beta.3: it now allows driver as a support case resolution source and adds the unit serial number and IP address columns. It is rerun-safe: installs on an earlier v0.1.52 beta apply it again and end with the same schema.

Changes since v0.1.52-beta.3

Features

  • Drivers close their own support case with Close Case, and a reply reopens a resolved or closed case. The Account entry that opens the case list is now Support (Support Cases, Close a Case).
  • Units carry an optional serial number and IP address, set when you create or edit a unit and shown to CSMS users only (never in the portal, OCPI or OCPP). The Create EVSE dialog lets you pick the unit, and the tab header names Create Unit (Stations, Manage units). Suggested by @Tobias9876 in #59.
  • Dashboard: a Charging Units card shows while stations have units (Dashboard, Stat Cards). Suggested by @Tobias9876 in #59. On phones, stat cards show two across, an odd last card full width.
  • Site page: Autocharge, Data Plan and Carbon Region have their own tabs (Sites, Autocharge, Data Plan, Carbon Region).
  • Portal location page: one row per charger, a unit charger named by its box (Location Detail).
  • Portal station and guest pages: the port card shows one line per connector with shared connector type names (J1772 and others), unit rows are titled by their box, guest mode names the box, and the plug-in step is animated (Charging, Guest Charging).
  • Where guest payment is not offered, guests see Sign In and Register instead of a payment-not-configured message (Guest Charging).

Fixes

  • CSMS and portal: one style for notices and save feedback, with a light Save spinner and Saved and Created messages. The warning color is split into a fill and a text color, and the outline button has its own text color.
  • CSMS: the Create button label is centered, the units text left the EVSE and Connectors header, the site Autocharge tab is read-only without sites:write, the active maintenance window shows as the shared warning notice, and the electrical safety notice comes first in the load management panel.
  • Dashboard: the Security Events station list pages 20 rows at a time.
  • CSMS and portal: the avatar editor buttons stack on phones with Remove set apart.
  • CSMS and portal: Unable to Connect follows the stored language, theme and mode.
  • Portal: the support list back button returns to where it was opened, also after a reload, and the reply box lines up with Send.
  • Portal: the Partner Network tab shows whenever roaming is on.
  • API: the Plug and Charge provider test answers its failures with their status and code.

Thanks

Thanks to @Tobias9876 for the unit serial number, IP address and Charging Units feedback in #59.