chore(deps): update development dependencies #95
No reviewers
Labels
No labels
dependencies
major
security-pin
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
trails-cool/trails!95
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/development-deps"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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.
eslinttypescript-eslintturboprettieri18nextreact-i18nextjsdom@types/leafletreact/react-domreach 19.2.8 and@types/react-dom19.2.5 through their existing ranges — no catalog edit needed.No catalog changes, deliberately
pnpm updateinitially rewrote rootpackage.json'sreact/react-domfromcatalog:to^19.2.8, breaking the catalog indirection. Bumping the catalog entries instead madeCI=true pnpm installfail withERR_PNPM_OUTDATED_LOCKFILEand an empty failure reason.Cause:
overridespinsreact/react-domtocatalog:, so pnpm resolves them via the override and omits them from the lockfile'scatalogs: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.json5reviews individually:typescript6.0.3 → 7.0.2,fit-file-parser4.1.0 → 5.0.2.Nothing from the
testing toolinggroup — those must move in lockstep with the Playwright image tag inci.yml.Testing
typecheck 14/14 · lint 14/14 · test 12/12 · openspec 81/0 ·
CI=true pnpm installclean.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.0as older than1.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.cb0802c1719402c4571b