Update dependency dotenv to v17 #8
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/dotenv-17.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
^16.0.0->^17.0.0Release Notes
motdotla/dotenv (dotenv)
v17.2.0Compare Source
Added
DOTENV_CONFIG_QUIET=truein your environment or.envfile to quiet the runtime log (#889)DOTENV_CONFIG_environment variables take precedence over any code set options like({quiet: false})v17.1.0Compare Source
Added
v17.0.1Compare Source
Changed
v17.0.0Compare Source
Changed
quietto false - informational (file and keys count) runtime log message shows by default (#875)v16.6.1Compare Source
Changed
quietto true – hiding the runtime log message (#874)config({ quiet: true })to suppress.require('dotenv').config()forrequire('@​dotenvx/dotenvx').config().v16.6.0Compare Source
Added
[dotenv@16.6.0] injecting env (1) from .env(#870){ quiet: true }to suppressv16.5.0Compare Source
Added
Changed
_logmethod. Use_debug#862v16.4.7Compare Source
Changed
.tapfolder when publishing. (oops, sorry about that everyone. - @motdotla) #848v16.4.6Compare Source
Changed
v16.4.5Compare Source
Changed
pathoption. return to historical behavior: do not attempt to auto find.envifpathset. (regression was introduced in16.4.3) #814v16.4.4Compare Source
Changed
?.with old school&&(fixing node 12 failures) #812v16.4.3Compare Source
Changed
pathoption. return to historical behavior: do not attempt to auto find.envifpathset. (regression was introduced in16.4.3) #814v16.4.2Compare Source
Changed
dotenvx.comv16.4.1Compare Source
pathoption #797v16.4.0Compare Source
error.codeto error messages around.env.vaultdecryption handling #795.env.vaultfile when filename(s) passed as an array #784v16.3.2Compare Source
Added
Changed
populate#792v16.3.1Compare Source
Added
processEnvandDOTENV_KEYoptions. #756v16.3.0Compare Source
Added
DOTENV_KEYto options rather than relying onprocess.env.DOTENV_KEY. Defaults toprocess.env.DOTENV_KEY#754v16.2.0Compare Source
Added
process.env. Defaults toprocess.env. #753v16.1.4Compare Source
Added
.github/to.npmignore#747v16.1.3Compare Source
Removed
browserkeys forpath,os, andcryptoin 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 forpath,os, andcrypto. node-polyfill-webpack-plugin provides these.v16.1.2Compare Source
Changed
_configDotenvasconfigDotenv. #744v16.1.1Compare Source
Added
decryptfunctionChanged
{crypto: false}inpackageJson.browserv16.1.0Compare Source
Added
populateconvenience method #733npm fundcommand.env.vaultsupport. 🎉 (#730)ℹ️
.env.vaultextends the.envfile 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 moreChanged
v16.0.3Compare Source
Changed
v16.0.2Compare Source
Added
env-options.jsandcli-options.jsin package.json for use with downstream dotenv-expand modulev16.0.1Compare Source
Changed
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR has been generated by Renovate Bot.
⚠️ 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:
The artifact failure details are included below:
File name: package-lock.json
Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠️ Warning: custom changes will be lost.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.