We’re on stable 1.4.2 and I saw in /Admin a notification that an upgrade was available. On the web update page, the discourse_manager was the only thing enabled to be upgraded, with other updates shown for other packages/plugins but their buttons not enabled. I upgraded but after it finished when returning to the the /Admin page and going back to select further updates (to update Discourse main, plugins etc) I get the following: [изображение] It’s no problem for me to go in and do that via SSH, but I just wanted to ping incase this wasn’t normal for a stable small point release? EDIT: I upgraded fine doing the above git pull etc, so really it’s just a question of if it needed to do this or not, i.e. not upgrade via the web admin?

Note to self: Don’t post here anymore.

We upgraded the base image because one of the library we use for optimizing PNGs was not available anymore https://github.com/discourse/discourse_docker/commit/11e1b624197ab8ad879c7572487439b078a6a629

1.4.3 Upgrade Oddity?

Product Support

omfg (omfg) 27.Ноябрь.2015 18:11:43 2

Did you try to click on the link and read the first 2 sentences?

Тема		Ответов	Просм.
Upgrades via the web UI are disabled until you run the latest image Product Support	5	1959	31.10.2017
A critical update is available. Please upgrade! But when going to upgrade shows up to date Product Support	4	441	12.04.2024
"Upgrade all" button is awesome! Praise	4	2652	02.07.2018
Upgrade Discourse to 2.3.0.beta4 Product Support	8	974	12.03.2019
Update error, website unavailable, possibly plugin related? Self-hosting	2	1464	12.01.2018

1.4.3 Upgrade Oddity?

Связанные темы