Repository navigation
fix(ci): reconcile lockfile dependency ranges - #644
Open
woahwhattheheck wants to merge 6 commits into
Open
woahwhattheheck wants to merge 6 commits into
woahwhattheheck wants to merge 6 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes the package-manifest/lockfile drift that made
npm cifail 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.jsonintent. Relative to current sponsor main, the remaining PR diff is the repairedpackage-lock.jsononly.Hosted CI
Current-head CI run 37518140038:
npm ci— passedThe 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.tsxuseUsageAnnouncement.test.tsxapiClient.test.tsuseApiMutation.test.tsxvalidateNumber.test.tsBigInt target errorsSo 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.