Skip to content

Website v1.0.5

For everyone: what changed in this release of the website. Released 2026-10-22.

Highlights

The website now runs on the same foundations as the course app: clearer error messages on the two forms, security headers on every page, a health check that tests the database, and logs that never record what visitors type.

Features

None.

Fixes

  • When a form cannot be sent, it now says "Please check the highlighted fields." or "Something went wrong. Please try again." with a reference to quote, instead of technical text. A page left open while the site was updated now shows "Could not reach the server. Please try again." instead of an internal error.
  • If a page fails to load, the site shows a "Something went wrong" page with a Try again button and a reference, instead of a blank error.
  • The site no longer stops when the database restarts, and a slow database no longer leaves a form waiting for minutes.

Operations

  • Every response carries security headers (HSTS, frame, content-type, referrer and permissions policies, and a frame-ancestors content security policy); the X-Powered-By header is gone.
  • /api/health now checks the database: it answers {"data":{"status":"ok"}}, or 503 when the database is unreachable.
  • Logs are structured JSON lines (pino). Each form submission and health check carries a correlation ID, and nothing a visitor typed is written to a log.
  • Configuration is checked: build-time values in src/lib/env.ts and run-time values and secrets in src/lib/server-env.ts. EMAIL_TO and NEXT_PUBLIC_RECAPTCHA_SITE_KEY are now required; LOG_LEVEL and SERVICE_NAME are new and optional. See Configuration.
  • The database driver changed from pg to postgres (as in the course app), with a 10-second connect and 15-second statement timeout.
  • The image runs on Node.js 24.22.1, which fixes the high-severity Node.js vulnerabilities announced on 21 October 2026.
  • CI now also checks formatting, unused code (knip), that migrations match the schema, the integration tests and a production build.

One migration: 0001 stores both created_at columns with their time zone. Existing values are kept as the same instants (they were stored in UTC).

Upgrade notes

  • Developers add EMAIL_TO, NEXT_PUBLIC_RECAPTCHA_SITE_KEY and either real SMTP and reCAPTCHA values or EMAIL_BYPASS=true / RECAPTCHA_BYPASS=true to .env.local; the dev server stops at once when a value is missing.
  • Unit tests (pnpm test) no longer need a database; the database tests run with pnpm test:integration.