Closed gabiborlea closed 7 months ago
I created the release from the PR branch, maybe that's why, not on purpose, just my first releases here :)
The README of this project has a section on how to release (within the development instructions)
Eventually followed them, thank you!
Sorry that its a bit of a manual and not so intuitive way to release at the moment, I never got around to wrap parts of it into some github action so that it would be easier and more intuitive...
No worries at all, thanks for all the automation work you've already done!
v2023.11.2 is tagged at f8ee5c7b94b87a562c00f67b671720af06e4c9da but the master branch is at commit 22adc4b5890ff966e5136c09fb45cfca2d5817a5 (2 different commit hashes, but with the same content, same parent and the same commit message). Is that on purpose or by accident?