@eileencodes this might help a lot with the merge conflict question you had.

That's an interesting solution to the problem. There's a couple things we need to do though before we can merge this.

1. There needs to be a CHANGELOG entry for active record.
2. How disruptive will this be to applications? Is there any value in making this configurable or is that overkill?

1. There needs to be a CHANGELOG entry for active record.

Done

2. How disruptive will this be to applications? Is there any value in making this configurable or is that overkill?

We're running this internally as a monkey patch and aside from the one-time cost of the first structure dump changing all the existing entries, it's been pretty invisible.

Interesting indeed! While that definitely means the same thing to the computer, it feels like a (small) experience downgrade for the human (who I think will still need to edit this section to resolve conflicts, at least sometimes, even with the spurious semicolon changes removed).

What if we reversed the sort order instead? 🤔

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Thank you for your contributions.

What if we reversed the sort order instead? 🤔

Tested this monkey patch:

# https://github.com/rails/rails/pull/43414
module ActiveRecord
  module ConnectionAdapters
    class PostgreSQLAdapter
      def insert_versions_sql(versions)
        if versions.is_a?(Array)
          super(versions.reverse)
        else
          super
        end
      end
    end
  end
end

It seems to work pretty well.

Edit: after running that monkey patch for about a month, I've made a PR to upstream: #44363