All Versions
231
Latest Version
Avg Release Cycle
50 days
Latest Release
-

Changelog History
Page 10

  • v8.0.4 Changes

    • ๐Ÿ›  Fixed an issue where notification digests weren't sending on some systems.
  • v8.0.3 Changes

    • ๐Ÿš‘ [CRITICAL] Fixed an issue where performing a bulk merge would merge more than intended.
    • ๐Ÿ›  Fixed saving the "Use Default Scrubbers" project setting
    • ๐Ÿ›  Fix syncing documentation when behind an http proxy
  • v8.0.2 Changes

    • ๐Ÿ›  Fix IntegrityError after merging groups.
    • Be less noisy about Cannot digest timeline, timeline is not in the ready state.
    • ๐Ÿ›  Fix incorrect Install links.
    • ๐Ÿ›  Fixed being able to select a Chinese locale.
    • ๐Ÿ›  Multiple bulk deletion improvements and bug fixes.
    • ๐Ÿ“š Clarify Forcing documentation sync error messaging.
  • v8.0.1 Changes

    • Ignore blob: urls in hashing algorithms.
    • โฌ†๏ธ Bump extra data size to 16k (previously 4k)
    • ๐Ÿ›  Fixed some odd behavior where superusers appeared as members of a team when they weren't.
    • 0๏ธโƒฃ By default, new superusers created through sentry createuser will be added as a member to a team, if there is only one team available.
  • v8.0.0 Changes

    ๐Ÿ”– Version 8 of Sentry introduces a brand new frontend. Most of the application has been overhauled ๐ŸŒ and rewritten on top of React and our web API. Additionally many new features have been exposed ๐Ÿš€ related to workflows (user assignment, snooze, resolution) and release tracking. This changelog does not attempt to capture the six+ months of incremental features and improvements in this ๐Ÿš€ release of Sentry.

    A Note on MySQL

    
    Due to numerous issues over the years and recent discoveries that nearly all schema migration was
    broken in MySQL (due to some behavior in our migration tool), we've made the decision to no longer
    ๐Ÿ‘Œ support MySQL. It is possible to bring the schema up to date on a MySQL machine, but Sentry's
    automated migrations will likely not work and require DBA assistance.
    
    ๐Ÿ‘ Postgres is now the only supported production database.
    
    ๐Ÿ‘ท A Note on Workers
    

    ๐Ÿ‘ท In the past it was supported to run Sentry's queue workers with the -B option to also spawn ๐Ÿ‘ท a celery beat process within the worker. This is no longer supported as it causes problems in some queue setups (in particular if redis is being used). Instead you should now spawn two ๐Ÿ“š independent processes. This is outlined in the installation documentation.

    ๐Ÿ”„ Changes to Quotas

    
    Team and System based quotas are now longer available. A new organization-relative project quota replaces them
    ๐Ÿ”ง and can be configured via Rate Limits on the organization dashboard.
    
    Notification Digests
    

    Email notifications will now automatically rollup if the rate of notifications exceeds a threshold. These can be ๐Ÿ”ง configured on a per project basis in Project Settings.

    ๐Ÿ”ง Configuration

    
    ๐Ÿ”ง An Install Wizard has been added to aid in configuring necessary first-run options. Notably your Admin Email,
    โšก๏ธ and URL Prefix. The Installation Wizard will also help any future updates and aid when new options are introduced.
    
    ๐Ÿ”ง A new configuration backend is now utilized for several options. These options can now be
    ๐Ÿ”ง configured via the web UI.
    
    - ๐Ÿ”ง A new configuration file, `config.yml` has been introduced. This new file is generated during `sentry init`
      the first time, and expected to be pointed at a directory. `config.yml` is the home for new configuration options that will be moved from the existing python config file.
    
    - ``SENTRY_URL_PREFIX`` has been deprecated, and moved to `system.url-prefix` inside of `config.yml` or it
      can be configured at runtime.
    
    - ๐Ÿ”ง ``INTERNAL_IPS``, if configured, will now restrict superuser access to only users with both ``is_superuser``
      and a matching IP.
    
    CLI
    ~~~
    
    The `sentry` CLI tooling has been rewritten to be faster and less confusing.
    
    Static files
    ~~~~~~~~~~~~
    
    โšก๏ธ Static files are now served with a far-futures Cache-Control header, and are versioned by default. If you were serving `/_static/` explicitly from your server config, you may need to update your rules or adjust the `STATIC_URL` setting accordingly.
    
    General
    ~~~~~~~
    
    - ๐Ÿ— Source builds now require Node 0.12.x or newer.
    - ๐Ÿšš The ``public`` setting on projects has been removed
      - This also removes ``SENTRY_ALLOW_PUBLIC_PROJECTS``
    - Clients which were only sending ``sentry_key`` and not using CORS will no
      longer be able to authenticate.
    - ๐ŸŒฒ All incoming events now log through ``sentry.api``, which will additionally
      capture far more events with improved console formatting.
    - ๐Ÿšš The 'sentry' user can no longer be removed.
    - The Cassandra nodestore backend was broken, and this has been resolved.
    - ๐Ÿ”Œ The ``has_perm`` plugin hook is no longer used.
    - Do not unconditionally map sys.stdout to sys.stderr
    - The HTTP interface's internal structure has greatly changed. Headers and Cookies are now lists. Body
      is now stored as a string.
    - ๐ŸŒฒ The internal metrics backend now supports both Datadog and a simple logging implementation (useful in DEBUG).
    - Member roles can now view client keys (DSNs).
    - ๐Ÿ“š Documentation for configuration wizards is now pulled from docs.getsentry.com as part
      of the ``upgrade`` and ``repair`` processes.
    - The SSO flow for existing users has been greatly improved to avoid duplicate accounts.
    - Deletions are delayed for one hour and can be cancelled by changing the status
      back to ``VISIBLE``.
    - Membership permissions have been overhauled and have been flattened into a single tiered
      role. Additionally owners will no longer be automatically added to new teams.
    - ๐Ÿ”Œ ``NotificationPlugin`` now requires ``is_configured`` to be declared.
    - โฌ†๏ธ ``sentry.search`` should no longer be extended (``index`` and ``upgrade`` have been removed)
    
    Client API
    ~~~~~~~~~~
    
    - The ``culprit`` attribute will now automatically be filled when not present.
    - The ``in_app`` attribute on frames will now be computed on event submission when not present.
    - The ``ip_address`` value will always be stored on the user interface when possible.
    - The user interface no longer accepts data missing one of the required identifiers.
    - ๐Ÿ–จ The ``fingerprint`` value is now stored in ``Event.data``.
    - The ``environment`` attribute is now soft-accepted and tagged.
    
    Schema Changes
    
    • โœ‚ Removed the Project.platform column.
    • โœ‚ Removed the Project.organization column.
    • โœ‚ Removed the AccessGroup table.
    • โž• Added EventUser table.
    • โž• Added user.{attribute} to search backends.
    • โž• Added Project.first_event column.
    • โž• Added Release.owner column.
    • โž• Added Organization.default_role column.
    • โž• Added OrganizationMember.role column.
    • โž• Added Broadcast.upstream_id column.
    • โœ‚ Removed Broadcast.badge column.
    • โž• Added Broadcast.title column.
    • Migrated blob data in File to FileBlob.
    • โœ‚ Removed File.storage column.
    • โœ‚ Removed File.storage_options columns.
    • โž• Added OrganizationOption table.
    • โž• Added GroupSnooze table.
    • โž• Added GroupResolution table.
    • โž• Added GroupBookmark.date_added column.
    • โœ‚ Removed User.last_name column.
    • (App-only) Renamed User.first_name to User.name.
    • โœ‚ Removed Activity.event column.
    • โœ‚ Removed Event.num_comments column.
  • v7.7.1 Changes

    • ๐Ÿ“Œ Pin Kombu dependency due to incompatibility.
  • v7.7.0 Changes

    • The behavior of create_or_update has changed. If you're using it please see the updated function.
    • โž• Added Group.first_release column.
    • โž• Added SavedSearch model for future features.
    • โž• Added Release.new_groups column.
    • ๐Ÿ—„ The explore feature is now deprecated and links have been hidden.
    • Expanded various API endpoints for future usage.
    • ๐ŸŽ‰ Initial prototype of embeddable crash reports. This adds the UserReport model.
    • โž• Added basic UI reporting for status checks.
    • โž• Added celery/beat alive check.
    • โž• Added celery app version check.
    • โž• Added queue overview to internal administration.
    • Upped TSDB's storage of 10s to 60m of data.
    • โž• Added protocol version 7 to client spec.
      • Adds fingerprint attribute.
    • The behavior of SENTRY_ENABLE_EXPLORE_USERS is now default and the setting has been removed.
  • v7.6.2 Changes

    • ๐Ÿ‘Œ Improved (fixed?) static bundling in various conditions.
  • v7.6.1 Changes

  • v7.6.0 Changes

    ๐Ÿš€ This releases entirely removes Access Groups. If you're upgrading from an installation that had yet to migrate away from this system you should first upgrade to a previous version, run the migration wizard, and then continue the upgrade.

    • ๐Ÿšš The project-wide Alert system has been removed (to be re-implemented in the future).
    • ๐Ÿšš Access groups have been permanently removed.
    • โž• Added 'access_token' to data blacklist.
    • ๐Ÿšš The legacy (unused) search tables have been removed.
    • โฌ†๏ธ Upgrades must now be applied manually via sentry upgrade or with sentry start --upgrade. (Don't forget to use --noinput if you're doing this via automated tooling!)
    • ๐Ÿšš Event.checksum and Group.checksum have been removed.
    • ๐Ÿšš The cleanup task has been removed (the command is still available).
    • Various optimizations to cleanup for Postgres users.
    • 0๏ธโƒฃ Within single organization mode users will automatically be added to the default organization.
    • โž• Added Organization.merge_to() helper to assist with merging organizations. (i.e. in an on-premise install which wants to convert to a single organization)
    • ๐Ÿ†• New import and export commands now exist for creating backups of critical metadata (i.e. api keys, projects, user settings)