Skip to content
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

fix: use the same Sentry project for different envs #167

Merged
merged 1 commit into from
Dec 18, 2024
Merged

Conversation

travis
Copy link
Member

@travis travis commented Dec 17, 2024

Sentry actually supports envs, which is useful when we start doing release notifications properly (which will give us source maps in Sentry) - use them!

Sentry actually supports envs, which is useful when we start doing release notifications properly (which will give us source maps in Sentry) - use them!
Copy link
Contributor

Website preview 🔗✨

build log

Copy link
Member

@alanshaw alanshaw left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👌

@travis travis merged commit 32dd6f8 into main Dec 18, 2024
5 checks passed
@travis travis deleted the feat/sentry branch December 18, 2024 18:28
travis pushed a commit that referenced this pull request Dec 18, 2024
🤖 I have created a release *beep* *boop*
---


##
[1.17.0](w3console-v1.16.2...w3console-v1.17.0)
(2024-12-18)


### Features

* add Sentry error tracking
([#165](#165))
([3e7069a](3e7069a))


### Bug Fixes

* use the same Sentry project for different envs
([#167](#167))
([32dd6f8](32dd6f8))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants