For example, I’m on 2026.4.2 which is reported as fixing 25 security bugs compared to 2026.4 As 2026.4.2 is very recent, I’d expect it to have backports of most or all security fixes found in 2026.6 which was released at about the same time. But no, again I see 25 security bugs fixed. I rather sus…

This will solve it: Do not show already-fixed security advisories in comparisons (#25) main ← security-range merged 02:32PM - 02 Jul 26 UTC (UTC) [이미지] …

[이미지] Ed_S: As 2026.4.2 is very recent, I’d expect it to have backports of most or all security fixes found in 2026.6 which was released at about the same time. It does have backports, and I think that’s the issue… we’re only looking forward from 2026.4.2 → 2026.6 and pulling “these are the s…

Yeah that’s exactly right, it’s just an artefact of how the release site does the comparisons. We backport all security fixes to all currently-supported releases. I’ll see if we can add some logic to make the cross-release comparisons work better on the site :eyes:

Thanks - can confirm that no security fixes are now shown from 2026.4.2 to 2026.6 which is as expected. A related question, though. On the releases page the presently in-progress 2026.7 offers two links: [image] The second of those takes us to [이미지] v2026.7.0-latest Changelog | Discours…

[이미지] Ed_S: which presently shows 11 security fixes, relative to v2026.6.0-latest. Is that right? Yes. 2026.6.0-latest came before 2026.6.0, and most commits labelled 2026.6.0-latest are vulnerable to these security issues. So if people are running 2026.6.0-latest, they need to update to 202…

[이미지] david: most commits labelled 2026.6.0-latest are vulnerable to these security issues Hmm, OK, I see that, thanks. I was expecting the actual label for -latest is sitting at the latest version of that flavour. The actual problem I’m trying to solve, or the question I will regularly be t…

[이미지] Ed_S: I’m hoping to get a list of fixes which are in that later version, relative to my current version, and then read up on them to see if they apply or if they look severe. If you use the ‘advanced’ section at the top of the changelog, you can specify specific commits. Recently, we in…

Thanks… I’m not seeing a ‘security fixes’ section there - specifically, say, in this case. (That’s the version in use by a specific forum I use.)

Thanks for the example link. Problem with unsupported-release comparisons is now fixed , so you’ll see all the security issues you’re affected by :sweat_smile: [image]

Ah, that’s great - thanks. One more observation - I’d prefer it if the Highlights section could be collapsed, or if the Fixes box could come ahead of it in the page.

Yeah, that would be useful in this case, given the number of new highlights. Although I do have to stress: comparing from a version that’s been totally unsupported for more than a year shouldn’t really be a common thing :sweat_smile:

releases.discourse.org에서 보고된 보안 패치에 대해 혼란스러움

지원

david (David Taylor) 7월 6, 2026, 9:24오전 11

변경 사항(changelog) 상단의 ‘고급’ 섹션을 사용하면 특정 커밋을 지정할 수 있습니다. 최근에는 셀프 호스팅 사이트의 관리자 대시보드 상단에 해당 형식 링크를 도입했습니다:

글		댓글	조회수
⚠ v2026.3.0-latest.1 has 33 security fixes, is already 6 days old Support	8	458	3월 26, 2026
Any release notes (not just commit log) available? Support	4	1029	4월 23, 2019
What changed in each stable point release? Support	4	1070	5월 26, 2016
January 2026 Releases Announcements release-notes	15	1450	2월 3, 2026
July 2026 monthly release Announcements release-notes	13	601	7월 29, 2026

releases.discourse.org에서 보고된 보안 패치에 대해 혼란스러움

Related topics