Commits page no longer follows file renames (possible regression from project_commits_refactor)

Caution: This issue analysis was AI assisted using Claude Fable 5.1

Summary

Since the commits page was rebuilt on GraphQL (project_commits_refactor, default_enabled: true), the file history view stops at the commit that renamed the file. Commits from before the rename are no longer shown. The old page and the REST API both still follow renames.

Steps to reproduce

Public reproduction on GitLab.com — Wireshark renamed packet-ssl.c → packet-tls.c in 50dbe4df (Sep 2018):

1. Open https://gitlab.com/wireshark/wireshark/-/commits/master/epan/dissectors/packet-tls.c
2. Page to the end of the history (or set "Show 100 items").
3. The last commit shown is 50dbe4df "Rename packet-ssl_to packet-tls_". Next is disabled.

What is the expected correct behavior?

File history should follow renames, as it did on the legacy commits page, as the REST API still does by default.

Workaround

We have a temporary solution for our self-managed 19.1 instances. However, we're not sure how long it will work.

Feature.disable(:project_commits_refactor, Project.find_by_full_path('group/project'))