Update dotenv-rails 3.1.4 → 3.1.7 (patch) #1406
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![depfu[bot]](https://avatars.githubusercontent.com/in/715?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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-rails (3.1.4 → 3.1.7) · Repo · Changelog
Release Notes
3.1.7
3.1.6
3.1.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
Merge pull request #523 from bkeepers/preserve-linebreaksPrepare for 3.1.7 releasePreserve repeated linebreaks when normalizing line endingsMerge pull request #521 from bkeepers/endoflife-matrixRun tests once/day to test against latest versionsTry continuing when bundle install failsGetting Ruby and Rails versions from endoflife.datePrepare for v3.1.6 releaseMerge pull request #519 from bkeepers/fix-518Restore previous parser behavior of returning existing variablesPrepare for 3.1.5 releaseMerge pull request #517 from bkeepers/refactorRefactor parser to avoid repeated scan/gsubSmall refactoring of parser to make it easier to grokMerge pull request #515 from andrewts129/andrewts129/faster-parsingAdd benchmarks for parsingMerge pull request #516 from JohnYangSam/patch-1Update README.mdOptimize parser by removing repeated hash mergesRelease Notes
3.1.7
3.1.6
3.1.5
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 19 commits:
Merge pull request #523 from bkeepers/preserve-linebreaksPrepare for 3.1.7 releasePreserve repeated linebreaks when normalizing line endingsMerge pull request #521 from bkeepers/endoflife-matrixRun tests once/day to test against latest versionsTry continuing when bundle install failsGetting Ruby and Rails versions from endoflife.datePrepare for v3.1.6 releaseMerge pull request #519 from bkeepers/fix-518Restore previous parser behavior of returning existing variablesPrepare for 3.1.5 releaseMerge pull request #517 from bkeepers/refactorRefactor parser to avoid repeated scan/gsubSmall refactoring of parser to make it easier to grokMerge pull request #515 from andrewts129/andrewts129/faster-parsingAdd benchmarks for parsingMerge pull request #516 from JohnYangSam/patch-1Update README.mdOptimize parser by removing repeated hash mergesRelease Notes
1.17.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 3 commits:
version bump to v1.17.2fix(jruby): XML::DocumentFragment.dup to another document (v1.17.x) (#3373)fix(jruby): XML::DocumentFragment.dup to another documentRelease Notes
1.6.2
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 2 commits:
version bump to v1.6.2fix: PermitScrubber accepts frozen tagsDepfu 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