The consumer UI has no automated checks. Nothing runs on a push and nothing runs on a pull request, so a dependency upgrade arrives with no evidence either way.
That is already blocking work. The react-router upgrade to v7.18.2 carries a security fix and has been open since 2026-09-09 with no way to tell whether it breaks the app, because react-router v7 changed its routing API and only the build would reveal it.
The app already defines the two commands that would answer the question. A workflow that installs dependencies, runs the type check, then runs the build would fail on an incompatible router version and pass on a safe one.
Add that workflow, triggered on push and on pull request. A test runner would be better still, though the build and type check clear the immediate bar and unblock the queue.
Related to https://github.com/datum-cloud/engineering/issues/414
The consumer UI has no automated checks. Nothing runs on a push and nothing runs on a pull request, so a dependency upgrade arrives with no evidence either way.
That is already blocking work. The react-router upgrade to v7.18.2 carries a security fix and has been open since 2026-09-09 with no way to tell whether it breaks the app, because react-router v7 changed its routing API and only the build would reveal it.
The app already defines the two commands that would answer the question. A workflow that installs dependencies, runs the type check, then runs the build would fail on an incompatible router version and pass on a safe one.
Add that workflow, triggered on push and on pull request. A test runner would be better still, though the build and type check clear the immediate bar and unblock the queue.
Related to https://github.com/datum-cloud/engineering/issues/414