Update dotenv 3.1.2 → 3.1.4 (patch) #235
Merged
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 update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ dotenv (3.1.2 → 3.1.4) · Repo · Changelog
Release Notes
3.1.4
3.1.3 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
Prepare for 3.1.4 release
Merge pull request #512 from alpaca-tc/fix-spring
Make spring specs a little more explicit
follow-up https://github.com/bkeepers/dotenv/pull/511/
Bump to 3.1.3
Prepare for v3.1.3
Merge pull request #511 from runephilosof-abtion/patch-1
Fix tests for spring changes
Only use Spring if already loaded
Merge pull request #509 from olleolleolle/run-standard
cleanup: Run standard:fix
Merge pull request #508 from olleolleolle/patch-1
README.md: typo "exiting"
Use releases for changelog URI
Merge pull request #506 from mark-young-atg/provide_changelog_link_on_rubygems
Provide a 'Changelog' link on rubygems.org/gems/dotenv
Fix link to PR in Changelog.md
Merge pull request #505 from mikegee/patch-1
Spell out 'FILENAME'
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