Hi friends, did you know these moments?: You’ve installed a bunch of bug fixes with the 1-click-updater and at the next days, you’ll notice even more bug fixes. It’s great to have a classification of features and fixes.. But how about an additional tag like e.g. [urgent] and [security]? Maybe with a trigger at the Discourse installation itselfs, that notifies the admin about important updates and not just version bumps. What’s you opinion on that? Are there updates, that could risk data base content, until they are not fixed? Best I have some bad experience and trouble until now with missing uploads ... [09]

When there are updates that are considered urgent they bump the version number.

@pfaffman And you’re suggesting to always wait?

[image] terraboss: [security]? This tag SECURITY already exists (read our security.md file in the github repository if you don’t believe me), so you’re asking for something that is already there.. also I’m not sure what you mean by “critical”. Define “critical” for us all, please?

Unless you are experiencing a particular issue that encourages you to update sooner. Things do happen between beta releases, but for the most part if there are significant reasons to upgrade they bump the version number.

[image] codinghorror: This tag SECURITY already exists (read our security.md file in the github repository if you don’t believe me), so you’re asking for something that is already there… Thanks for the hint! Can’t remember to see that before at the Github commits page.I’ll keep my eyes more open in future :slight_smile: Definition of „Critical“: I‘d like to cover situations of potential risks (= probability x amount of danger) for user data and system / security integrity. The threshold should be defined by security experts in your team, with a good understanding of FMEA at Discourse. More general: It’s nessary to categorize “unwanted effects” in terms of quality management. Unfortunately, quality management never was and will be a popular topic due to the extra classification and documentation work. But I think, any QM is better than none. Or did I miss something at the agile development culture of Discourse? :face_with_hand_over_mouth::thinking:

That’s great! Thank you :heart: I need to setup IFTTT again…

Notification about critical bug fixes?

Product Support

pfaffman (Jay Pfaffman) March 21, 2019, 10:58am 7

Oh, and now that you mention it, I do use Email me Discourse security updates from RSS feed - IFTTT

Topic		Replies	Views
⚠ v2026.3.0-latest.1 has 33 security fixes, is already 6 days old Product Support	8	541	March 26, 2026
How critical is this update? Self-hosting	3	1594	August 12, 2018
Any release notes (not just commit log) available? Product Support	4	1138	April 23, 2019
Email/Webhook Notification for Critical Security Updates Product Support	3	456	February 10, 2024
About the Bug category Bug	0	15451	February 1, 2013

Notification about critical bug fixes?

Related topics