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.0
Release Notes
motdotla/dotenv (dotenv)
v17.2.0
Compare Source
Added
DOTENV_CONFIG_QUIET=true
in your environment or.env
file to quiet the runtime log (#889)DOTENV_CONFIG_
environment variables take precedence over any code set options like({quiet: false})
v17.1.0
Compare Source
Added
v17.0.1
Compare Source
Changed
v17.0.0
Compare Source
Changed
quiet
to false - informational (file and keys count) runtime log message shows by default (#875)v16.6.1
Compare Source
Changed
quiet
to true – hiding the runtime log message (#874)config({ quiet: true })
to suppress.require('dotenv').config()
forrequire('@​dotenvx/dotenvx').config()
.v16.6.0
Compare Source
Added
[dotenv@16.6.0] injecting env (1) from .env
(#870){ quiet: true }
to suppressv16.5.0
Compare Source
Added
Changed
_log
method. Use_debug
#862v16.4.7
Compare Source
Changed
.tap
folder when publishing. (oops, sorry about that everyone. - @motdotla) #848v16.4.6
Compare Source
Changed
v16.4.5
Compare Source
Changed
path
option. return to historical behavior: do not attempt to auto find.env
ifpath
set. (regression was introduced in16.4.3
) #814v16.4.4
Compare Source
Changed
?.
with old school&&
(fixing node 12 failures) #812v16.4.3
Compare Source
Changed
path
option. return to historical behavior: do not attempt to auto find.env
ifpath
set. (regression was introduced in16.4.3
) #814v16.4.2
Compare Source
Changed
dotenvx.com
v16.4.1
Compare Source
path
option #797v16.4.0
Compare Source
error.code
to error messages around.env.vault
decryption handling #795.env.vault
file when filename(s) passed as an array #784v16.3.2
Compare Source
Added
Changed
populate
#792v16.3.1
Compare Source
Added
processEnv
andDOTENV_KEY
options. #756v16.3.0
Compare Source
Added
DOTENV_KEY
to options rather than relying onprocess.env.DOTENV_KEY
. Defaults toprocess.env.DOTENV_KEY
#754v16.2.0
Compare Source
Added
process.env
. Defaults toprocess.env
. #753v16.1.4
Compare Source
Added
.github/
to.npmignore
#747v16.1.3
Compare Source
Removed
browser
keys forpath
,os
, andcrypto
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 forpath
,os
, andcrypto
. node-polyfill-webpack-plugin provides these.v16.1.2
Compare Source
Changed
_configDotenv
asconfigDotenv
. #744v16.1.1
Compare Source
Added
decrypt
functionChanged
{crypto: false}
inpackageJson.browser
v16.1.0
Compare Source
Added
populate
convenience method #733npm fund
command.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 moreChanged
v16.0.3
Compare Source
Changed
v16.0.2
Compare Source
Added
env-options.js
andcli-options.js
in package.json for use with downstream dotenv-expand modulev16.0.1
Compare 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.