Ember-cli-deploy plugin for Sentry integration — uploads sourcemaps, creates releases, and associates commits during deployment. Current version 3.1.0 supports Node 12+ and requires ember-cli-deploy ^1.0.2 as a peer dependency. The plugin runs sentry-cli under the hood and offers options for custom Sentry servers, URL prefix, and revision type. It has a stable release cadence with recent fixes for mono-repo setups and re-deploy with empty changesets.
npm install ember-cli-deploy-sentry-cliVerified import paths — ran on the pinned version, not inferred.
Shows installation, sourcemap generation setup, plugin configuration in deploy.js with environment variable for auth token, and optional revision type setting.
Ensure your Sentry auth token has at least `org:read` and `project:releases` scopes. Generate a token at https://sentry.io/settings/account/api/auth-tokens/
Connect your repository in Sentry project settings (under Releases) to associate commits. Also ensure git history is available during deployment.
Set `modulePrefix` in config/environment.js to match `appName` in deploy.js, and use `version-commit` as revision type in deploy.js for consistent release naming.
Use `orgName` and `appName` in deploy.js config instead of relying on environment variables.
Upgrade Node.js to version 12+ (14 or 16+ recommended).
Check that SENTRY_AUTH_TOKEN is set and has scopes: org:read, project:releases. See https://sentry.io/settings/account/api/auth-tokens/
Connect your repository in Sentry project settings (Releases -> Repositories). Ensure deployment runs in a git repository.
Set authToken in deploy.js config or set SENTRY_AUTH_TOKEN environment variable.