Upgrade from 1.0 to 1.1 did not update workspace version number
Hi you all
I updated from 1.0 to 1.1.1. It seems to work but I have this warning :
[Nest] 56 - 07/21/2025, 5:08:54 PM LOG [UpgradeCommand] Initialized upgrade context with:
currentVersion (migrating to): 1.1.1
fromWorkspaceVersion: 1.0.0
5 commands
[Nest] 56 - 07/21/2025, 5:08:54 PM LOG [UpgradeCommand] Upgrading workspace 5bc2d041-8036-41ed-ba7a-a5514e1216d6 from=1.0.0 to=1.1.1 1/1
[Nest] 56 - 07/21/2025, 5:08:54 PM LOG [UpgradeCommand] Upgrade for workspace 5bc2d041-8036-41ed-ba7a-a5514e1216d6 ignored as is already at a higher version.
[Nest] 56 - 07/21/2025, 5:08:54 PM LOG [UpgradeCommand] Command completed!
[Nest] 56 - 07/21/2025, 5:08:54 PM LOG [PgPoolSharedService] pg Pool for key "localhost|5432|postgres||no-ssl" has been closed. Remaining pools: 0
Successfully migrated DB!
Registering background sync jobs...
Could you tell me how to be sure that everything is OK and that it will not break the next updates ?9 Replies
Hey @greg [iero] could you please share your workspace version from
default.core.workspace.version ?
It's indeed not normalHi @Prastoin When I launch this command
WORKSPACE_VERSION=$(docker exec -e PGPASSWORD="${PG_DATABASE_PASSWORD}" "${CONTAINER_NAME}" \
psql -h localhost -U "${PG_DATABASE_USER}" -d "${PG_DATABASE_NAME}" -t -c \
"SELECT version FROM core.workspace LIMIT 1;" | xargs)
I get : 1.1.1It looks like you've already upgraded your instance correctly
Any chance youv'e been upgrading to 1.1.1 automatically without noticing before ?
for example using TAG=latest
no, I have TAG=v1.1. Before it was 1.0.
I updated some days ago, and I did not notice this warning until yesterday as I was looking for why I have no logs. And this warning seems strange then!
When restarting your app it will attemp to do an upgrade
If you're restarting on the same version it will detect it has already been upgraded
Not issue here from my understanding as it's the first bootstrap post TAG mutation
Ok I get it. So the "fromWorkspaceVersion: 1.0.0" is just a wrong message, the bootstrap did not find this 1.0.0 anywhere in my install
No
"fromWorkspaceVersion: 1.0.0" is the expect workspace version to be migrated in 1.1.1
It did not find any because you already upgraded before, it will attempt an upgrade on any restart
Ok so I'm good then, thanks 🙂
Would it be fine to have TAG=latest and then just upgrade by changing the Image version in docker-compose.yml?