Wrong commit SHA in staging

[dbelokon]

What happened: Today, I head over the staging deployment, and I clicked on the version tag (as of right now, it is version 2.5.0). After clicking it redirected to a commit that does not exist (the SHA in the link does not reference an existing commit).

What should have happened: A page that shows an existing commit.

How to reproduce it (as precise as possible): Go to staging and click on the version tag.

Anything else we need to know?: This might be related to #2650 or not. I am not really sure.

Environment:

• OS: Windows 10
• Browser: FireFox v. 95.0.2

[manekenpix]

It seems that this issue only happens during releases.
From what I can see, the current commit displayed in staging is fd66d60, and checking the logs, I see that 2 events took place during the 2.5.0 release:

and one of them had this payload:

"ref": "refs/tags/2.5.0",
"before": "0000000000000000000000000000000000000000",
"after": "fd66d60f67d6491e4fd008a1deeee620e2711ea1",

with the same commit sha that's currently displayed in staging. I wonder if somehow we processed this request and ended up with this wrong sha in staging.