Skip to content

Update dependency @types/dotenv to v8.2.3#479

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/dotenv-8.x
Open

Update dependency @types/dotenv to v8.2.3#479
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/dotenv-8.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jul 5, 2025

This PR contains the following updates:

Package Change Age Confidence
@​types/dotenv 8.2.08.2.3 age confidence

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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
Copy link
Contributor Author

renovate bot commented Jul 5, 2025

⚠️ 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 ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: next-offline@5.0.5
npm ERR! Found: webpack@5.73.0
npm ERR! node_modules/webpack
npm ERR!   dev webpack@"5.73.0" from the root project
npm ERR!   peerOptional webpack@"^4 || ^5" from @next/react-refresh-utils@11.1.4
npm ERR!   node_modules/@next/react-refresh-utils
npm ERR!     @next/react-refresh-utils@"11.1.4" from next@11.1.4
npm ERR!     node_modules/next
npm ERR!       next@"11.1.4" from the root project
npm ERR!       2 more (next-env, next-offline)
npm ERR!   2 more (copy-webpack-plugin, terser-webpack-plugin)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^4.19.1" from next-offline@5.0.5
npm ERR! node_modules/next-offline
npm ERR!   next-offline@"5.0.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   peer webpack@"^4.19.1" from next-offline@5.0.5
npm ERR!   node_modules/next-offline
npm ERR!     next-offline@"5.0.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-02T17_34_16_983Z-debug-0.log

@vercel
Copy link

vercel bot commented Jul 5, 2025

Deployment failed with the following error:

Environment Variable "AUTH0_DOMAIN" references Secret "auth0-domain", which does not exist.

@sonarqubecloud
Copy link

sonarqubecloud bot commented Jul 5, 2025

@renovate renovate bot force-pushed the renovate/dotenv-8.x branch from f5c7093 to 1168342 Compare January 22, 2026 05:56
@vercel
Copy link

vercel bot commented Jan 22, 2026

Deployment failed with the following error:

Environment Variable "AUTH0_DOMAIN" references Secret "auth0-domain", which does not exist.

Learn More: https://vercel.com/docs/environment-variables

@sonarqubecloud
Copy link

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