release v3.28.6 was overriden pointing to different commit only few hours after release

[dbelyaev]

I am not following development and release process closely here, but I have a question:

Why was the latest v3.28.6 released as commit 4e83f6b818d7c9f52143570963b2c7f7f055decb overridden as v3.28.6 and different commit 17a820bf2e43b47be2c72b39cc905417bc1ab6d0 only few hours later instead of deploying a new v3.28.7?

Or am I missing something?

[aeisenberg]

There was a problem with our automation. After pushing the tag, a release and a PR on a branch merging back to main was supposed to have been created, but our workflow was missing a permission. I fixed the permission problem and re-pushed the tag. You can see the diff here.

4e83f6b...17a820b

[dbelyaev]

@aeisenberg thank you for the explanation!
It just triggered 2 upgrade notification in my pipeline within a such short timeframe, which looked suspicious, so needed a verification.

[aeisenberg]

Apologies for the confusion. In retrospect, starting a new release would have been better.