• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Unleash / unleash / 26509634955
87%
master: 91%

Build:
Build:
LAST BUILD BRANCH: main
DEFAULT BRANCH: master
Ran 27 May 2026 12:06PM UTC
Jobs 1
Files 1180
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

27 May 2026 11:56AM UTC coverage: 87.125%. Remained the same
26509634955

push

github

web-flow
chore: update react router step 1: relativeSplatPath (#12080)

Part of the gradual migration to React Router v7. Opts the app into v7's
`relativeSplatPath` behavior behind an internal flag
(`reactRouter_v7_relativeSplatPath`) so we can roll it out controllably
and fall back if something regresses in production.

## What this does

- Adds a new internal feature flag `reactRouter_v7_relativeSplatPath`
(defaults off in OSS, on in dev).
- Wires the flag to `<BrowserRouter future={{ v7_relativeSplatPath }}>`
in `frontend/src/index.tsx`.
- Pins the flag to `true` in `testRenderer.tsx` so tests run under the
new behavior.
- Fixes one site that broke under the new resolution semantics: the
project-settings vertical tabs in `ProjectSettings.tsx`. Both the
`onChange` handler and the catch-all `<Navigate>` were passing relative
tab IDs (`'access'`, `''`, etc.) into `navigate`/`<Navigate>`. Under v7
these append to the current URL instead of resolving against the route
mount; switched them to absolute paths derived from `location.pathname`.

## Why

Under v7, `navigate('access')` from `/projects/X/settings/segments`
resolves to `/projects/X/settings/segments/access` (appending) rather
than `/projects/X/settings/access` (replacing). This is the v7-correct
behavior — splat captures are no longer silently stripped during
relative-path resolution — but it surfaced a latent bug in the settings
tab navigation that was relying on the old (buggy) v6 behavior.

## Migration reference

- React Router v6 → v7 upgrade guide for this flag:
https://reactrouter.com/upgrading/v6#v7_relativesplatpath
- `useResolvedPath` docs explaining the resolution change:
https://reactrouter.com/6.30.3/hooks/use-resolved-path#splat-paths

---------

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

1852 of 2047 branches covered (90.47%)

15118 of 17352 relevant lines covered (87.13%)

920.61 hits per line

Coverage Regressions

Lines Coverage ∆ File
1
86.05
-0.78% src/lib/services/api-token-service.ts
Jobs
ID Job ID Ran Files Coverage
1 26509634955.1 27 May 2026 12:06PM UTC 1180
87.13
GitHub Action Run
Source Files on build 26509634955
  • Tree
  • List 1180
  • Changed 3
  • Source Changed 1
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #26509634955
  • d2268bbe on github
  • Prev Build on main (#26441993136)
  • Next Build on main (#26520568826)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc