It doesn't matter why the package was retired. We want to keep the commit history identical for both branches whenever possible.

Note: The formatting changes make it hard to review the content changes. It would be much easier to review if those changes were split into two commits.

Retirements are generally only allowed for rawhide, Branched (currently f43), and epel*, so I'm not sure this is entirely accurate.

Retirements are generally only allowed for rawhide, Branched (currently f43), and epel*, so I'm not sure this is entirely accurate.

But unretirements can happen for stable branches.

I think the commit message include a link to https://pagure.io/releng/issue/12905 so it's clear why this was changed.

Retirements are generally only allowed for rawhide, Branched (currently f43), and epel*, so I'm not sure this is entirely accurate.

But unretirements can happen for stable branches.

Ah, right, "this" is referring to unretirement tickets.

There is a note here about closing the ticket with a link to the distgit repository. Should the closing message also include a reminder to submit a new build for each unretired branch?

Looks good to me, can you please address the above comments seems reasonable!

I addressed the changes. Thank you everyone for your inputs.