Sentry 8.2.2 / 8.1.4 is a security update. Code execution vulnerability that's only exploitable by Sentry superusers, so nothing too urgent.
Description
Description
Related Objects
Related Objects
Event Timeline
Comment Actions
8.2.4 / 8.1.5 is another security update. "If being run in multi-organization mode, it was possible for a user to craft a URL which would allow them to view membership details of other users." - not a big deal.
Gilles has pointed out that Sentry 8 dropped MySQL support. Our PostgreSQL puppet roles need a lot of love, so this upgrade will be a big task.
Comment Actions
8.2.5 is also another security update "Fixed a bug which allows API keys more permission than granted within the organization."
But they're upto 8.10.0 now...
Comment Actions
But they're upto 8.10.0 now...
The release cycle has roughly been one release per month.
(In my organisation the Sentry instances run using Docker and docker-compose, using the on-premise setup, which takes away most of the upgrade pain).
Comment Actions
This task has been assigned to the same task owner for more than two years. Resetting task assignee due to inactivity, to decrease task cookie-licking and to get a slightly more realistic overview of plans. Please feel free to assign this task to yourself again if you still realistically work or plan to work on this task - it would be welcome!
For tips how to manage individual work in Phabricator (noisy notifications, lists of task, etc.), see https://phabricator.wikimedia.org/T228575#6237124 for available options.
(For the records, two emails were sent to assignee addresses before resetting assignees. See T228575 for more info and for potential feedback. Thanks!)
Comment Actions
Sentry is at 10.0 now (actually, 20.6, but they have changed their versioning schema) so this task is a bit pointless.