Repository navigation
chore(api): remove the pre-2.0 API and its 7-day login tokens - #107
Merged
Merged
Conversation
The old routes (/api/places, /api/events, /api/itinerary, /api/user,
/api/weather; 17 endpoints) were still mounted although nothing calls
them: the web app and Android build use /api/v1 only, and the server
log since the last deploy shows 176 /api/v1 calls and none to the old
routes. They were also a security gap:
- /api/user/login issued 7-day tokens that /api/v1 accepted, so they
outlived sign-out, password reset and session revocation
- /api/user/register skipped validation and terms consent, gave 150 XP
Removed the routes, their controllers, the old auth middleware and rate
limits, config/jwt.ts and the unused Overpass service; verifyAccessToken
no longer accepts { id } tokens. WEATHER_API_KEY and GEMINI_API_KEY are
no longer read. /api/health stays. BACKEND.md now documents /api/v1.
Tests: old routes return 404, an old-style token is refused while a new
login works, /api/health still answers; API suite 147/147.
LEVELING2108
added a commit
that referenced
this pull request
Nov 13, 2026
Release: research into main (remove pre-2.0 API, #107)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The old routes (/api/places, /api/events, /api/itinerary, /api/user, /api/weather; 17 endpoints) were still mounted although nothing calls them: the web app and Android build use /api/v1 only, and the server log since the last deploy shows 176 /api/v1 calls and none to the old routes. They were also a security gap:
Removed the routes, their controllers, the old auth middleware and rate limits, config/jwt.ts and the unused Overpass service; verifyAccessToken no longer accepts { id } tokens. WEATHER_API_KEY and GEMINI_API_KEY are no longer read. /api/health stays. BACKEND.md now documents /api/v1.
Tests: old routes return 404, an old-style token is refused while a new login works, /api/health still answers; API suite 147/147.