b55139eb1c
Some checks failed
The Sentry setup used a config.sentry.* accessor that sentry-rails has never provided, so booting with SENTRY_DSN set raised NoMethodError during environment load (e.g. db:prepare). The code only ran once a DSN was configured, which is why it surfaced in production now. Rewrites config/initializers/sentry.rb to call Sentry.init, the actual sentry-ruby API, and removes the duplicate broken block from production.rb. Verified production boots with SENTRY_DSN set (Sentry.initialized? == true) and that the no-DSN path still early-returns. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>