Developer-first error tracking and performance monitoring
OTHER License
Bot releases are hidden (Show)
Published by chadwhitacre almost 3 years ago
By: @billyvg (#28878)
Apple started moving away from their Intel based chipset to arm64 chipsets (aka as Apple Silicon).
In order to do Sentry development on this new architecture we need to do various changes to Sentry's development environment. Some of these changes include using a different Python version (arm64 support was added on Python 3.8.10), upgrading Python packages and hosting some Python wheels that third-party maintainers are not yet releasing.
By: @armenzg (#29739, #29449, #29315, #28769, #28607)
In order to do development for Sentry, we need to spin up various Docker containers.
Apple is moving away from Intel based chipset to arm64 chipsets (aka Apple Silicon).
This milestones track all work required to make sure we can still use these development services on Apple's arm64 architecture.
By: @armenzg (#29494, #29293, #29284, #29157, #29081, #29117, #29084, #28672, #28724)
Open a Dashboard widget in Discover. Add a Discover Query to a Dashboard.
By: @edwardgou-sentry (#28699, #28827, #28745, #28637)
regressed_in_release
search term to issue search (#29890) by @wedamijaparams = {}
(#29834) by @evanpurkhiserwhere_should_be_participating
(#29802) by @mgaetawhere_should_be_participating
(#29757) by @mgaetaPipeline
to a file (#29679) by @mgaetasentry.notifications
(#29678) by @mgaetaraw
in ProjectOwnership
(#29628) by @wedamijapath
matching for project owners (#29629) by @wedamijapost_process.handle_owner_assignment
(#29632) by @oiokiRuleProcessor
so that expensive conditions are run last (#29558) by @wedamijaside
to operand (#29419) by @wmakif: always()
conditions from workflows (#29414) by @billyvgGroupHistory
to group deletions (#29487) by @wedamijaorganizations:group-history
feature flag. (#29470) by @wedamijaGroupHistory.actor
to set null on delete (#29469) by @wedamijaSET_RESOLVED_IN_PULL_REQUEST
activity in GroupHistory
(#29466) by @wedamijaSET_RESOLVED_IN_COMMIT
activity in GroupHistory (#29464) by @wedamijaget_prev_history
to fetch the correct previous history row for a status (#29425) by @wedamijaentity_handler=True
to metrics-extraction feature (#29407) by @untitakerupdate_groups()
from requests (#29303) by @mgaetaorganization
from build_linking_url()
(#29299) by @mgaetasync
helper (#29158) by @mgaetacheck migration
job (#29118) by @billyvgvalidHookNames
(#29094) by @evanpurkhiseremail
utils into files (#28614) by @mgaetasync_status_inbound
a Task (#28906) by @mgaetacomparisonDelta
parameter in OrganizationEventsStatsEndpoint
(#29028) by @wedamijatimeseries_query
to make comparison queries (#29018) by @wedamijahas_reappared
can be undefined (#29004) by @wedamijacomparison_delta
to metric alerts api. (WOR-1219) (#28707) by @wedamijaconfirm
prop of SelectField less complex (#28681) by @evanpurkhiseritemKey
in removeRow
(#28664) by @mgaetacomparison_delta
field to AlertRule
. (WOR-1218) (#28665) by @wedamijaother
(#28642) by @wmakBaseEventFrequencyCondition
to be able to perform comparison alerts (#28644) by @wedamijanotification-slack-automatic
less often (#28601) by @mgaetasample_rate
configurable in callback_timing
function (#28583) by @wedamijaPublished by BYK almost 5 years ago
Please see our blog post: https://blog.sentry.io/2020/01/07/self-hosted-sentry-10-is-ready-to-serve-get-it-while-its-hot/
Published by BYK over 5 years ago
src/sentry
(#13743)See https://github.com/getsentry/sentry/compare/9.1.1...9.1.2 for full changes
See https://github.com/getsentry/sentry/compare/9.1.0...9.1.1 for full changes
The changelog for Sentry 9.1 is summarized. For full details, we recommend reviewing the
full set of SCM changes on GitHub.
First, an important preface:
FUTURE VERSIONS OF SENTRY WILL INTRODUCE BACKWARDS INCOMPATIBLE INFRASTRUCTURE
This is the last version in the 9.x series, and our next release will migrate many legacy technologies onto standardized versions our SaaS service uses. The most notable, known concerns are:
This is required for Sentry to continue to support open source releases in a meaningful way, and ensures we have only a single, standard way of running the services.
We've added a new global integration concept to Sentry, which raises plugins to the organization level. Access to these integrations are controlled with the org:integrations
scope, and are granted to any user with an Admin or higher role.
This release includes integrations for:
There is additionally a Slack integration, though it requires a now-deprecated workspace token in order to use.
Note: a known issue exists where integrations are always shown as enabled, even when you haven't configured the appropriate server settings (such as OAuth keys).
Various improvements for native (compiled) runtimes is included in this release.
org:integrations
)See https://github.com/getsentry/sentry/compare/releases/9.0.x...9.1.0 for full changes
Published by mattrobenolt over 6 years ago
The changelog for Sentry 9 is summarized. For full details, we recommend reviewing the
full set of SCM changes on GitHub. There are far too many changes to list in Sentry 9,
but the major highlights are documented below.
There are also significant schema and data changes in this release, so plan for a huge amount
of updates and a measurable increase in utilization of your data stores.
Note: Major features which are undocumented here should be considered unstable, and are almost
certainly behind a feature switch which is intended to be disabled.
We've removed the project-manager-esque dashboard and brought back a team/card based selection as
as a new sidebar for quick access. We will continue to iterate on what projects mean in Sentry
going forward and this is simply a first step towards future changes.
A new global settings UI has been introduced. This is an attempt to unify all settings and make
it easier to find the numerous configuration options throughout Sentry.
Environments have been moved up in the hierarchy and are now a first class citizen. While
still early, this is intended to replace the need for having separate projects per environment.
To use environments you simply need to ensure you're configuring the environment
parameter
in the Sentry SDK, and it should automatically propagate into Sentry proper.
A new owners feature allows you to define per-project rules for declaring explicit ownership.
Much like GitHub's .gitowners, this helps Sentry understand who is responsible for a specific
issue, and more importantly lets you limit email alerts to only the relevant parties.
In addition to explicit owners, the release framework has expanded to support implicit owners
and suspect commits. This currently only works with GitHub.com hosted repositories, but will be
expanded to support other providers in future versions of Sentry.
Projects can now be associated with many teams, and teams can be referenced in comments and
assignment as well as the new ownership features.
Both Team and Project names have been deprecated, and the short name as been promoted as the
canonical reference. Teams can be mentioned using #team-name.
The beginnings of the new integration framework (plugin v3) have landed, along with an initial
version of a new Slack integration.
The new integrations framework will likely change in upcoming versions of Sentry, and we dont
suggest building against it yet.
Some caveats:
Various portions of processing for the API will require additional dependencies and configuration
(such as symbolic).
As part of GDPR, the open source version of Sentry now changes the default policy for its beacon
(the service which tells sentry.io statistics about open source usage) to not send the system's
contact email address by default. You can still opt-in to this, which will allow us to contact you
in the event of a major security issue.
See https://github.com/getsentry/sentry/compare/releases/8.22.x...9.0.0 for full changes
SAML2AuthProvider
. See getsentry/sentry-auth-saml2.ProjectSymCacheFile
model.TagValue(project_id, key, last_seen)
GroupShare
model.See https://github.com/getsentry/sentry/compare/releases/8.21.x...8.22.0 for full changes
List-Id
header) to digest emails.IdentityProvider
model.Identity
model.UserIdentity
model.ProjectTeam
modelSee https://github.com/getsentry/sentry/compare/releases/8.20.x...8.21.0 for full changes
redis.clusters
configuration along sideProjectPlatform(last_seen)
columnGroupCommitResolution.commit_id
citext
extension in Postgres.TagKey.project_id
foreign key constraintTagValue.project_id
foreign key constraintGroupTagKey.project_id
foreign key constraintGroupTagKey.group_id
foreign key constraintEmail
modelSee https://github.com/getsentry/sentry/compare/releases/8.19.x...8.20.0 for full changes
integration_id
for a givenIntegration
modelOrganizationIntegration
modelProjectIntegration
modelRepository.integration_id
columnSee https://github.com/getsentry/sentry/compare/releases/8.18.x...8.19.0 for full changes
auth.allow-registration
) for determining whether registrationRelease.commit_count
Release.last_commit_id
Release.authors
Release.total_deploys
Release.last_deploy_id
FeatureAdoption
modelDSymBundle
DSymObject
DSymSDK
DSymSymbol
GlobalDSymFile
GroupHash.state
ReleaseEnvironment(project_id)
ReleaseCommit(project_id)
ReleaseEnvironment(project_id, release_id, environment_id)
GroupResolution.type
GroupResolution.actor_id
Project.platform
GroupSnooze.actor_id
ScheduledJob
GroupResolution.actor_id
ScheduledJob
modelUser.last_active
See https://github.com/getsentry/sentry/compare/releases/8.17.x...8.18.0 for full changes
in_app
values for cocoa events.project:rate-limits
feature).sentry.deletions
abstraction to improve bulk deletions.GroupTagValue.group_id
foreign key constraintGroupTagValue.project_id
foreign key constraintDeploy.notified
columnEventTag.date_added
Environment(organization_id, name)
ReleaseEnvironment(organization_id, release_id, environment_id)
EventUser.name
columnUserReport.event_user_id
columnSee https://github.com/getsentry/sentry/compare/releases/8.16.x...8.17.0 for full changes
0302
that prevented upgradingSee https://github.com/getsentry/sentry/compare/8.16.0...8.16.1 for full changes
Distribution
modelReleaseFile.dist
columnUserOption.organization
columnCommitAuthor.external_id
columndateStarted
in releases endpointsSee https://github.com/getsentry/sentry/compare/releases/8.15.x...8.16.0 for full changes
sentry.app
to use individual modules.--concurrency
on sentry cleanup
Fixes SHORTID
are included in releasesDeploy
modelApiApplication
modelApiAuthorization
modelApiGrant
modelApiToken.key
columnApiToken.application
columnApiToken.refresh_token
columnApiToken.expires_at
columnApiToken.scope_list
columnApiKey.scope_list
columnReleaseHeadCommit
modelSee https://github.com/getsentry/sentry/compare/releases/8.14.x...8.15.0 for full changes
See https://github.com/getsentry/sentry/compare/8.14.0...8.14.1 for full changes
Fixes SHORTID
annotation will now be tracked appropriately.sentry.utils.encryption
).timesSeen
keyword to issue search.app
for cocoa events.assignedTo
param to /projects/{org}/{project}/issues/
.Release(organization_id, version)
Release(project_id, version)
GroupCommitResolution
model.Environment.organization_id
column.EnvironmentProject
model.Project.flags
column.Environment.organization_id
column.Environment.project_id
and ReleaseEnvironment.project_id
columnsSee https://github.com/getsentry/sentry/compare/releases/8.13.x...8.14.0 for full changes
mail:subject_template
option).ReleaseProject.new_groups
column.OrganizationAvatar
model./organizations/{org}/
endpoint.See https://github.com/getsentry/sentry/compare/releases/8.12.x...8.13.0 for full changes
activeSince
to search (uses active_at
).firstSeen
to search (uses first_seen
).lastSeen
to search (uses last_seen
).firstRelease
to search (uses first_release
).Group.first_release
.<=
).repos
interface has been added.Release.organization
column.ReleaseProject
model.ReleaseCommit.organization_id
column.ReleaseFile.organization
column.ReleaseEnvironment.organization_id
column.See https://github.com/getsentry/sentry/compare/releases/8.11.x...8.12.0 for full changes