Changelog

All notable changes to the Alakili browser extension are documented in this file.

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

The extension versions independently of the API and the web app, because the product changes constantly without touching it. The product’s changelog is at the repository root.

Chrome will not accept a SemVer pre-release or build-metadata label in a manifest, so the manifest’s version carries the numeric core and version_name carries the full string. The version shown in the popup is version_name.

0.2.1 (2026-10-15)

Fixed

• ci: bring staging deploy fixes back into dev (#89) (1fa8773)

0.2.0 (2026-10-01)

Added

• ci: configure release-please for versioning and changelog management (#80) (09da916)

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 extension as it stands rather than listing every change that got it here.

Added

• Reconciliation against the server’s plan — the extension asks the API what is missing and fetches only that. It keeps no record of its own, so a reinstall changes nothing and the endpoint knowledge can change without a store review.
• Portal reads using the dispatcher’s own session — the roster, associates, routes and fleet are read from an already signed-in logistics.amazon.com tab. The extension never sees an Amazon password.
• A popup that says what is wrong — one next step at a time, whether that is signing in to Amazon, signing in to Alakili, opening a portal page, or choosing which station an unmatched service area belongs to. It shows a row per configured feed with when each last worked.
• Scheduled reconciliation — a weekly alarm plus a check on browser startup, with the server saying when to ask again.
• Error reporting — Sentry, flushed before the service worker suspends.