Merge a branch into main

I need the feature branch feature/auth-token merged into main and deployed by Friday. Check the branch for any failing tests, confirm the changelog entry and migration script are present, then merge into main with a fast-forward if possible. After merge, run the CI pipeline and notify Priya in QA and Marco in ops with the commit hash and any post-merge steps.

Before I merge feature/auth-token into main, make it easy for reviewers to sign off: surface failing tests or flaky tests up top, show the exact migrations and changelog additions, summarize any database changes in one sentence, and flag commits that touch shared libraries so Marco in operations can decide about deployment timing.

I just ran the test suite on feature/auth-token and one integration test failed; Priya in QA needs a stable build by Friday and Marco in ops will only allow the merge if there are no DB migrations missing. I am worried the failure masks a migration issue and I can’t tell if the test is flaky or caused by my changes. What is the likely cause and what’s the safest next step to unblock the merge?

Over the last three sprints we’ve had two rollbacks after merging because migrations or changelog entries were missing and ops blocked deployment. I want to stop that pattern. Which pre-merge checks and small team habits (who signs off, where to add a checklist) will most quickly reduce merge rollbacks and save time for Priya in QA and Marco in ops?