Release as 5.0.0 instead of 4.2.0

CHANGELOG.md

@@ -11,7 +11,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 > from git history and grouped by theme rather than exhaustive per-commit
 > detail.
 
-## [4.2.0] - 2026-10-02
+## [5.0.0] - 2026-10-04
 
 ### Added
 - **Import a GPS-tagged GoPro video as a session.** Every GoPro since the

docs/plans/0022-drag-mode.md

@@ -2,7 +2,7 @@
 
 > Status: **DONE** — all four commits below landed (detector first,
 > logic-first like plan 0015, then mapping, orchestration and UI); ships in
-> 4.2.0. The follow-ups section is deliberately out of scope for v1.
+> 5.0.0. The follow-ups section is deliberately out of scope for v1.
 
 ## Why this exists
 
@@ -111,7 +111,7 @@ Course-less pre-application (drag runs, and the waypoint fallback) goes
 through `applyCourselessLaps`, which **clears the course selection** first. The
 loader carries the previous file's selection into a new load, and a drag
 session left holding it kept `canSnapshot` live — a 10-second run could replace
-that course's snapshot and cloud-sync it (4.2.0 release review A1).
+that course's snapshot and cloud-sync it (5.0.0 release review A1).
 `useLapSnapshots` also refuses drag sessions outright (`snapshotEligible`), and
 every "fastest" pick in the app goes through `fastestRankedLap`, never a bare
 min-reduce (A2).

docs/plans/0024-native-export-bridge.md

@@ -142,7 +142,7 @@ export shortcut goes away. The pure parts — ordering, totals, labels,
 applying a removal, byte formatting — live in `deviceVideos.ts` with tests;
 the panel is a thin view.
 
-## Follow-up 4 (landed): release-review hardening (4.2.0)
+## Follow-up 4 (landed): release-review hardening (5.0.0)
 
 - **Stale copy, wrong session.** `loadRecording`'s background copy set
   `nativeStoredKey` whenever it resolved, so a copy that finished after a

docs/plans/0027-precache-resilience.md

@@ -52,7 +52,7 @@ service worker at all.
 
 `DEFERRED_ASSET_DIRS` (`samples/`, `loggers/`) is the single source of truth —
 it lives in `scripts/deferredAssets.ts` (moved out of `vite.config.ts` after the
-4.2.0 release review so the runtime-cache route, previously a hand-copied regex,
+5.0.0 release review so the runtime-cache route, previously a hand-copied regex,
 could be derived from it and unit-tested). It feeds three things:
 
 1. `globIgnores` — those directories stay out of the install-blocking precache.
@@ -93,7 +93,7 @@ The route deliberately has no `ExpirationPlugin`: entries written by the client
 aren't in the plugin's own index, and a fixed set of build assets has nothing to
 expire.
 
-### Revision the deferred cache (follow-up, 4.2.0 release review PERF-1)
+### Revision the deferred cache (follow-up, 5.0.0 release review PERF-1)
 
 Moving `samples/` and `loggers/` out of the precache also moved them out of
 Workbox's per-file revisioning, and the runtime route is `CacheFirst` with no

docs/plans/0029-gopro-gps-video-import.md

@@ -90,7 +90,7 @@ the C library).
   extractor stays off the main chunk.
 - `src/lib/gopro/goproDetect.ts` — the cheap eager gates (`isGoProVideoFile`,
   `isGoProVideoBuffer`) the routers call on every import.
-- Hardening (4.2.0 review): a malformed GPS stream skips its payload instead of
+- Hardening (5.0.0 review): a malformed GPS stream skips its payload instead of
   aborting the import, and a uniform `stsz` count is capped at
   `fileSize / sampleSize` so a hostile MP4 can't allocate billions of entries.
 - `src/lib/gopro/videoHandoff.ts` — one-shot pending video for a session.

package.json

@@ -1,7 +1,7 @@
 {
   "name": "doves-dataviewer",
   "private": true,
-  "version": "4.2.0",
+  "version": "5.0.0",
   "description": "Open-source, offline-first motorsport telemetry viewer (Dove's DataViewer / LapWing).",
   "license": "GPL-3.0-or-later",
   "author": "TheAngryRaven",