did a nodebb upgrade, ACP says I'm not up-to-date

[julian]

@Giorgio-Chiodi Looks like that commit doesn't exist in our repository, so it's probably been modified by you? So you're possibly out of date with our repo...

[Giorgio Chiodi]

@julian mhh no haven't edited that part.

ah I just noticed everything is pointing to github.com/designcreateplay/NodeBB - last edit 22 May (!) in gitx

[Giorgio Chiodi]

@julian is it possible to switch git user folder to upgrade?

[julian]

@Giorgio-Chiodi Not sure if gitx is saving and committing changes you're making. That's why the git commit hash doesn't match any of ours.

See if you can sync up with the latest code from NodeBB

[Giorgio Chiodi]

@julian Should I just download and replace the code, because if I update it via git it goes still to github.com/designcreateplay/NodeBB

[julian]

That link should still work -- it redirects to our new repository.

Please type git status

[Giorgio Chiodi]

@julian

       # On branch v0.4.x
       # Your branch is ahead of 'origin/v0.4.x' by 2 commits.
       #   (use "git push" to publish your local commits)
       # 
       nothing to commit, working directory clean

[julian]

Right, v0.4.x (v0.4.3) is our stable branch. No new updates will be pushed to it, and the next release will be v0.5.0, at which point a new branch (v0.5.x) will be created.

[Giorgio Chiodi]

@julian wait are tags on the stable one?

[julian]

@Giorgio-Chiodi Unfortunately not -- it was introduced after v0.4.3 was released.

[Giorgio Chiodi]

@julian ah ok

...

when will it be released?

[Giorgio Chiodi]

@julian No wait julian - something's wrong. Look here the tags work!

http://146.185.184.104:4567/category/4/blogs