Bump updated_at on Ci::RunnerManager#heartbeat (!209822) · Merge requests · GitLab.org / GitLab

What does this MR do and why?

Bump updated_at on Ci::RunnerManager#heartbeat

As per the discussion at https://gitlab.com/gitlab-data/analytics/-/issues/25129#note_2835760103 we found by using update_columns() we don't bump the updated_at column of the ci_runner_machines table. Which is really confusing and makes external mechanisms, like our data analyzis platform feeding mechanism, not catching the updates that were happening.

References

Screenshots or screen recordings

Before	After

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.