Skip to main content

FF RESTaurent 1.0.0

Release date: 2026-07-14

Release tag: v1.0.0

Production branch: main

Overview​

Version 1.0.0 completes the Phase 1 launch scope for FF RESTaurent. The release hardens authentication and authorization, protects settlement integrity, completes the shared bill and payment journey, exposes in-app reminders, and adds the automated release gates needed for a controlled deployment.

Phase 1 is complete. The verified develop release candidate was promoted to main, and v1.0.0 records the immutable production release boundary.

Highlights​

Secure group access​

  • Registration requires a private group invite code.
  • JWT sessions have explicit expiry and production secret validation.
  • Production CORS uses an explicit origin allowlist.
  • Login and registration are rate-limited.
  • Demo credentials and automatic demo seeding are disabled in production.
  • The final Head Chef and role-administration boundaries are protected.

Trustworthy bills and settlement​

  • Bill and payment responses never serialize password hashes.
  • Bill edits preserve payment state for unchanged participants.
  • Financial or participant changes are blocked after payment begins.
  • Participant changes and payment corrections are audited.
  • Payment updates support both PAID and WAITING with optimistic conflict protection.
  • Bill previews use the authoritative shared calculation and reconcile every participant share before submission.
  • Multiple fixed or percentage discounts and coded vouchers are supported.

Complete payment and notification journey​

  • Bill managers can provide a validated HTTPS payment link.
  • Customers can open the payment target directly from bill detail.
  • Users can correct payment mistakes through a confirmed, audited action.
  • The notification bell shows unread reminders and navigates to the bill.
  • Reminder delivery excludes settled participants and applies a 15-minute per-recipient cooldown.
  • Transient data failures no longer sign users out or discard loaded data.

Release readiness​

  • CI uses deterministic installation and requires lint, typecheck, tests, production builds, PostgreSQL integration coverage, and Playwright smoke journeys.
  • Customer, Sous Chef, and Head Chef launch journeys are covered in Chromium, with an additional 390px mobile overflow check.
  • /ready verifies database connectivity separately from /health.
  • Staging smoke and scheduled backup/restore-drill workflows are included.
  • Structured launch events cover login, bill creation, payment changes, and request failures.
  • The production deployment and rollback procedure is documented in the Production Runbook.

Production web delivery​

  • React Router Data Mode provides direct, browser-history URLs with lazy-loaded page modules and route-level error handling.
  • The Render Static Site configuration rewrites client routes to index.html, preventing direct URL and refresh failures.
  • Hashed JavaScript and CSS assets use long-lived immutable browser caching.
  • The login screen begins a user-triggered API warm-up, and authenticated bootstrap requests run concurrently where authorization permits.
  • The fixed responsive application shell, bilingual interface, theme controls, searchable dropdowns, and container-only scrolling are included in the production release.

API changes​

  • Registration payloads now require inviteCode.

  • Payment updates use:

    PATCH /bills/:id/participants/:memberId/payment

    with status and expectedStatus in the JSON body.

  • Expected client failures return stable error codes and 4xx responses.

  • GET /ready returns 503 when PostgreSQL is unavailable.

  • Bill responses include an optional paymentUrl.

Database migration​

Migration 20260711000000_add_payment_url adds the nullable Bill.paymentUrl column. Apply it before starting the 1.0.0 API:

npm run prisma:migrate:deploy -w @ff-restaurent/api

Production migrations are a separate release step. Application startup does not seed demo accounts in production.

Required production configuration​

DATABASE_URL=postgresql://USER:PASSWORD@HOST:5432/ff_restaurent?schema=public
JWT_SECRET=use-a-random-secret-with-at-least-32-characters
JWT_EXPIRES_IN=8h
CORS_ORIGINS=https://app.example.com
REGISTRATION_INVITE_CODE=use-a-private-group-invite
API_PORT=4000
VITE_API_URL=https://api.example.com

Verification record​

  • Lint: passed across all workspaces.
  • Typecheck: passed across all workspaces.
  • API contract and PostgreSQL integration tests: 7 passed.
  • Shared bill-calculation tests: 4 passed.
  • Chromium journeys: Customer, Sous Chef, Head Chef, and mobile layout passed.
  • Production builds: API, web, and shared packages passed.
  • Authenticated staging smoke: passed against the disposable release database.
  • Prisma schema validation and all three migrations: passed.
  • React Router startup, login error handling, API warm-up, and concurrent loader regression tests: passed.
  • Render production configuration syntax and the web production bundle: passed.

Release closure​

  1. Phase 1 implementation and release gates completed on develop.
  2. The release candidate was promoted through the reviewed develop → main workflow.
  3. Production migrations, health/readiness checks, smoke coverage, rollback controls, and recovery procedures are documented and accepted for release.
  4. The final release boundary is recorded by the annotated v1.0.0 tag on main.
  5. Phase 1 Linear work, FF-5 through FF-21, is closed; later roadmap phases remain open independently.

Known limitations and next phase​

Render Free web services can introduce cold-start delay after idle periods. The web client warms the API during login as a temporary mitigation; an always-on API instance is the production-grade remedy.

Phase 2 owns deeper delivery optimization, scalable search and pagination, restaurant enrichment, reusable Cuisine and Dining Area catalogs, Collections, Feedback, structured Vietnamese addresses, and member-management improvements. The maintained roadmap and ticket-level contracts live in Linear rather than in this immutable release note.