Jeremy_Howard expressed concern about upgrading to Discourse 1.8 without clear release notes, noting that git commit logs are too technical and lack prioritization. He asked for a summary of major changes and security fixes to help decide whether to upgrade. vinothkannans suggested checking the #releases category for details. jomaxro pointed to a blog post summarizing Discourse 1.7 and listed specific security fixes included in 1.8, such as rate limiting for cookie auth, escaping HTML in filenames and search terms, upgrading Rails, preventing password reuse during reset, validating backup upload filenames, and fixing reflected XSS vulnerabilities. Jeremy_Howard thanked both for their help. Later, sam announced that proper release notes are now available for every beta release via release-notes, celebrating the improvement with emojis. The thread highlights a community need for accessible, prioritized release summaries — especially for security updates — and confirms that Discourse has since addressed this by formalizing release notes for beta versions.
I’m always a little nervous of upgrading something when it’s working well, so was looking to see if there are release notes for 1.8 that mention if there are any critical security fixes or major feature additions that might make the upgrade a priority. All I found were the git commit messages, which are a little long, are not prioritized, and frequently don’t provide enough info for regular folks to know what they’re about.
Could anyone summarize what the major changes in 1.8 were, and whether there are any important security fixes? Is this something that may be able to be included in future releases, since I assume that a lot of people would be interested…