Skip to content

Update dependency react-google-recaptcha to v1.1.0#84

Open
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/react-google-recaptcha-1.x
Open

Update dependency react-google-recaptcha to v1.1.0#84
renovate[bot] wants to merge 1 commit into
developmentfrom
renovate/react-google-recaptcha-1.x

Conversation

@renovate

@renovate renovate Bot commented Nov 27, 2020

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
react-google-recaptcha 1.0.51.1.0 age confidence

Release Notes

dozoisch/react-google-recaptcha (react-google-recaptcha)

v1.1.0

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM (* 0-3 * * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/react-google-recaptcha-1.x branch from e5be219 to 1440e29 Compare September 25, 2022 16:31
@renovate renovate Bot force-pushed the renovate/react-google-recaptcha-1.x branch from 1440e29 to 835455f Compare July 9, 2023 07:51
@renovate renovate Bot force-pushed the renovate/react-google-recaptcha-1.x branch from 835455f to 9bc1c81 Compare August 10, 2025 13:09
@renovate renovate Bot force-pushed the renovate/react-google-recaptcha-1.x branch from 9bc1c81 to ed1f6fc Compare August 31, 2025 10:18
@renovate

renovate Bot commented Aug 31, 2025

Copy link
Copy Markdown
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: eslint-plugin-graphql@2.1.1
npm warn Found: graphql@14.2.0
npm warn node_modules/graphql
npm warn   peer graphql@"^14.1.0" from @gatsbyjs/relay-compiler@2.0.0-printer-fix.2
npm warn   node_modules/@gatsbyjs/relay-compiler
npm warn     @gatsbyjs/relay-compiler@"2.0.0-printer-fix.2" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn   9 more (apollo-link, apollo-utilities, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer graphql@"^0.12.0 || ^0.13.0" from eslint-plugin-graphql@2.1.1
npm warn node_modules/eslint-plugin-graphql
npm warn   eslint-plugin-graphql@"^2.0.0" from gatsby@2.3.4
npm warn   node_modules/gatsby
npm warn
npm warn Conflicting peer dependency: graphql@0.13.2
npm warn node_modules/graphql
npm warn   peer graphql@"^0.12.0 || ^0.13.0" from eslint-plugin-graphql@2.1.1
npm warn   node_modules/eslint-plugin-graphql
npm warn     eslint-plugin-graphql@"^2.0.0" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: express-graphql@0.6.12
npm warn Found: graphql@14.2.0
npm warn node_modules/graphql
npm warn   peer graphql@"^14.1.0" from @gatsbyjs/relay-compiler@2.0.0-printer-fix.2
npm warn   node_modules/@gatsbyjs/relay-compiler
npm warn     @gatsbyjs/relay-compiler@"2.0.0-printer-fix.2" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm warn   9 more (apollo-link, apollo-utilities, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0" from express-graphql@0.6.12
npm warn node_modules/express-graphql
npm warn   express-graphql@"^0.6.12" from gatsby@2.3.4
npm warn   node_modules/gatsby
npm warn
npm warn Conflicting peer dependency: graphql@0.13.2
npm warn node_modules/graphql
npm warn   peer graphql@"^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0" from express-graphql@0.6.12
npm warn   node_modules/express-graphql
npm warn     express-graphql@"^0.6.12" from gatsby@2.3.4
npm warn     node_modules/gatsby
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: gatsby-plugin-sass@2.0.11
npm error Found: node-sass@7.0.0
npm error node_modules/node-sass
npm error   node-sass@"7.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer node-sass@"^4.9.0" from gatsby-plugin-sass@2.0.11
npm error node_modules/gatsby-plugin-sass
npm error   gatsby-plugin-sass@"2.0.11" from the root project
npm error
npm error Conflicting peer dependency: node-sass@4.14.1
npm error node_modules/node-sass
npm error   peer node-sass@"^4.9.0" from gatsby-plugin-sass@2.0.11
npm error   node_modules/gatsby-plugin-sass
npm error     gatsby-plugin-sass@"2.0.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-07-12T10_49_30_968Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-07-12T10_49_30_968Z-debug-0.log

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.

0 participants