All Versions
104
Latest Version
Avg Release Cycle
39 days
Latest Release
2089 days ago

Changelog History
Page 7

  • v4.1.0 Changes

    March 19, 2014
    • โž• Added verify_ssl option to HTTP transport (defaults to False).
    • โž• Added capture_locals option (defaults to True).
    • message can now be passed to capture* functions.
    • ๐Ÿ‘ Django <1.4 is no longer supported.
    • Function object serialization has been improved.
    • ๐Ÿšš SanitizePasswordsProcessor removes API keys.
  • v4.0.0 Changes

    December 26, 2013
    • Sentry client protocol is now version 4.
  • v3.6.0 Changes

    December 11, 2013

    This changelog does not attempt to account for all changes between 3.6.0 and 3.0.0, but rather focuses on recent important changes

    • ๐Ÿ”จ Transport modules paths have been refactored.
    • 0๏ธโƒฃ The threaded transport is now the default.
    • ๐Ÿ“š Client.context has changed. Please see documentation for new API.
    • Client.user_context was added.
    • Client.http_context was added.
    • Client.extra_context was added.
    • Client.tags_context was added.
    • ๐Ÿ‘ Flask support has been greatly improved.
    • ๐Ÿšš raven.contrib.celery.Client has been removed as it was invalid.
  • v3.0.0 Changes

    December 27, 2012

    3.0 of Raven requires a Sentry server running at least version 5.1, as it implements ๐Ÿ”– version 3 of the protocol.

    ๐Ÿ‘Œ Support includes:

    • Sending 'python' as the platform.
    • ๐Ÿ‘ The 'tags' option (on all constructors that support options).
    • โšก๏ธ Updated authentication header.

    โž• Additionally, the following has changed:

    • ๐Ÿ”ง Configuring the client with an empty DSN value will disable sending of messages.
    • All clients should now check Client.is_enabled() to verify if they should send data.
    • Client.create_from_text and Client.create_from_exception have been removed.
    • ๐Ÿšš Client.message and Client.exception have been removed.
    • ๐Ÿšš The key setting has been removed.
    • The DEBUG setting in Django no longer disables Raven.
    • ๐Ÿšฆ The register_signals option in RAVEN_CONFIG (Django) is no longer used.
    • A new helper, Client.context() is now available for scoping options.
    • ๐Ÿ—„ Client.captureExceptions is now deprecated in favor of Client.context.
    • 0๏ธโƒฃ Credit card values will now be sanitized with the default processors.
    • A new eventlet+http transport exists.
    • A new threaded+http transport exists.
    • ๐Ÿ‘ PyPy is now supported.
    • ๐Ÿ‘ Django 1.5 should now be supported (experimental).
    • ๐Ÿ‘ Gevent 1.0 should now be supported (experimental).
    • ๐Ÿ‘ Python 2.5 is no longer supported.
    • ๐Ÿ‘ [Django] The skip_sentry attribute is no longer supported. A new option config option has replaced this: SENTRY_IGNORE_EXCEPTIONS.
  • v2.0.0 Changes

    July 05, 2012
    • ๐Ÿ†• New serializers exist (and can be registered) against Raven. See raven.utils.serializer for more information.
    • You can now pass tags to the capture method. This will require a Sentry server compatible with the new tags protocol.
    • A new gevent+http transport exists.
    • A new tornado+http transport exists.
    • A new twisted+http transport exists.
    • ๐Ÿ‘€ Zope integration has been added. See docs for more information.
    • ๐Ÿš€ PasteDeploy integration has been added. See docs for more information.
    • ๐Ÿ‘€ A Django endpoint now exists for proxying requests to Sentry. See raven.contrib.django.views for more information.
  • v1.9.0 Changes

    May 23, 2012
    • Signatures are no longer sent with messages. This requires the server version to be at least 4.4.6.
    • ๐Ÿ›  Several fixes and additions were added to the Django report view.
    • long types are now handled in transform().
    • ๐Ÿ‘Œ Improved integration with Celery (and django-celery) for capturing errors.
  • v1.8.0 Changes

    May 16, 2012
    • There is now a builtin view as part of the Django integration for sending events server-side (from the client) to Sentry. The view is currently undocumented, but is available as {% url raven-report %} and will use your server side credentials. To use this view you'd simply swap out the servers configuration in raven-js and point it to the given URL.
    • A new middleware for ZeroRPC now exists.
    • A new protocol for registering transports now exists.
    • Corrected some behavior in the UDP transport.
    • ๐Ÿšฆ Celery signals are now connected by default within the Django integration.
  • v1.7.0 Changes

    April 18, 2012
    • The password sanitizer will now attempt to sanitize key=value pairs within strings (such as the querystring).
    • ๐Ÿšš Two new santiziers were added: RemoveStackLocalsProcessor and RemovePostDataProcessor
  • v1.6.0 Changes

    April 13, 2012
    • Stacks must now be passed as a list of tuples (frame, lineno) rather than a list of frames. This includes calls to logging (extra={'stack': []}), as well as explicit client calls (capture(stack=[])).

    This corrects some issues (mostly in tracebacks) with the wrong lineno being reported for a frame.

  • v1.4.0 Changes

    February 05, 2012
    • Raven now tracks the state of the Sentry server. If it receives an error, it will slow down requests to the server (by passing them into a named logger, sentry.errors), and increasingly delay the next try with repeated failures, up to about a minute.