Upgrade dotenv to version 16.0.1 #117
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ dotenv (^8.2.0 → ^16.0.1) · Repo · Changelog
Release Notes
16.0.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 21 commits:
Version bump - patch 16.0.1
Update CHANGELOG
Merge pull request #658 from motdotla/dev-dep-updates
Update various dev dependencies
Update dev dependency @types/node
Update links in README
Change link
Update README
Update README
Update README
Add note above README
Use dotenv-vault
Merge pull request #646 from motdotla/test-clarifications
Clarify that inline comments do not require a space after the number sign
Merge pull request #643 from odcey/fix-readme-returnline-typo
fix: update typo on readme concerning return line documentation
Merge pull request #628 from kunalpanchal/patch-1
Update the broken reference link to require module
Merge pull request #621 from motdotla/braces-spec
Add spec confirming https://github.com/motdotla/dotenv-expand/issues/49 no longer an issue
Update CHANGELOG
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands