Theia version upgrade must use version number?

#1

Hi, all contributors

I am trying to use the new release 1.38.0 of Theia.

Currently I am managing my sources as follows to manage my packages.

{
  "private": true,
  "name": "electron-app",
  "main": "src-gen/frontend/electron-main.js",
  "version": "0.0.0",
  "dependencies": {
    "@theia/core": "latest",
    "@theia/electron": "latest",
    "@theia/markers": "latest",
    "@theia/messages": "latest",
    "@theia/preferences": "latest",
    "@theia/process": "latest",
    "@theia/workspace": "latest"
  },
  "devDependencies": {
    "@theia/cli": "latest",
    "electron": "^23.2.4"
  },
  "scripts": {
    "prepare": "theia build --mode development",
    "start": "theia start",
    "watch": "theia build --watch --mode development"
  },
  "theia": {
    "target": "electron"
  }
}

To apply the new updated Theia, delete the node_modules folder and the yarn.lock file, and then type
When I type ‘yarn’ in the command again to install Theia, the version that is installed is 1.37.2.

Do I need to enter an explicit version number instead of ‘latest’ to keep Theia’s version up to date?

#2

@VICTUS Seems like during our latest patch release, the latest tag got set incorrectly. We always recommend devs to pin their @theia/* dependencies to a single version to prevent mismatching dependencies, so I’d recommend you to do the same.