[security issue] Sentry Auth token exposed in eas.json

[TowhidKashem]

Describe the bug

89c975413cd543fbb683b11bec984fc2163d9a77312c41c0b4480a570f3daa65

According to this thread:

expo/sentry-expo#321

you don't want to expose the auth token and use env variables instead. The thread is about using it in app.json but I think it applies here as well since the the security vulnerability is in others knowing the token first and foremost.

To Reproduce

Steps to reproduce the behavior:

1. Check eas.json
2. Confirm token is there

Expected behavior

Use env variables that are loaded via dot env where needed and not committed to the repo.

[alimony]

You should send potential security issues directly to security@bsky.app rather than opening an issue, per README.

[TowhidKashem]

You should send potential security issues directly to security@bsky.app rather than opening an issue, per README.

nice catch, I emailed them. Will keep the issue open and they can close it after resolving...

[pfrazee]

Ah lovely -- I was under the impression only public tokens were in the repo. I've deauthorized this auth token. Thanks for raising the issue.

[TowhidKashem]

Looks good!