chore(deps): update development dependencies #95

Merged
ullrich merged 1 commit from chore/development-deps into main 2026-08-24 16:23:08 +00:00
Owner

Replaces #86, which was conflicted and proposed openspec 1.9.0 — already superseded by 1.10.0 in #94.

Rebuilt against current main rather than merging #86's lockfile. Hand-merging a stale lockfile is exactly what caused #66 to silently revert three merged PRs, so this re-resolves from scratch.

eslint 10.7.0 → 10.9.0
typescript-eslint 8.63.0 → 8.67.0
turbo 2.10.4 → 2.10.11
prettier 3.9.5 → 3.9.6
i18next 26.3.6 → 26.4.0
react-i18next 17.0.9 → 17.0.12
jsdom 30.0.0 → 30.0.1
@types/leaflet 1.9.21 → 1.9.22

react/react-dom reach 19.2.8 and @types/react-dom 19.2.5 through their existing ranges — no catalog edit needed.

No catalog changes, deliberately

pnpm update initially rewrote root package.json's react/react-dom from catalog: to ^19.2.8, breaking the catalog indirection. Bumping the catalog entries instead made CI=true pnpm install fail with ERR_PNPM_OUTDATED_LOCKFILE and an empty failure reason.

Cause: overrides pins react/react-dom to catalog:, so pnpm resolves them via the override and omits them from the lockfile's catalogs: block — true on main as well (19 entries there, not 21). Editing catalog entries under an override is separate work; left to Renovate.

Also excluded

Majors, which renovate.json5 reviews individually: typescript 6.0.3 → 7.0.2, fit-file-parser 4.1.0 → 5.0.2.

Nothing from the testing tooling group — those must move in lockstep with the Playwright image tag in ci.yml.

Testing

typecheck 14/14 · lint 14/14 · test 12/12 · openspec 81/0 · CI=true pnpm install clean.

Diffed every resolved version against main: 29 upgrades, 0 downgrades. The comparator self-tests numeric ordering first, because the naive string compare reads 1.10.0 as older than 1.6.0 — my first attempt at this check had exactly that bug. This diff is the check whose absence let the #66 revert through, and it's worth making routine on any lockfile-touching branch.

Replaces #86, which was conflicted and proposed openspec 1.9.0 — already superseded by 1.10.0 in #94. **Rebuilt against current main rather than merging #86's lockfile.** Hand-merging a stale lockfile is exactly what caused #66 to silently revert three merged PRs, so this re-resolves from scratch. | | | |---|---| | `eslint` | 10.7.0 → 10.9.0 | | `typescript-eslint` | 8.63.0 → 8.67.0 | | `turbo` | 2.10.4 → 2.10.11 | | `prettier` | 3.9.5 → 3.9.6 | | `i18next` | 26.3.6 → 26.4.0 | | `react-i18next` | 17.0.9 → 17.0.12 | | `jsdom` | 30.0.0 → 30.0.1 | | `@types/leaflet` | 1.9.21 → 1.9.22 | `react`/`react-dom` reach 19.2.8 and `@types/react-dom` 19.2.5 through their existing ranges — no catalog edit needed. ## No catalog changes, deliberately `pnpm update` initially rewrote root `package.json`'s `react`/`react-dom` from `catalog:` to `^19.2.8`, breaking the catalog indirection. Bumping the catalog entries instead made `CI=true pnpm install` fail with `ERR_PNPM_OUTDATED_LOCKFILE` and an *empty* failure reason. Cause: `overrides` pins `react`/`react-dom` to `catalog:`, so pnpm resolves them via the override and omits them from the lockfile's `catalogs:` block — true on main as well (19 entries there, not 21). Editing catalog entries under an override is separate work; left to Renovate. ## Also excluded Majors, which `renovate.json5` reviews individually: `typescript` 6.0.3 → 7.0.2, `fit-file-parser` 4.1.0 → 5.0.2. Nothing from the `testing tooling` group — those must move in lockstep with the Playwright image tag in `ci.yml`. ## Testing typecheck 14/14 · lint 14/14 · test 12/12 · openspec 81/0 · `CI=true pnpm install` clean. Diffed every resolved version against main: **29 upgrades, 0 downgrades**. The comparator self-tests numeric ordering first, because the naive string compare reads `1.10.0` as older than `1.6.0` — my first attempt at this check had exactly that bug. This diff is the check whose absence let the #66 revert through, and it's worth making routine on any lockfile-touching branch.
chore(deps): update development dependencies
Some checks failed
CD Staging / Build & Push Docker Images (pull_request) Has been skipped
CD Staging / Build & Push Docker Images-1 (pull_request) Has been skipped
CD Staging / Deploy Staging (pull_request) Has been skipped
CD Staging / Deploy PR Preview (pull_request) Has been skipped
CD Staging / Tear Down PR Preview (pull_request) Has been skipped
CI / Security Scan (pull_request) Successful in 41s
CI / Dockerfile Package Check (pull_request) Successful in 13s
CI / Checks (pull_request) Successful in 4m42s
CI / Visual Tests (pull_request) Successful in 2m22s
CI / Journal Image Smoke Test (pull_request) Successful in 17m20s
CI / E2E Tests (pull_request) Failing after 44m56s
cb0802c171
Replaces #86, which was conflicted and proposed openspec 1.9.0 — already
superseded by 1.10.0 in #94. Rebuilt against current main rather than merging its
stale lockfile, since hand-merging a stale lockfile is what caused #66 to
silently revert three merged PRs.

  eslint             10.7.0  -> 10.9.0
  typescript-eslint  8.63.0  -> 8.67.0
  turbo              2.10.4  -> 2.10.11
  prettier           3.9.5   -> 3.9.6
  i18next            26.3.6  -> 26.4.0
  react-i18next      17.0.9  -> 17.0.12
  jsdom              30.0.0  -> 30.0.1
  @types/leaflet     1.9.21  -> 1.9.22

react/react-dom reach 19.2.8 and @types/react-dom 19.2.5 through their existing
ranges, with no catalog edit needed.

DELIBERATELY NO CATALOG CHANGES. `pnpm update` initially rewrote root
package.json's react/react-dom from `catalog:` to `^19.2.8`, breaking the catalog
indirection, and bumping the catalog entries then made `CI=true pnpm install`
fail with ERR_PNPM_OUTDATED_LOCKFILE and an empty failure reason. `overrides`
pins react/react-dom to `catalog:`, so pnpm resolves them through the override
and omits them from the lockfile's `catalogs:` block (true on main too — 19
entries there, not 21). Editing catalog entries under an override is a distinct
piece of work; left to Renovate.

Also excluded, as majors that renovate.json5 reviews individually:
typescript 6.0.3 -> 7.0.2, fit-file-parser 4.1.0 -> 5.0.2. And nothing from the
"testing tooling" group, which must move in lockstep with the Playwright image
tag in ci.yml.

Verified: typecheck 14/14, lint 14/14, test 12/12, openspec 81/0, and
`CI=true pnpm install` clean. Diffed every resolved version against main —
29 upgrades, 0 downgrades — using a comparator that self-tests numeric ordering
first, since the naive string compare reads 1.10.0 as older than 1.6.0. That
diff is the check whose absence let the #66 revert through.
ullrich force-pushed chore/development-deps from cb0802c171
Some checks failed
CD Staging / Build & Push Docker Images (pull_request) Has been skipped
CD Staging / Build & Push Docker Images-1 (pull_request) Has been skipped
CD Staging / Deploy Staging (pull_request) Has been skipped
CD Staging / Deploy PR Preview (pull_request) Has been skipped
CD Staging / Tear Down PR Preview (pull_request) Has been skipped
CI / Security Scan (pull_request) Successful in 41s
CI / Dockerfile Package Check (pull_request) Successful in 13s
CI / Checks (pull_request) Successful in 4m42s
CI / Visual Tests (pull_request) Successful in 2m22s
CI / Journal Image Smoke Test (pull_request) Successful in 17m20s
CI / E2E Tests (pull_request) Failing after 44m56s
to 9402c4571b
All checks were successful
CD Staging / Build & Push Docker Images (pull_request) Has been skipped
CD Staging / Build & Push Docker Images-1 (pull_request) Has been skipped
CD Staging / Deploy Staging (pull_request) Has been skipped
CD Staging / Deploy PR Preview (pull_request) Has been skipped
CI / Security Scan (pull_request) Successful in 39s
CI / Dockerfile Package Check (pull_request) Successful in 15s
CI / Checks (pull_request) Successful in 5m4s
CI / Visual Tests (pull_request) Successful in 2m11s
CI / Journal Image Smoke Test (pull_request) Successful in 15m27s
CI / E2E Tests (pull_request) Successful in 7m20s
Cancel superseded CI / Cancel in-flight CI (pull_request) Successful in 12s
CD Staging / Tear Down PR Preview (pull_request) Successful in 31s
2026-08-24 15:51:26 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
trails-cool/trails!95
No description provided.