jh-block b8b2ef3d62 Inject Sentry DSN at build time instead of hard-coding it ...

Remove the hard-coded Sentry DSN from source code and instead inject it
via the SENTRY_DSN environment variable at build time. This ensures that
cloned/forked builds don't send errors to our Sentry project, while
official release and canary builds get the DSN from a GitHub Actions
secret.

- Rust: use option_env!("SENTRY_DSN") for compile-time injection
- Electron: use process.env.SENTRY_DSN via Vite define block
- CI: pass SENTRY_DSN secret through release and canary workflows
- Cross.toml: add SENTRY_DSN to passthrough for cross-compiled builds

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-03-10 11:27:30 +01:00

..

actions/generate-release-pr-body

Fetch less and use the right SHA (#5621)

2025-11-07 09:25:07 -05:00

DISCUSSION_TEMPLATE

Add Diagnostics Info to Q&A and Bug Report Templates (#5565)

2025-11-04 14:44:03 -05:00

ISSUE_TEMPLATE

Cleanup: Remove Recipe Key Flow (#6015)

2025-12-09 11:13:45 -05:00

workflows

Inject Sentry DSN at build time instead of hard-coding it

2026-03-10 11:27:30 +01:00

CODEOWNERS

Add @angiejones as CODEOWNER for documentation (#7711)

2026-03-07 17:08:39 +00:00

copilot-instructions.md

copilot instructions: reword no prerelease docs (#7101)

2026-02-26 15:55:56 +00:00

pull_request_template.md

Cleanup: Remove Recipe Key Flow (#6015)

2025-12-09 11:13:45 -05:00