Release 9.1.2 #13902
Merged
Release 9.1.2 #13902
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* refactored releases and added restriction that latest cannot be a ref or version name. * moved release_head_commit to release.py because that's the only place it is used now. * Fixed the missing fields. * got org release details and org releases tests to work. * ensured project release tests worked * Added project release details and fixed the tests. * removed ref check.
Previously, if there was no callback function (specifically for `complete`), cleanup was skipped entirely.
This method checks if the current pathname is part of the "global selection routes". This means if you were on issue details page it would fail because it was not apart of the routes that use global selection header. Instead, what we want is to check the target pathname
Fixes ISSUE-416
If an oauth token is revoked or expired we shouldn't 500 when handling jira & jira server webhooks. Instead we can reply with a 400 and hope that one day the user deletes the webhook. Fixes SENTRY-9PF Fixes SENTRY-AA2
…s related to a removed repo (SEN-516) We have an issue that has a pr associated with it, but the repository associated with the pr has been deleted. This causes an issue with serialization, so just have the externalUrl be blank if the repository doesn't exist. Fixes SENTRY-AE5
When a customer's jira-server times out while getting a request token we don't need to 500. Instead we should convert the timeout to an ApiError instance which all integrations should be handling correctly. Fixes SEN-511 Fixes SENTRY-AG9
Stack hovercards at the same height as the global selection header so that they appear on top of the global header should they intersect. Fixes SEN-514
Get the latest in timezone data. Fixes #9945
Introduces as SLACK_INTEGRATION_USER_WST setting that can be enabled to use the legacy workspace token apps (which is what sentry.io uses). - When installing the integration we now use scopes depending on if the workspace token app setting is enabled. Otherwise we use bot tokens. NOTE that the WST app scopes have not changed. - When using bot tokens we must store the bot token _and_ user token to handle unfurling. - We can still pre-link the authorizing user, but we have to make a API request first to receive the users ID.
While the WST apps can use the oauth.access (as pointed out by @hwz, this endpoint does not return the authorizing_user_id, thus we must continue to use the legacy oauth.token endpoint for slack OAuth token access token retrieval. Fixes ISSUE-483
`sentry_repository.name` is 200 bytes long. We should allow that same length when specifying refs during release creation or repositories with long names cannot have releases made. Refs #13487
Right now this is breaking docker-sentry git builds. Guessing it will cause more issues in the future and was reported here on the forums: https://forum.sentry.io/t/enhancement-configs-not-found-on-latest-branches/6800?u=byk
* fix(installWizard): Fix client default values not set Fixes #12813.
Resolves the issue reported here: https://forum.sentry.io/t/unable-to-configure-google-oauth-provider/6872 Will also prevent any similar issues in the future, such as https://forum.sentry.io/t/enhancement-configs-not-found-on-latest-branches/6800 Fixes #13565
Expired organisation members would be deleted during silent cleanup even when filtered (not specified on the command line). Fixes GH-13968
Since we turned on Rust-based store normalization a lot more data is persisted that was previously discarded. Update code to deal with it. Fix SENTRY-9X7 Fix SENTRY-9BR Fix SENTRY-A58 Fix SENTRY-9C3 Fix SENTRY-A6Z Fix SENTRY-A48 Fix SENTRY-A4A Fix SENTRY-A9D
SnubaEvents are not renormalize because they use NodeData directly. This patch adds the wrapper class to NodeData to do just that.
The docs and assets need to be built prior to the build command, so that they are copied over from src/ -> build/ in the subsequent build command.
This is a binary wheel variant of psycopg2 that prevents needing to compile against libpq.
mattrobenolt
approved these changes
Jul 22, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Has the following commits on top of 9.1.1:
src/sentry(fix(packaging): Include all ofsrc/sentry#13743)