← Back to home

Release Notes

Changelog for the LeaveBy Chrome extension

v1.7.1

April 6, 2026

Recurring event reliability

LeaveBy now handles recurring events much more efficiently. Drive time lookups are cached per route during each scan, so a weekly meeting at the same office makes one API call instead of seven. Failed lookups are retried once, and skipped events are now visible in the popup.

  • Drive time caching — one API call per unique destination per scan, even for recurring events with multiple occurrences
  • Retry on failure — transient network errors are retried once; rate-limited requests are handled gracefully without wasting quota
  • Skip tracking — the popup now shows how many events were skipped when a route couldn’t be calculated
  • Location-removed cleanup — if you remove the location from an event, the travel block is automatically cleaned up
  • Removal feedback — the popup now shows when outdated travel blocks are removed

v1.7.0

March 20, 2026

Premium features & Stripe payments

LeaveBy now offers an optional premium upgrade for power users. Early adopters who installed before March 30, 2026 get premium for free — everyone else can unlock it with a one-time $5 payment via Stripe.

  • Travel block color customization — choose from 11 Google Calendar colors instead of the default gray
  • Busy/Free toggle — control whether travel blocks show as “Busy” (blocks your time) or “Free” (visible but available)
  • One-click upgrade — click “Upgrade to Premium” in the popup, pay via Stripe, then restore your purchase — premium is tied to your Google account
  • Onboarding banner fix — the “Complete Setup” button no longer overflows outside the onboarding banner

v1.6.0

March 9, 2026

Deleted travel blocks stay deleted

Previously, if you deleted a LeaveBy travel block you didn't want (e.g., a hotel in another city, a flight, or any event you're simply not driving to), the next scan would recreate it. Now, LeaveBy remembers your deletion and won't recreate the block.

  • Permanent dismissal — delete a travel block and it stays deleted for the life of that event, even if the event is rescheduled
  • Automatic cleanup — tracking entries are pruned once the event is more than 7 days in the past
  • Safer API handling — if the Calendar API fails when fetching existing blocks, dismissal detection is skipped entirely to prevent false dismissals
  • Duplicate block prevention — fixed concurrent scan race conditions, API failure fallback, and per-event error isolation to eliminate duplicate travel blocks
  • Partial failure feedback — the popup now tells you if some blocks failed to create instead of showing a blanket success message

v1.5.0

March 1, 2026

Drift detection for rescheduled events

LeaveBy now detects when a calendar event or your settings have changed and automatically replaces stale travel blocks with corrected ones. No more leaving too early or too late when a meeting gets moved.

  • Automatic updates — travel blocks are replaced when events are rescheduled, relocated, or your settings change (color, buffer, reminder, busy/free)
  • Scan result feedback — the popup now shows how many blocks were updated alongside the created count

v1.4.0

February 2026

Onboarding wizard & address autocomplete

A guided setup experience for new users, plus Google Places autocomplete for entering your home address.

  • First-install onboarding — step-by-step wizard guides you through connecting Google Calendar and setting your home address
  • Address autocomplete — Google Places suggestions as you type, shared between popup and onboarding
  • Orphan cleanup — automatically deletes travel blocks when their parent events are deleted or cancelled

v1.3.0

January 2026

Initial Chrome Web Store release

The first public release of LeaveBy on the Chrome Web Store.

  • Automatic travel blocks — scans Google Calendar for events with locations and creates [LeaveBy] blocks with real drive times
  • Configurable settings — buffer time, departure reminders, travel block color, and busy/free status
  • Background scanning — re-scans every 30 minutes via Chrome Alarms API
  • Duplicate prevention — uses extended properties to avoid creating duplicate blocks