A discussion about a Discourse update to version 3.2.1 reveals some confusion about the update process. ecki notices that the update is labeled as 3.2.1 +9 and is unsure what this means. Arkshine explains that the +9 indicates that there are several commits available on top of the current version, while pmusaraj clarifies that these commits are fixes that were missed before the 3.2.1 tag was issued.
ecki also wonders why the main dashboard doesn’t show the update yet, despite being able to see it in the “Updates” tab. pmusaraj explains that the “Updates” screen and the main dashboard are two separate checks that don’t communicate with each other, resulting in the discrepancy.
Additionally, ecki asks if there is a mechanism to signal when a rebuild is necessary, such as for emergency updates to the base, database, or data containers.
I know you recommend tests-passed, but I need to follow the stable branch, and 3.2.1 just showed up. However I wonder why does it show up as 3.2.1 +9. Isnt the stable branch supposed to be on the released tag (at least directly after release)?
In my understanding, v3.2.0 +9 +9 means a few commits are available on top of your current version (before 3.2.1)
v3.2.1 +5 would mean you can update to the next version, 3.2.1, and a few commits have already been added on top of this version. Usually, I believe that would be important fixes backported from the main branch.
I understand that could be confusing a first. I’m wondering if this could be improved.
ah ok, so the repository column means “your local current install” - that could make sense, thanks. And i read the 3.2.1 announcement today, so i was supprised that there are already more commits, but if this is expected, its also fine with me.,
Any idea why the main dashboard doent show me that update yet? (I can understand when its only refreshed daily but then it should have also updated when i checked on the “Updates” tab manually.
This is correct, the next version tag is 3.2.1. We missed a couple of commits just before the bump, so they got added right after, hence the +5. Usually we make sure to backport before the tag is issued, but we missed it this time. It happens.
Note that the +5 commits there fix the following issues:
a translation for guidelines_topic.body
an error with security key validations in an older Firefox version (not the latest)
styling for the video placeholders
The commit id you will get after the update is 6a0aa03@ecki, it includes the fixes above.
The “Updates” screen is from the docker manager plugin, the main dashboard is core’s check, which only happens once a day. The two don’t communicate, hence the discrepancy. (Good point, though, it would be nice if they did communicate.)
While we are on the topic, is there a mechanism to decide when a rebuild should be done, for example emergency base/db/data container updates or is that never signalled in frontend update dashboard,
