Sharetribe version 7.3.0 is now available!

Announcements
1

Added

  • Per hour availability 3166
  • Support for NZ bank account with Stripe 3165
  • “View conversations” section in admin panel 3173
  • Account tokens for Stripe bank account connections 3234

Changed

  • Made user confirmation form more secure 3170

Removed

  • Confirmation days x after end time of the transaction 3205

Fixed

  • Improvements to PayPal workflow (IPNs) 3176
  • Some bugs related to sending emails from admin#3183

Upgrade from 7.2.0 to 7.3.0

Nothing special. See the [#general-update-instructions].

2

For the update, do we run this command?

git checkout latest

3

Dear Sharetribe Team,
could right some more details about the right way to sync with the git repository?

The general update procedure does not work for me and I guess the git repository command needs to be different.

https://github.com/sharetribe/sharetribe/blob/master/UPGRADE.md

At the moment I figured out with this ones:

git remote add upstream git://github.com/sharetribe/sharetribe.git
git fetch upstream
git checkout Gemfile.lock
git reset --hard HEAD
git merge upstream/master master

But if I try then inside the sharetribe folder the

git checkout latest

It still says 7.2.0 and not 7.3.0 and the other commands show no option.

Help is highly appreciated!! :wink:

Best regards,
Stefan

4

Hi Stefan,

Can you explain a bit why the general procedure doesn’t work for you? Do you see an error, or what is the main problem you’re experiencing?

5

Hi Mikko,
I have a v7.2.0 running on an ubuntu 16x on digitalocean; I don’t use heroku. A fresh installation with the latest version works fine, but the upgrade does not work so far;)

So first, I guess I have to stop all services. I do that before the upgrade.
If I then just go into the ST folder and run:

bundle install
npm install
RAILS_ENV=production rake db:migrate

ST is not updated; bundle install seems to do something, but npm install stays stucked… If I check then with

git checkout latest
it still says 7.2.0

(BTW: for npm install I always have to go into the sharetribe/client folder and then run the npm install command)

Thus I guess, before doing the upgrade I have to sync the files on the DO-droplet with the git-repository on github. If I do that with, e.g.

git remote add upstream git://github.com/sharetribe/sharetribe.git
git fetch upstream

Then I can see which files are updated; but if I re-do then the upgrade procedure; nothing happens again. and git checkout latest still says 7.2.0
So question 1: Do I have to do the git sync at all or is it already in the bundle install script?

git remote add upstream git://github.com/sharetribe/sharetribe.git
git fetch upstream

Second question: My feeling is, that there might be a problem with the npm install…?

What is your opinion?

Thank you in advance,
Cheers,
Stefan

1 Like
6

Ahaa, got it. The reason for this, I believe, is that git pull and git fetch don’t update tags by default. So instead of git fetch upstream, try git fetch upstream --tags. This should update the position of the latest tag, and after that, git checkout latest should checkout the right version.

I updated the instructions accordingly, thanks for pointing this out!

Hard so say about the npm install issue. Maybe you could try to update the code to 7.3.0 according to the new instructions and try again?

7

Hi Mikko,
thx that worked perfectly. It’s all about the details;)

Best regards,
Stefan

1 Like