Upgrade all of rails to version 6.1.1 - #34
Closed
depfu[bot] wants to merge 1 commit into
Closed
Conversation
Author
|
Closed in favor of #38. |
This file contains hidden or 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
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.
Welcome to Depfu 👋
This is one of the first three pull requests with dependency updates we've sent your way. We tried to start with a few easy patch-level updates. Hopefully your tests will pass and you can merge this pull request without too much risk. This should give you an idea how Depfu works in general.
After you merge your first pull request, we'll send you a few more. We'll never open more than seven PRs at the same time so you're not getting overwhelmed with updates.
Let us know if you have any questions. Thanks so much for giving Depfu a try!
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?
✳️ activerecord (>= 3.2.3, < 5.2.0 → >= 3.2.3, <= 6.1.1) · Repo · Changelog
Release Notes
6.1.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 23 commits:
Preparing for 6.1.1 releaseFix has_many_inversing with touch: true on a belongs_to association with inverseMerge pull request #41037 from mkasztelnik/remove-update_table_definition-from-migration-logMerge pull request #41029 from kamipo/fix_has_many_through_with_through_scope_with_joinsMerge pull request #41025 from uxxman/destroy_async_sti_fixMerge pull request #41023 from kuldeepaggarwal/patch-1Merge pull request #41012 from kamipo/fix_complicated_through_associationMerge pull request #40992 from kamipo/fix_enum_with_mangling_collisionMerge pull request #40974 from kamipo/dont_mangle_enum_names_for_unicode_lettersMake sure db:prepare works even the schema file doesn't existMerge pull request #40306 from cindysx89/ensure_db_dirFix indentation [ci skip]Make sure the :if options of callbacks is not mutatedMerge pull request #40951 from kamipo/fix_where_with_polymorphic_associationMerge pull request #40877 from PhilCoggins/destroy_async_documentation_updateMerge pull request #40880 from kamipo/fix_money_type_castMerge pull request #40879 from glaszig/fix-belongs-to-polymorphicMerge pull request #40849 from kamipo/fix_composed_of_with_symbol_mappingDocs: fix code formatting [ci skip]Merge pull request #40835 from kamipo/fix_where_with_aliased_associationMerge pull request #40803 from fatkodima/revertible-expression-indexesMerge pull request #40815 from kamipo/fix_where_with_custom_primary_keyMerge pull request #40792 from ghiculescu/fixture-strict-loadingDepfu 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