Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.
Sign up[ruby] Upgrade responders to version 3.0.0 #74
Conversation
This comment has been minimized.
This comment has been minimized.
codecov-io
commented
Jun 23, 2019
•
Codecov Report
@@ Coverage Diff @@
## master #74 +/- ##
=====================================
Coverage 100% 100%
=====================================
Files 5 5
Lines 34 34
=====================================
Hits 34 34Continue to review full report at Codecov.
|
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.
depfu bot commentedJun 23, 2019
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?
Release Notes
3.0.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 31 commits:
Prepare to 3.0.0Remove code to support Rails 4.2Configure rubocop and autocorrect everythingHappy new year :tada:Update CHANGELOG [ci skip]Make sure the template being rendered matches the media typeCheck the media type instead of content typeFix minitest warningsRemove support to Rails 4.2Test against released rackRun tests with 2.6 and the global gemfileCommit the Gemfile.lockMerge pull request #211 from deivid-rodriguez/allow_rails_61_prereleasesRemove the upper bound on rails dependenciesAllow Rails 6.1 prereleasesMerge pull request #208 from deivid-rodriguez/update_rails_6_branchMerge pull request #206 from deivid-rodriguez/remove_rubyforge_gemspec_attributeMerge branch 'master' into remove_rubyforge_gemspec_attributeMerge pull request #209 from deivid-rodriguez/drop_old_rubies_supportDrop support for old rubiesPoint Rails 6 Gemfile to 6-0-stable`rubyforge_project` attribute was removed from rubygemsMerge pull request #205 from abraham/patch-1Use example domain for emailMerge pull request #203 from Shopify/deduplicate-action-namesDeduplicate action namesMerge pull request #202 from matthewrudy/rails-6.0.0travis: exclude rails 4.2 and ruby 2.6travis: test against rails master (6.0.0.beta)travis: test rails 5.2 correctlytravis: enable ruby 2.6.0Depfu 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