Nasty releases

[hannesa2]

Hi, I tried to start with #3188 (comment)
Doing so I looked around the current state, but I see you created releases on unknown SHA1, that's nasty !
Even you don't tag a release.

Even to modify a changelog manually is as modern as sending a FAX in 2023

I made already a pull request to automate this ci/release/pullrequest with automated changelogs. Related to your feedback, I gave up here. That's why I only see this mess. -sorry, I've to say this-

Please avoid this releases on unknown SHA1 and please tag every release.

[jesmrec]

All releases are not only tagged, also verified with the GitHub green tick:

Please use the tagged commit like oc-android-4.0 , oc-android-3.0.4 to checkout to the proper commit. Or, checkout to the stable branch to get the latest stable. It's so easy.

Will check why the GitHub warning or how to avoid it. Thanks for reporting.

[hannesa2]

Ahh, sorry my fault.
I assumed a git fetch --all does the job, but I need git fetch upstream --tags