Open greenkeeper[bot] opened 7 years ago
Update to this version instead 🚀
<a name"2.1.0">
Update to this version instead 🚀
<a name"3.0.0">
defaultenv
wouldn't read .env
unless it was passed by name or the--dotenv
option was given. Now the default behavior is to read the .env
file in the project--no-dotenv
option.(d203d2aa)
Update to this version instead 🚀
<a name"3.0.2">
Update to this version instead 🚀
<a name"3.0.3">
Version 2.0.0 of defaultenv just got published.
The version 2.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of defaultenv. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v2.0.0<a name"2.0.0">
2.0.0 (2017-07-06)
Bug Fixes
Features
Breaking Changes
(fea3221d)
Commits
The new version differs by 4 commits.
fea3221
feat(dotenv): support --dotenv option
32db4f0
Merge branch 'master' of https://github.com/jcoreio/defaultenv
6f7b4a9
fix(options): modify process.env immediately with -f and -p options
97fb2a4
feat(options): add -f and -p options
See the full diff
Not sure how things should work exactly?
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: