GINBOT v1.2.0

GINBOT v1.2.0

Summary

Onboarding, destination-first setup, saved-location shortcuts, idle cleanup, restart restoration, and public repository documentation release.

Added

• First-time onboarding and concise GINBOT instructions.
• Telegram command registration.
• Destination-first setup for typed destinations.
• Saved Home and Work shortcuts.
• Native Telegram Current Location origin workflow.
• Address suggestions for manual origin and destination entry.
• Custom Traffic Duration thresholds.
• Stable-traffic prompt with five-minute automatic idle cleanup.
• Restart restoration for active alerts and pending idle-stop decisions.
• Public-facing README, beta testing guidance, security policy, contributing guide, issue templates, and release checklist.

Changed or Fixed

• Aligned runtime copy, command descriptions, and documentation with the GINBOT product name.
• Improved route confirmation and recovery after typed destinations or partial Maps parsing.
• Preserved active alerts while users set up replacement routes.

Deployment Notes

• Continue using python main.py as the worker command.
• Railway deployments should keep DATA_DIR=/data, LOG_LEVEL=INFO, and exactly one polling replica.
• Do not run a local bot worker at the same time as the deployed worker with the same Telegram token.

Known Limitations

• Closed beta: testers should verify important trips directly in Google Maps.
• Notifications depend on Telegram, Google routing data, network access, credentials, and a running worker.
• Destination-first text does not include autocomplete, multi-stop routing, or general natural language understanding.

GINBOT v1.1.0

GINBOT v1.1.0

Summary

Route parsing, setup recovery, deployment persistence, and logging hardening release.

Added

• Fallback route setup when a Google Maps link does not expose both route endpoints.
• Persistent DATA_DIR support for Railway volumes.
• Saved-location validation and storage migration.

Changed or Fixed

• Improved Google Maps route extraction from redirects, public route URLs, destination links, and app-link formats.
• Hardened duplicate callback edit handling.
• Improved setup recovery when users send another Maps link mid-flow.
• Suppressed third-party INFO logs that can include token-bearing request URLs.

Deployment Notes

• Railway deployments should mount a persistent volume at /data.
• Set DATA_DIR=/data without quotes.
• Keep exactly one polling worker active for the Telegram bot token.

Known Limitations

• Parsing remains best effort because some Google Maps links do not expose endpoints publicly.
• No browser automation, logged-in Google sessions, or unofficial Google APIs are used.

GINBOT v1.0.0

GINBOT v1.0.0

Summary

Initial Telegram commute-assistant release with Google Routes API monitoring, recurring checks, and JSON persistence.

Added

• Telegram long-polling worker started by python main.py.
• Traffic Duration alerts based on a target drive time.
• Arrive By alerts based on a required arrival time and lead time.
• Google Routes API drive-time lookup.
• JobQueue recurring monitoring.
• Current Alert, Stop Alert, and Snooze actions.
• JSON state storage.
• Railway worker deployment through Procfile.

Changed or Fixed

• No prior public release.

Deployment Notes

• Requires GOOGLE_API_KEY and TELEGRAM_BOT_TOKEN.
• Runs as a single polling worker.
• Uses python main.py as the canonical entry point.

Known Limitations

• One active alert per user.
• Google Maps link parsing is best effort.
• Telegram bots cannot message users before they start or message the bot.