Skip to content

fix(ci): reconcile lockfile dependency ranges - #644

Open
woahwhattheheck wants to merge 6 commits into
Agentpay-Org:mainfrom
woahwhattheheck:fix/agentpay-lock-ci-drift-20261006-sol56
Open

woahwhattheheck wants to merge 6 commits into
Agentpay-Org:mainfrom
woahwhattheheck:fix/agentpay-lock-ci-drift-20261006-sol56

Conversation

@woahwhattheheck

@woahwhattheheck woahwhattheheck commented Oct 6, 2026 •

Copy link
Copy Markdown

Fixes the package-manifest/lockfile drift that made npm ci fail before application checks could run.

Current repair

Current head: 3e161b4f7b1b104815fdc7bcbfec8b0864a83e3c.

The branch restores the coherent Node-20 dependency graph from the original Dependabot update while keeping the sponsor's current package.json intent. Relative to current sponsor main, the remaining PR diff is the repaired package-lock.json only.

Hosted CI

Current-head CI run 37518140038:

  • npm ci — passed
  • Next.js 16.3.1 build — dependency/compile phase proceeds, then fails in TypeScript checking
  • bundle-budget and test-with-coverage steps are therefore skipped

The TypeScript diagnostics are not introduced by this lockfile repair. The same diagnostics are present in historical run 32711454021 on original Dependabot head ff42f5145f46216daa0e8da6ec35d06a17c82642, including:

  • useAdminStatusAnnouncement.test.tsx
  • useUsageAnnouncement.test.tsx
  • apiClient.test.ts
  • useApiMutation.test.tsx
  • validateNumber.test.ts BigInt target errors

So this PR fixes install/lock coherence; it does not claim the repository's pre-existing TypeScript test debt is resolved or that current CI is green.

Current CI: https://github.com/Agentpay-Org/Agentpay-frontend/actions/runs/37518140038
Historical comparison: https://github.com/Agentpay-Org/Agentpay-frontend/actions/runs/32711454021

Node 20 compatibility

The CI workflow uses Node 20. Keeping ESLint 9 and jest-dom 6 preserves that supported runtime. The smaller root-spec-only alternative would restore jest-dom 7.0.1, whose locked engine requires Node >=22, and ESLint 10.8.1, which falls outside the locked eslint-plugin-import, eslint-plugin-jsx-a11y, and eslint-plugin-react peer ranges. Its existing run 37762581070 installed only with engine/peer warnings, compiled, and then stopped at the same TypeScript diagnostics before tests could run. It therefore does not establish runtime compatibility and is superseded by this PR's coherent graph.

Compensation

I am claiming this CI repair under @woahwhattheheck and requesting the applicable contribution payment. Please confirm eligibility, assignment, the reward amount, and the payout process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant