-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
GitLab Access token exposed in Sentry notification emails #89257
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Assigning to @getsentry/support for routing ⏲️ |
@syphernl -- I'm looking in to this issue. The template for this email hasn't change in quite some time. sentry/src/sentry/templates/sentry/emails/activity/release.html Lines 58 to 69 in 0c743bb
|
@mdtro I noticed there were 3 repositories added without a name (in Sentry-format, e.g. |
Routing to @getsentry/product-owners-settings-security-privacy for triage ⏲️ |
@syphernl -- Ah, I linked the wrong lines of the template. Yes, this is intended to be the repository name.
SpikeeLabs/semantic-release-sentry-releases is not maintained by Sentry. I do see in their README though that the repository URL/name has some default behavior I suspect you may be running in to (see below). Let me know if you still experience the same issue after updating your configuration. I'll keep this issue open for now. |
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Re: Deployed version 1.7.1 to production
)https://gitlab-ci-token:[email protected]
). In an earlier release it showed the repository path (in sentry-style)Expected Result
No access tokens to be exposed in notification emails sent out
Actual Result
Product Area
Releases
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: