Version Bump
vbjay opened this issue · 8 comments
Released version is 2.51.05 and 3.0 is coming.
The 2.51.05 is seen by default by setting latest branch on the on the commit to be seen and is one of many steps involved in a release that supposedly is easy to miss.
@RussKie Can you force push so master/latest, release/2.51 is on one of the branches before updating in main repo?
I'm confused and no idea what you're talking about, sorry. 😴
You should have all necessary permissions to do it yourself 😉
I messed up and master etc are on separate commits. do not have permission to push to protected branches at all so I cannot fix.
@RussKie
The intention was to give you less work, not more...
🤣 no worries
so you want master and latest to point to the same commit?
As well as release/2.51
Right, so all of them to point to the same commit.
I'll do it tonight
Done
