When doing a fresh install, yarn takes the latest versions of the packages according to semver.
Then it creates a yarn.lock
file, and won't upgrade the packages anymore.
Yarn upgrade only upgrades the modules installed locally. It has no effect for anybody
else as it does not modify package.json
.
Option 1
- Publish gaia-engine
- Then log on remotely, do
cd gaia-site && yarn upgrade @gaia-project/engine
Option 2
- Publish gaia-engine
- On the github repo of
gaia-site
, editpackage.json
with the most recent version of gaia-engine - log on remotely, do
cd gaia-site && git pull && yarn install
Option 1
- Publish gaia-viewer
- Then log on remotely, do
cd gaia-site/front && yarn upgrade @gaia-project/viewer && yarn build
Option 2
- Publish gaia-viewer
- On the github repo of
gaia-site
, editfront/package.json
with the most recent version of gaia-viewer - log on remotely, do
cd gaia-site && git pull && cd front && yarn install && yarn build
For a full upgrade based on the code source of the website, do:
- log on remotely
- do
cd gaia-site && git pull && yarn install
- do
cd front && yarn install && yarn build
It should update everything, backend & front-end.