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

chore(deps): update dependency dotenv to v16.4.7 #824

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 14, 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 - "after 4pm on friday,before 9am on monday,every weekend" in timezone Europe/Paris, 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 force-pushed the renovate/dotenv-16.x branch from 054a603 to 830c042 Compare July 1, 2022 16:55
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 830c042 to b53a9bf Compare September 25, 2022 21:32
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from b53a9bf to 3fa1414 Compare November 20, 2022 09:16
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.0.1 chore(deps): update dependency dotenv to v16.0.3 Nov 20, 2022
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.0.3 chore(deps): update dependency dotenv to v16.1.3 Jun 2, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 3fa1414 to c2eb336 Compare June 2, 2023 15:57
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.1.3 chore(deps): update dependency dotenv to v16.1.4 Jun 4, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from c2eb336 to 51a7264 Compare June 4, 2023 18:22
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.1.4 chore(deps): update dependency dotenv to v16.2.0 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 51a7264 to 7c48977 Compare June 16, 2023 14:54
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.2.0 chore(deps): update dependency dotenv to v16.3.0 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 7c48977 to a9ea73f Compare June 16, 2023 18:49
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.3.0 chore(deps): update dependency dotenv to v16.3.1 Jun 17, 2023
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from a9ea73f to 57cf1de Compare June 17, 2023 18:21
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 57cf1de to 4ad8f06 Compare October 13, 2023 14:21
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 4ad8f06 to 81cbb32 Compare January 19, 2024 17:17
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.3.1 chore(deps): update dependency dotenv to v16.3.2 Jan 19, 2024
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.3.2 chore(deps): update dependency dotenv to v16.4.1 Jan 26, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 81cbb32 to 51135a1 Compare January 26, 2024 18:03
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.4.1 chore(deps): update dependency dotenv to v16.4.2 Feb 10, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch 2 times, most recently from 341fb9d to 18b2dce Compare February 16, 2024 16:04
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.4.2 chore(deps): update dependency dotenv to v16.4.4 Feb 16, 2024
@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 18b2dce to 73c3d50 Compare February 23, 2024 16:00
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.4.4 chore(deps): update dependency dotenv to v16.4.5 Feb 23, 2024
Copy link
Contributor Author

renovate bot commented Feb 23, 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: yarn.lock
Internal Error: Error when performing the request to https://registry.npmjs.org/yarn; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:22882:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:22896:20)
    at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:22948:20)
    at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:22971:14)
    at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:23349:25)
    at async executePackageManagerRequest (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:24207:28)
    at async BinaryCommand.validateAndExecute (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:21173:22)
    at async _Cli.run (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:22148:18)
    at async Object.runMain (/opt/containerbase/tools/corepack/0.25.2/node_modules/corepack/dist/lib/corepack.cjs:24279:12)

@renovate renovate bot force-pushed the renovate/dotenv-16.x branch from 73c3d50 to dce8de4 Compare December 6, 2024 17:24
@renovate renovate bot changed the title chore(deps): update dependency dotenv to v16.4.5 chore(deps): update dependency dotenv to v16.4.7 Dec 6, 2024
Copy link
Contributor Author

renovate bot commented Dec 6, 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: yarn.lock
/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:21609
    throw new Error(
          ^

Error: Error when performing the request to https://registry.npmjs.org/yarn/latest; for troubleshooting help, see https://github.com/nodejs/corepack#troubleshooting
    at fetch (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:21609:11)
    at async fetchAsJson (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
    ... 4 lines matching cause stack trace ...
    at async Object.runMain (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:23102:5) {
  [cause]: TypeError: globalThis.fetch is not a function
      at fetch (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:21603:33)
      at async fetchAsJson (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:21623:20)
      at async fetchLatestStableVersion (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:21550:20)
      at async fetchLatestStableVersion2 (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:21672:14)
      at async Engine.getDefaultVersion (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:22298:23)
      at async Engine.executePackageManagerRequest (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:22396:47)
      at async Object.runMain (/opt/containerbase/tools/corepack/0.30.0/16.14.2/node_modules/corepack/dist/lib/corepack.cjs:23102:5)
}

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