Add dismissed_at to dependency_management_remediations

What does this MR do and why?

Adds a nullable dismissed_at to dependency_management_remediations.

The model derives a dismissal time from updated_at, following the schema review decision to avoid a second timestamp and express the meaning with a model-layer alias. That does not hold: updated_at is also written when a proposal is re-recorded against a row that stays dismissed, so the reported dismissal time moves even though nobody dismissed anything.

The alias goes with it, in the same MR. Left in place it would shadow the reader Active Record generates for the new column, so the column would be unreadable through the model.

Nothing writes the column yet. The write path sets it when a row moves to dismissed and clears it when a reopen or a higher target version ends the dismissal.

No backfill: nothing writes to this table in production yet.

References

Related to #603968

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.

Edited by Albina Yusupova

Merge request reports

Loading
Loading