Part 8: Release v1.2.0: KV → D1 Telemetry Migration & Drive Distribution
Part 8: Release v1.2.0 — KV → D1 Telemetry Migration, Drive Distribution & Update Nudge
Two weeks after v1.1.0, I released SpringBored TOKEN1 (merge commit bd273f5, PR #3) across both SpringBored (Course Edition course-v1.2.0) and SpringBored - Assessment (Assessment Edition assessment-v1.2.0).
This is a maintenance and infrastructure release. No course-runner or assessment-solving behavior changed. The three drivers were:
1. Telemetry backend exhausted the Cloudflare Workers KV free tier — 1,000 put operations per day is not enough for per-event telemetry from active users. Writes started returning HTTP 429.
2. GitHub Release assets needed a temporary home while the repository's release packaging workflow is being reworked.
3. Manifest version bump to 1.2.0 so existing v1.1.0 users receive the built-in update nudge banner in the popup and HUD.
Here is everything that shipped in v1.2.0.
1. Telemetry Backend Migrated from Cloudflare Workers KV to D1
The live usage heatmap and aggregate impact counters on springbored.ojasdeshpande.in are powered by anonymous telemetry events posted from both extensions' background.js every time you complete a lecture, solve a question, or finish an assessment. Each event carries:
{
"edition": "course | assessment",
"version": "1.2.0",
"installId": "<random-anonymous-uuid>",
"event": "lecture_completed | question_solved | assessment_completed | ...",
"deltas": { "lecturesCompleted": 1, "savedSeconds": 420, ... }
}
In v1.1.0 and earlier, the Worker at https://springbored.ojasdeshpande.in/api/telemetry wrote each event to a Cloudflare Workers KV namespace (SPRINGBORED_KV). The Workers Free plan allows 1,000 put operations per day. With even a few dozen daily active users generating multiple events each, that limit was hit within hours, and subsequent writes returned 429 Too Many Requests — silently dropping telemetry.
In v1.2.0, the telemetry endpoint now persists to Cloudflare D1 (SPRINGBORED_DB) instead. The Workers Free plan includes 100,000 row writes per day on D1 — two orders of magnitude more headroom. The migration steps:
- Created
SPRINGBORED_DBwith atelemetry_eventstable (installId,edition,version,event,deltas_json,receivedAt). - Ran a one-time seed script that scanned all KV keys, parsed the aggregated counters, and inserted synthetic daily rollup rows so the public heatmap and totals remain continuous.
- Kept
SPRINGBORED_KVas a fallback: if the D1 write fails (timeout, schema error, maintenance), the Worker falls back to KV so no events are lost. - Updated
PRIVACY.mdandSecurity.mdto reflect the dual-store architecture.
The Worker code change in Backend/worker.js (deployed via Wrangler) is minimal:
// Telemetry handler — D1 primary, KV fallback
async function handleTelemetry(request, env) {
const body = await request.json();
const stmt = env.SPRINGBORED_DB.prepare(`
INSERT INTO telemetry_events (installId, edition, version, event, deltas_json, receivedAt)
VALUES (?, ?, ?, ?, ?, ?)
`);
try {
await stmt.bind(body.installId, body.edition, body.version, body.event, JSON.stringify(body.deltas), Date.now()).run();
return new Response('ok');
} catch (e) {
// Fallback to KV if D1 is down
await env.SPRINGBORED_KV.put(`telemetry:${Date.now()}:${crypto.randomUUID()}`, JSON.stringify(body));
return new Response('ok (kv fallback)');
}
}
2. Temporary Google Drive Distribution
While the GitHub Releases asset pipeline is being reworked, v1.2.0 archives are hosted in a Google Drive folder:
📁 Google Drive Release Folder (v1.2.0)
Both editions are available:
SpringBored-Course-v1.2.0.zip(311 KB)SpringBored-Assessment-v1.2.0.zip(357 KB)
All documentation (README.md, How_To_Use.md, CHANGELOG.md, PRIVACY.md, Security.md, CONTRIBUTING.md, DISCLAIMER.md, and the .github/ISSUE_TEMPLATE/bug_report.md) now points to this Drive folder for downloads. Once the GitHub Releases workflow is restored, the Drive links will be replaced with edition-anchored release URLs (.../releases/tag/course-v1.2.0, .../releases/tag/assessment-v1.2.0).
3. Manifest Version Bump & Update Nudge
Both manifest.json files now report "version": "1.2.0":
// SpringBored/manifest.json
{ "manifest_version": 3, "name": "SpringBored", "version": "1.2.0", ... }
// SpringBored - Assessment/manifest.json
{ "manifest_version": 3, "name": "SpringBored (Assessment Edition)", "version": "1.2.0", ... }
The extensions' background.js runs checkForExtensionUpdate() every 12 hours (and on demand via the Updates button in the popup footer). It queries https://springbored.ojasdeshpande.in/api/version (with a fallback to the GitHub Releases API), compares the returned latestVersion against chrome.runtime.getManifest().version, and shows the gold NEW badge when a newer version exists.
Because v1.1.0 users have "version": "1.1.0" in their installed manifest, the bump to 1.2.0 automatically triggers the update nudge — no user action required beyond clicking Reload on chrome://extensions/ after extracting the new zip.
Zero Behavior Changes
This release intentionally changes no runtime behavior:
- Course Edition video speed (
16×), seek offset (duration - 3s), TOC expansion, modal handling — identical. - Assessment Edition DOM scraper, Gemini fallback chain, two-pass critic, cross-origin iframe relay, Fullscreen HUD (
Alt + S) — identical. - Consent gate (
sbConsent.versionupdated to"1.2.0"), local stats, telemetry schema — identical.
4. v1.2.0 Release Packages & How to Upgrade
If you are already running v1.1.0, you will see the gold NEW badge (v1.2.0) appear in your extension popup and Assessment HUD automatically. To upgrade without losing your saved Gemini API key, personal impact stats, or consent acceptance:
1. Download the v1.2.0 zip for your edition from the Google Drive release folder and extract it over your existing extension folder (or run git pull if you cloned the repository).
2. Open chrome://extensions/ and click the Reload (↻) icon on the extension card.
Links & Resources
- GitHub Pull Request (
PR #3): github.com/OjasD07/SpringBored/pull/3 - Merge Commit:
bd273f5(includesc041c92docs sync +2f64b87version bump) - Official Website & Live 52-Week Heatmap: springbored.ojasdeshpande.in
- Support My Open-Source Work: sponsor.ojasdeshpande.in
Series Navigation: ← Previous: Part 7: Release TOKEN0 — Collapsible AI Drawer, Popup Refresh & HUD Upgrades | Back to Series Home: Building SpringBored | All Articles