I don't think that commit has been released yet, which would explain why you'd still have the error. You could have just cherry-picked that commit you linked, but what you did works as well. It might just end up conflicting with future upgrades.
Solved easy nodebb upgrade process
Admit that wp upgrade spoiled me. Is there an upgrade button in nodebb?
is there instructions to show how to upgrade from v1.0.0 to v1.0.x?
@charles just follow the NodeBB docs
@pichalite thanks! I tried that and tbh it's written as if many should understand the process.
docs really need to be more friendly to all audiences
should anyone have to guess between patch revisions or minor revisions?
then it talks about "if not upgrading between branches (ie v0.3.3 to v0.3.4)" use the git reset
is nodebb now at the patch, minor or between branches now?
so should I use git fetch git checkout and git merge or should I only use git fetch git reset section?
@charles it is what it is... not sure if the docs or the upgrade process can be simplified. if you are on 1.0.0 then it's a patch
Yes, I'll admit the write up is a little verbose, but that's how I am when I write text
The gist of it is...
git checkout v1.x.xif not already there
git pull && ./nodebb upgrade
So if I'm upgrading from v1.0.0 to v1.0.1 does that mean I should replace the x.x for the command you provided with
git checkout v1.0.1?
phit last edited by
@charles no, it stays
git checkout v1.x.x
that's the branch name for the latest 1.x.x, so right now 1.0.1
I thought it was clear, but didnt work for me i upgraded, it appeared to work, but still when i go into the dashboard it says 1.0.0
@ViolentCrumble I'll be testing it and will let you know what works so you can also try.
tried commands below and works for me. Now logged in and version showing v1.0.2
git checkout v1.x.x git pull ./nodebb upgrade
@charles Not sure what i am doing wrong, but this happens
charles last edited by charles
@ViolentCrumble I was confused with commands too.
git checkout v1.x.xexactly as shown. do not add any numbers. after that you can use the other commands shown in my previous reply.
./nodebb restartand then check the version again
@charles Whelp, now it's showing 1.0.0 and isn't showing any stats
@ViolentCrumble that is strange that you have
when I try
git checkout v1.x.xI get
Already on 'v1.x.x'
Your branch is up-to-date with 'origin/v1.x.x'.
@charles I think i might have broken something when i was attempting to backup my forums using git...
When i type git remote -v
i get my own personal git directory. i think i done and gone broken something