The fkra journal
Changelog · 1 min· 63 reads

The first beta

Releases become tags rather than branch pushes, and the learner surface gets the error handling it was missing.

Changelog

The first beta

The first tagged release. From here on a deploy is something someone cuts on purpose: a tag drives it, and CI has to be green before it moves.

Deploys became deliberate

Until now a merge could reach the world. From this release a deploy is something someone cuts on purpose: a version tag drives it, and the checks have to be green first. Every pull request and every merge into develop runs typecheck, tests and build; a merge into develop ships nothing on its own.

Failure has a place to land

A session that has run out now says so instead of letting the next request fail in silence, and a request that breaks lands on a designed page rather than a blank screen. The same treatment reaches inside the app, where an in-app error panel explains a failed panel without taking the rest of the screen with it.

Also in this release

Added

  • A release workflow that ships from a version tag, and a CI workflow that gates every pull request and every merge into develop.
  • A session-expiry watcher, so a session that has run out says so instead of failing the next request silently.
  • Global error pages and an in-app error panel, so a failure lands somewhere designed rather than on a blank screen.
  • Social icons for the transactional email footer, served from the CDN rather than the repository.

Fixed

  • Landing imagery now loads with the caching and CORS headers the CDN expects, so the hero stops falling back to placeholders.
0
63 views
v1.0.0-beta.1addedfixed
FK
Get the next entry

One email when we publish. Research, product decisions, and what teams report back.