Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency dotenv to v16.4.7 #430

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 16, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
dotenv 16.0.0 -> 16.4.7 age adoption passing confidence

Release Notes

motdotla/dotenv (dotenv)

v16.4.7

Compare Source

Changed
  • Ignore .tap folder when publishing. (oops, sorry about that everyone. - @​motdotla) #​848

v16.4.6

Compare Source

Changed
  • Clean up stale dev dependencies #​847
  • Various README updates clarifying usage and alternative solutions using dotenvx

v16.4.5

Compare Source

Changed
  • 🐞 fix recent regression when using path option. return to historical behavior: do not attempt to auto find .env if path set. (regression was introduced in 16.4.3) #​814

v16.4.4

Compare Source

Changed
  • 🐞 Replaced chaining operator ?. with old school && (fixing node 12 failures) #​812

v16.4.3

Compare Source

Changed
  • Fixed processing of multiple files in options.path #​805

v16.4.2

Compare Source

Changed

v16.4.1

Compare Source

  • Patch support for array as path option #​797

v16.4.0

Compare Source

  • Add error.code to error messages around .env.vault decryption handling #​795
  • Add ability to find .env.vault file when filename(s) passed as an array #​784

v16.3.2

Compare Source

Added
  • Add debug message when no encoding set #​735
Changed
  • Fix output typing for populate #​792
  • Use subarray instead of slice #​793

v16.3.1

Compare Source

Added
  • Add missing type definitions for processEnv and DOTENV_KEY options. #​756

v16.3.0

Compare Source

Added
  • Optionally pass DOTENV_KEY to options rather than relying on process.env.DOTENV_KEY. Defaults to process.env.DOTENV_KEY #​754

v16.2.0

Compare Source

Added
  • Optionally write to your own target object rather than process.env. Defaults to process.env. #​753
  • Add import type URL to types file #​751

v16.1.4

Compare Source

Added
  • Added .github/ to .npmignore #​747

v16.1.3

Compare Source

Removed
  • Removed browser keys for path, os, and crypto in package.json. These were set to false incorrectly as of 16.1. Instead, if using dotenv on the front-end make sure to include polyfills for path, os, and crypto. node-polyfill-webpack-plugin provides these.

v16.1.2

Compare Source

Changed
  • Exposed private function _configDotenv as configDotenv. #​744

v16.1.1

Compare Source

Added
  • Added type definition for decrypt function
Changed
  • Fixed {crypto: false} in packageJson.browser

v16.1.0

Compare Source

Added
  • Add populate convenience method #​733
  • Accept URL as path option #​720
  • Add dotenv to npm fund command
  • Spanish language README #​698
  • Add .env.vault support. 🎉 (#​730)

ℹ️ .env.vault extends the .env file format standard with a localized encrypted vault file. Package it securely with your production code deploys. It's cloud agnostic so that you can deploy your secrets anywhere – without risky third-party integrations. read more

Changed
  • Fixed "cannot resolve 'fs'" error on tools like Replit #​693

v16.0.3

Compare Source

Changed
  • Added library version to debug logs (#​682)

v16.0.2

Compare Source

Added
  • Export env-options.js and cli-options.js in package.json for use with downstream dotenv-expand module

v16.0.1

Compare Source

Changed
  • Minor README clarifications
  • Development ONLY: updated devDependencies as recommended for development only security risks (#​658)

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 renovate bot added the dependencies Pull requests that update a dependency file label May 16, 2022
@renovate
Copy link
Author

renovate bot commented May 16, 2022

⚠ 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-routes@1.4.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR!   peer react@"^17.0.2 || ^18.0.0-0" from next@12.1.0
npm ERR!   node_modules/next
npm ERR!     next@"12.1.0" from the root project
npm ERR!     peer next@">=7.0.0" 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!     1 more (next-routes)
npm ERR!   5 more (react-dom, react-icons, react-map-gl, styled-jsx, use-subscription)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR! node_modules/next-routes
npm ERR!   next-routes@"1.4.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR!   node_modules/next-routes
npm ERR!     next-routes@"1.4.2" 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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-02-20T03_54_09_015Z-debug-0.log

@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from d0bc95d to 274954c Compare September 25, 2022 23:02
@renovate renovate bot changed the title Update dependency dotenv to v16.0.1 Update dependency dotenv to v16.0.2 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 274954c to e41fd2f Compare November 20, 2022 20:28
@renovate renovate bot changed the title Update dependency dotenv to v16.0.2 Update dependency dotenv to v16.0.3 Nov 20, 2022
@renovate renovate bot changed the title Update dependency dotenv to v16.0.3 Update dependency dotenv to v16.1.0 May 30, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from e41fd2f to d9a743c Compare May 30, 2023 18:12
@renovate renovate bot changed the title Update dependency dotenv to v16.1.0 Update dependency dotenv to v16.1.1 May 31, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch 2 times, most recently from 7209578 to 5d57475 Compare May 31, 2023 17:22
@renovate renovate bot changed the title Update dependency dotenv to v16.1.1 Update dependency dotenv to v16.1.2 May 31, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 5d57475 to f1d5fbc Compare May 31, 2023 19:15
@renovate renovate bot changed the title Update dependency dotenv to v16.1.2 Update dependency dotenv to v16.1.3 May 31, 2023
@renovate renovate bot changed the title Update dependency dotenv to v16.1.3 Update dependency dotenv to v16.1.4 Jun 4, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from f1d5fbc to aeae9c5 Compare June 4, 2023 17:09
@renovate renovate bot changed the title Update dependency dotenv to v16.1.4 Update dependency dotenv to v16.2.0 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch 2 times, most recently from 4c99385 to ca5a657 Compare June 16, 2023 20:23
@renovate renovate bot changed the title Update dependency dotenv to v16.2.0 Update dependency dotenv to v16.3.0 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from ca5a657 to 69ebade Compare June 17, 2023 19:17
@renovate renovate bot changed the title Update dependency dotenv to v16.3.0 Update dependency dotenv to v16.3.1 Jun 17, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 69ebade to 85129a4 Compare January 19, 2024 17:32
@renovate renovate bot changed the title Update dependency dotenv to v16.3.1 Update dependency dotenv to v16.3.2 Jan 19, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 85129a4 to 973c98f Compare January 23, 2024 21:20
@renovate renovate bot changed the title Update dependency dotenv to v16.3.2 Update dependency dotenv to v16.4.0 Jan 23, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 973c98f to aa3f58b Compare January 24, 2024 21:14
@renovate renovate bot changed the title Update dependency dotenv to v16.4.0 Update dependency dotenv to v16.4.1 Jan 24, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from aa3f58b to 3eb80aa Compare February 10, 2024 21:03
@renovate renovate bot changed the title Update dependency dotenv to v16.4.1 Update dependency dotenv to v16.4.2 Feb 10, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 3eb80aa to 1381386 Compare February 12, 2024 21:55
@renovate renovate bot changed the title Update dependency dotenv to v16.4.2 Update dependency dotenv to v16.4.3 Feb 12, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 1381386 to 1002805 Compare February 13, 2024 18:30
@renovate renovate bot changed the title Update dependency dotenv to v16.4.3 Update dependency dotenv to v16.4.4 Feb 13, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 1002805 to d5145ad Compare February 20, 2024 03:54
@renovate renovate bot changed the title Update dependency dotenv to v16.4.4 Update dependency dotenv to v16.4.5 Feb 20, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from d5145ad to e3028c5 Compare December 3, 2024 02:04
@renovate renovate bot changed the title Update dependency dotenv to v16.4.5 Update dependency dotenv to v16.4.6 Dec 3, 2024
Copy link
Author

renovate bot commented Dec 3, 2024

⚠️ 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-routes@1.4.2
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   react@"17.0.2" from the root project
npm ERR!   peer react@"^17.0.2 || ^18.0.0-0" from next@12.1.0
npm ERR!   node_modules/next
npm ERR!     next@"12.1.0" from the root project
npm ERR!     peer next@">=7.0.0" 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!     1 more (next-routes)
npm ERR!   5 more (react-dom, react-icons, react-map-gl, styled-jsx, use-subscription)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR! node_modules/next-routes
npm ERR!   next-routes@"1.4.2" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: react@16.14.0
npm ERR! node_modules/react
npm ERR!   peer react@"^15.4.2 || ^16" from next-routes@1.4.2
npm ERR!   node_modules/next-routes
npm ERR!     next-routes@"1.4.2" 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 /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-12-03T02_04_31_388Z-debug-0.log

@renovate renovate bot changed the title Update dependency dotenv to v16.4.6 Update dependency dotenv to v16.4.7 Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants