<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary <!-- Summarize the bug encountered concisely. --> After Upgrading our Community Edition gitlab instance our MR no longer upgrade. This is true for existing MR as well as new ones. For existing MR no new branch pipelines are dispatched or displayed in the UI, new MR are stuck on "Your merge request is almost ready!" ### Relevant logs and/or screenshots In Sidekiq, the UpdateMergeRequestsWorker job's and NewMergeRequestWorker job's all are "dead". Each with the same error message: ``` PG::NotNullViolation: ERROR: null value in column "committed_date" of relation "merge_request_diff_commits" violates not-null constraint DETAIL: Failing row contains (null, null, 8828, 0, null, null, {}, null, null, 1713, null). ``` ### Similar Issues There was a similar issue in 18.1, the [proposed solution there](https://support.gitlab.com/hc/en-us/articles/25896786403356-Break-Fix-Merge-requests-stuck-with-Your-merge-request-is-almost-ready-after-upgrading-to-GitLab-18-1) does not help, so I assume this is of a different nature.