chore(deps): bump @types/googlepay from 0.7.10 to 0.7.11 - #979
chore(deps): bump @types/googlepay from 0.7.10 to 0.7.11#979dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [@types/googlepay](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/googlepay) from 0.7.10 to 0.7.11. - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/googlepay) --- updated-dependencies: - dependency-name: "@types/googlepay" dependency-version: 0.7.11 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
There was a problem hiding this comment.
Safe to merge. This is a patch bump of @types/googlepay (a type-only DefinitelyTyped package) from 0.7.10 to 0.7.11.
What actually changed (diffed the npm tarballs):
index.d.ts: the sole change is a JSDoc comment — a documentation link was removed from the comment on the tokenization token field. There are no type-signature changes.package.json:typeScriptVersionbumped5.2->5.6. The repo uses TypeScript5.6.3(catalog), so the new minimum is satisfied.
Usage check: The google.payments.api.* namespace is consumed in packages/types/uiComponents.ts and packages/ui-components/src/GooglePay/* (PaymentDataRequest, MerchantInfo, PaymentData, CardAuthMethod, CardNetwork, CardFundingSource, PaymentsError, PaymentsClient, PaymentDataError, Address, ErrorReason, CallbackIntent, BillingAddressFormat). None of these were touched by the diff.
Verification: pnpm install + full pnpm build succeeded with 0.7.11 installed, and tsc --noEmit typecheck passed (exit 0) for both the types and @evervault/ui-components packages. No source changes were required. No security or performance concerns (Socket Security and CodeQL checks are green).
Bumps @types/googlepay from 0.7.10 to 0.7.11.
Commits
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)