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

[Giorgio Chiodi]

I have this on my live server

And this on my test server

whhhhyyyyyy

@julian

[julian]

Mm... green means you're fine, red means you're out of date, blue means we couldn't check in some way.

Look for error in web console

[Giorgio Chiodi]

@julian says it couldn't find this (404)

https://api.github.com/repos/designcreateplay/NodeBB/tags

[julian]

Live server seems out of date -- we fixed it to point to the proper github url already, afaik...

[Giorgio Chiodi]

@julian mh maybe i didn't update properly?

git pull
./nodebb upgrade

[julian]

git rev-parse HEAD please, and what does line 23 of public/src/forum/admin/index.js say? It should read:

$.get('https://api.github.com/repos/NodeBB/NodeBB/tags', function(releases) {

[Giorgio Chiodi]

@julian

this is my git rev-parse HEAD (btw - what does it do?? massage??)

b2dd2f7237d75ff35a53f5baee878713d44deefa

ahhh my admin/index.js still says "designcreateplay"

	$.get('https://api.github.com/repos/designcreateplay/NodeBB/tags', function(releases) {

[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