Skip to content

Allow destruction of Tagless Releases

Hunter Stewart requested to merge hustewart-allow-destroy-tagless-releases into master

Why

See Only latest Release is displayed on Releases page (#404562 - closed)

We have Releases that do not have tags. This data is invalid and causes problems loading the Releases page.

We have data validations in the application to protect against empty strings/nil and in the database to protect against null.

This may be old data that pre-dates the validations, or there may be a bug somewhere allowing this kind of data in.

What

We have a couple of options. The main ones I could think of:

  • A) some sort of data migration do either destroy the Tagless Releases
  • B) update the Destroy Release Service to allow destruction of Tagless releases.

I think the B is going to be necessary anyway to destroy the releases in a way that allows all the normal callbacks and side-effects to happen. We wouldn't want to just destroy the records, we'd want to follow all the steps that happen in the destroy service.

Once we do B, it would be a lot easier to solve problems for users on a one-off basis, and if we feel the need, we could write a data migration that finds tagless releases and destroys them.

Edited by Hunter Stewart

Merge request reports