Mark Stacey 37dc19a352 Migrate Sentry settings to environment variables (#11085) ... Sentry is now configured with environment variables, rather than with hard-coded values. This makes it easier to test Sentry functionality using a different Sentry account, as we did recently during QA of v9.5.1. The only change for the normal build process is the introduction of the `SENTRY_DSN_DEV` variable, which can be set via `.metamaskrc` or via an environment variable. This determines where error reports are sent. It still defaults to our team Sentry account's `metamask-testing` project. The `sentry:publish` script now requires SENTRY_ORG and SENTRY_PROJECT to be set in order to publish release artifacts. The CircleCI configuration has been updated with these values, so it should act the same as it did before. Previously we had used a CLI flag to specify the organization and project, but Sentry already natively supports these environment variables [1]. [1]: https://docs.sentry.io/product/cli/configuration/#configuration-values		2021-05-18 13:56:22 -02:30
..
account-import-strategies
constants
controllers	use safer toChecksum utility (#11117)	2021-05-17 16:19:39 -05:00
lib	Migrate Sentry settings to environment variables (#11085)	2021-05-18 13:56:22 -02:30
migrations	use safer toChecksum utility (#11117)	2021-05-17 16:19:39 -05:00
platforms
background.js
contentscript.js
disable-console.js
first-time-state.js
initSentry.js
inpage.js
metamask-controller.js	use safer toChecksum utility (#11117)	2021-05-17 16:19:39 -05:00
metamask-controller.test.js
phishing-detect.js
runLockdown.js
ui.js