All Versions
Latest Version
Avg Release Cycle
50 days
Latest Release

Changelog History
Page 16

  • v3.6.0 Changes

    This version focuses on improving membership control. It includes the ability to revoke project members access temporarily (by suspending them), as well as revoking users (outside of Sentry) via the user.is_active flag.

    โž• Additionally, it brings the beginnings of an "invite user" flow, allowing you to invite users who may or may not already have accounts in the system. We plan to improve ๐Ÿš€ this flow in an upcoming release to allow invitees easy registration within the system if they don't already have an account.

  • v3.5.0 Changes

    Several improvements and additions have been made around the administration, including ๐ŸŽ performance improvements.

    If you're utilizing the queue, the installation guide now recommends you switch off the ๐Ÿšš database backend, and move to something more efficient (such as Redis).

  • v3.4.0 Changes

    0๏ธโƒฃ Eventlet is no longer used as the default worker for gunicorn, and thus is no longer installed by default. If you're using the udp worker, or send_fake_data you MUST ๐Ÿ‘ท install eventlet yourself. The recommended worker class for gunicorn is now gevent as it corrects some issues with async queries in psycopg2.

  • v3.3.0 Changes

    The queue has been changed from direct Kombu, to utilizing Celery entirely. If you were โฌ†๏ธ already using the queue, the upgrade simply requires you to change "sentry start worker" to "sentry celeryd".

  • v3.0.0 Changes

    ๐Ÿ”– Version 3 of Sentry is centered around a restructure of the internal services and ๐Ÿ”Œ the architecture for running those. It also includes improvements to the plugin architecture.

    โฌ†๏ธ The upgrade process should be trivial, just be aware that if you were using --config before you must change the way you pass it so that it's before the subcommand. For example if you were doing sentry start --config... the command would now be changed to sentry --config... start.

    • Sentry no longer provides the ability to daemonize processes. This should now be done at the system level.
    • All of Sentry's CLI is now handled through Logan (, which simply pipes commands to Django's internal system utilizing custom configuration.
    • ๐Ÿ”Œ Plugins now have a hook for managing some level of permissions (beyond the required defaults).
    • ๐Ÿ”Œ The plugin interface (IPlugin) is now documented.
    • It is now recommended that clients allow the Sentry server to compute checksums.
  • v2.9.0 Changes

    • ๐Ÿ”Œ Plugins must now behave as singletons and be registered with a newly provided sentry.plugins.@register decorator.
    • The Bugzilla and Redmine extensions are no longer part of Sentry core.
    • โž• Added a global overview of projects to the administration.
  • v2.8.0 Changes

    • โž• Added an Account Settings panel which allows users to change their name, email, and password.
    • 0๏ธโƒฃ The default Sentry server now correctly wraps itself in its own middleware.
    • ๐Ÿ‘Œ Improved Real-time JavaScript.
  • v2.7.0 Changes

    • ๐Ÿ‘€ Added first_seen and last_seen to all message filter values.
    • โž• Added a new "since" option to the dashboard with a default value of 3 days.
  • v2.6.0 Changes

    • The built-in webserver is now powered by gunicorn.
    • Cleaned up several admin pages and split them into sub-pages.
  • v2.5.0 Changes

    • Corrected some queue behavior.
    • Resolve Feed now only resolves items active within current filters.
    • ๐Ÿ– Handle unicode characters in POST body for replay request.
    • Ensure client side requests run checks on HTTP_REFERER
    • ๐Ÿ“š Adjust documentation for service settings.