#135 · Major dependency upgrades: 5 packages requiring breaking-change review
Last checked with GitLab: . Status comes from GitLab using a 2-minute cache. Merge events clear affected cached statuses. An already-open page does not update itself. Refresh page.
An MR completes this bounty when it is merged into main with Closes #135 and GitLab closes the issue. A mention or an updated timestamp is not completion. Awarded points appear in Activity.
cp .dev.vars.example .dev.vars && pnpm dev, after rebasing on main) and fully test your change before opening the MR.
Description
Rebaseline before selection: the original package list is historical. Inventory current versions and pending Renovate MRs, choose one necessary same-major patch or deliberately approved major, and give it a separate scoped MR. Follow release-age/build-script policy and boot the deployment-shaped image where applicable. No blanket major overrides.
Earlier scope (historical; current qualification above takes precedence)
Background
v5.13.5 catalog patch sweep cleared all minor/patch upgrades. 5 major upgrades remain, each needing dedicated breaking-change review. Listed in v5.13.5 release notes as deferred.
Each warrants its own MR + regression test plan rather than one mega-PR. This issue is the tracker that links to the per-major MRs.
The 5 majors
| Package | From → To | App | Concern | |---|---|---|---| | \@peculiar/x509\ | 1.9.7 → 2.0.0 | apps/tak-service | Full cert-handling API rewrite. tak-service generates client certs for ATAK enrollment — regression risks: cert expiry, key derivation, mTLS handshakes | | \fast-xml-parser\ | 4.5.6 → 5.8.0 | apps/tak-service | Parser config + output-shape changes. HIGH blast radius — used to parse Cursor-on-Target (CoT) XML inbound from ATAK clients. Test multi-marker missions, malformed CoT, large payloads | | \pdf-parse\ | 1.1.4 → 2.4.5 | packages/shared-utils (dev) | Full ESM rewrite. Dev-only impact (bot's \!pdfread\ / article-extractor) — confirm replacement API on attached PDF tests | | \@commitlint/cli\ + \@commitlint/config-conventional\ | 20.5.3 → 21.0.1 | apps/signal-bot | Node 20+ floor. Bot's lefthook commit-msg uses this — confirm node version on bot host (currently \v22.22.2\ so should be fine) | | \@vitejs/plugin-react\ | 5.2.0 → 6.0.1 | apps/developer-portal | Vite 6 peer. Either bump Vite to 6 across the developer-portal client OR pin the plugin at 5.x. Coordinate with the developer-portal lint/logger work in issue #128 |
Approach
Each major gets its own MR:
- Bump in package.json
- \
pnpm install\+ verify lockfile clean - Read the package's CHANGELOG / migration guide
- Update call sites
- \
pnpm turbo typecheck\+ targeted manual test - Land independently with a clear release note entry
Acceptance
- This issue becomes the parent linking 5 MRs
- All 5 majors land or get formally deferred with documented blocker
- \
pnpm outdated -r\shows no \Major\column entries except documented-as-deferred ones
Bounty: L
5 majors × ~2-4 hrs each, depending on call-site count. Bounty split per MR.
<!-- bounty-reconciled:2026-10 -->
Relevant files
No relevant files linked yet.
Hints
No hints yet.
Activity
No points have been awarded for this bounty yet.
Comments
Sign in to join the discussion.
No comments yet. Be the first to weigh in.