Closed depfu[bot] closed 3 years ago
This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.
🔍 Inspect: https://vercel.com/linbudu599/nx-plugins/6PMfRfTHrYgH9DZfCiBAMx8bck9S
âś… Preview: https://nx-plugins-git-depfu-updatenpmdotenv-1000-linbudu599.vercel.app
Closing because this update is no longer necessary.
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 (9.0.0 → 10.0.0) · Repo · Changelog
Release Notes
10.0.0 (from changelog)
9.0.2 (from changelog)
9.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 22 commits:
Merge pull request #536 from motdotla/changelog
Bump 10.0.0
Merge pull request #531 from ericmorand/issue_530
Merge pull request #528 from brelian/pylon/support-homedir
Merge pull request #534 from paulrobertlloyd/patch-1
Update CHANGELOG
Update CHANGELOG
allow for import "dotenv/config.js"
Merge pull request #533 from motdotla/remove-funding
Update README
Remove funding
Resolve issue #530
Update README
Bump 9.0.2
Merge pull request #523 from motdotla/windows-debug
Update CHANGELOG
Bump 0.9.1
Update README
Update README
fix linting error
chore: revert error changes
feat: support to parse home directory
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Travis-CI](https://travis-ci.com) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.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
Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.