Changelog

All notable changes to the Alakili product — the API and the web app — are documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

The browser extension ships on its own release train and has its own changelog.

1.2.0 (2026-10-22)

Added

• docs: add guide for installing extension (c1aa4b2)

Fixed

• dispatch: driver reassignment, live pair-rule warnings; publish reviewed policies (#98) (8253420)
• notify: list hub drivers in channel posts and allow multiple send channels (#101) (9669286)

1.1.0 (2026-10-15)

Added

• add recursive flag to infisical run for fetching secrets from subdirectories (#90) (a9b71c4)
• add roster sorting and fix the integration connect and search bugs (#94) (73425e7)
• enhance station management and vehicle assignment features (#87) (c63337c)
• onboarding: replace self-serve setup with a guided product tour (#85) (7f6de33)

1.0.0 (2026-10-01)

⚠ BREAKING CHANGES

• release: first stable release v1.0.0 (#83)

Added

• ci: configure release-please for versioning and changelog management (#80) (09da916)
• release: first stable release v1.0.0 (#83) (6ff2e5e)
• workflows: add flow node component and job/run management pages (#79) (145055f)

Fixed

• ci: add changelog files to dockerfile (#81) (2772ed7)

Unreleased

0.1.0 - 2026-09-24

The first versioned release. Everything below was built before the project adopted SemVer, so this entry describes the product as it stands rather than listing every change that got it here.

Added

• Dispatch board — build a day’s assignments from the roster and the routes, move drivers and walkers between trucks, set dock doors, and advance the day through a configurable workflow with per-stage permissions.
• Assignment engine — drafts a day automatically: hub routes first, then drivers to truck routes, then walkers to trucks, honouring area preferences, captain cover, walker capacity and per-station rules.
• Roster ingestion — a browser extension pulls the roster, associates, routes and fleet from the Amazon logistics portal using the dispatcher’s own session, and the server decides what to fetch and when. Spreadsheets can also be uploaded by hand.
• People and compliance — an employee record per person with licences, background checks and expiry tracking, plus a compliance queue of what is lapsing.
• Attendance and reliability — daily attendance outcomes, six-day-in-a-row detection, and reliability metrics over a fourteen-day window.
• Notifications — driver and walker messages over Discord, Slack, SMS and email, with per-truck channel posts, a station ops channel, crew channel access granted for the day and revoked when it is archived, and every attempt recorded.
• Confirmation rounds — scheduled shift confirmations with inbound replies feeding back onto the board.
• Scorecards, reports and a dashboard — weekly station and team scores, daily performance per driver, and wage findings.
• Multi-tenancy and billing — organizations, stations, role-based access with per-station grants, plans, subscriptions, seats and feature entitlements.
• Platform console — an internal /admin area for provisioning organizations, managing plans and staff, and seeding or resetting demo data.
• Demo organizations — an organization marked is_demo can be filled with a station of synthetic people, trucks, routes and three working weeks of history produced by the real engine, and never pulls live data from the portal.