Repository navigation
fix: upgrade Stripe.js to 10.2.0 and retain patched test tooling - #2400
Open
dependabot[bot] wants to merge 5 commits into
Open
dependabot[bot] wants to merge 5 commits into
dependabot[bot] wants to merge 5 commits into
Conversation
Bumps [@stripe/stripe-js](https://github.com/stripe/stripe-js) from 9.17.0 to 10.0.0. - [Release notes](https://github.com/stripe/stripe-js/releases) - [Commits](stripe/stripe-js@v9.17.0...v10.0.0) --- updated-dependencies: - dependency-name: "@stripe/stripe-js" dependency-version: 10.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Important Review skippedBot user detected. To trigger a single review, invoke the
 |
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.OpenSSF ScorecardScorecard details
Scanned Files
|
groupthinking
requested changes
Oct 28, 2026
groupthinking
left a comment
groupthinking
left a comment
Owner
There was a problem hiding this comment.
Review at head bb8c28e0: this PR changes apps/web/package.json without updating the root package-lock.json, and current-head build, lint, and frontend test checks fail. Reconcile the workspace lockfile with the manifest, then rerun the checks before approval.
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
groupthinking
previously approved these changes
Oct 28, 2026
groupthinking
left a comment
groupthinking
left a comment
Owner
There was a problem hiding this comment.
Code review at b9d3666153213e28dc5b56660d74b58ece8afc15: the earlier manifest/lockfile and failing-check concerns are resolved. The two-file diff updates @stripe/stripe-js to 10.2.0; clean install, web tests (1,520 passed, 28 skipped), lint, type check, and production build passed locally, and current hosted checks show 26 passed and 3 skipped. A repository source search found no import or loader call for Stripe.js; current browser checkout paths redirect to server-provided Checkout URLs. The Stripe.js 10 Payment Request Button and Elements changes therefore do not alter a current in-app call site.
I approve the code change at this head. This is not a merge recommendation or a payment transaction verdict. The shared dependency-review job still fails after a 3-base/1-head snapshot comparison and has no reliable evidence artifact. Keep the PR open until that check is corrected. Any future client-side Stripe.js integration needs its own browser test.
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
Contributor
Author
|
A newer version of @stripe/stripe-js exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged. |
groupthinking
changed the title
Contributor
✅ E2E Test Results: ALL TESTS PASSED
Test Output |
This branch was successfully deployed
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.
Current main integration — 2026-11-02
Head
8634445b61c3293cad65c0d5d435bff59d50c84dmerges current mainffd07a012ddae375096d0ac0f7d20faa680464feinto the existing Stripe update without rewriting its history. The PR still changes onlyapps/web/package.jsonand the rootpackage-lock.json: the app declares@stripe/stripe-js ^10.0.0and resolves 10.2.0. The original branch's Vitest 4.1.12 / tinyrainbow 3.2.0 lock updates remain, and all other current-main manifest and lock records are preserved.A fresh source scan found no
@stripe/stripe-js,loadStripe, orredirectToCheckoutcall inapps/web/src. Current checkout and renewal components navigate to the URL created by the server-side Stripe integration. Loading the installed Stripe.js pure module from the actual web consumer succeeded and exposed its loader; no browser loader or payment transaction was invoked.Local validation used Node 24.20.0 and npm 10.8.0:
npx --yes npm@10.8.0 ci --ignore-scriptsandnpx --yes npm@10.8.0 run postinstall --workspace apps/webpassed.npx --yes npm@10.8.0 run test --workspace apps/web -- --maxWorkers=2passed 1,534 tests across 176 files, with 28 skipped, including existing checkout, renewal and billing regressions.npx --yes npm@10.8.0 run type-check --workspace apps/web,npx --yes npm@10.8.0 run lint --workspace apps/web, andNEXT_TELEMETRY_DISABLED=1 npx --yes npm@10.8.0 run build:webpassed; build generated 53/53 static pages.git diff --checkpassed.npx --yes npm@10.8.0 ls --all --jsonremains nonzero with exactly the seven issues also reproduced on current main: two extraneous platform package records, two OpenTelemetry peer-version conflicts, and three existing Nest/SWC peer gaps. No graph issue was added.Security dependency evidence
The retained root Vitest patch resolves
@vitest/mocker 4.1.11 → 4.1.12and removes its two moderate advisory entries, GHSA-qxg6-89mg-rqv8 and GHSA-xp26-3454-mjgp, from the current-main comparison. Mocker remains a transitive development dependency; no package was promoted into application dependencies.npx --yes npm@10.8.0 audit --json --package-lock-onlystill reports 56 records (25 high, 31 moderate) versus main's 58 (25 high, 33 moderate), with no new primary advisory. This PR does not claim a clean repository security audit. Rollback should use a reviewed revert; reverting the retained Vitest patch would restore those advisory findings.Hosted checks, dependency-review artifacts and review decisions for this new head are pending. Keep this PR unmerged until current-head hosted dependency evidence is verified. No live payment, production deployment or merge was performed for this local repair; a future Stripe.js browser integration requires its own browser validation.