Release Tracking and Deployment Notifications
You'll learn how to associate frontend errors with specific code releases and automatically alert your team when new deployments break things.
The Core Idea
When errors spike after a deployment, you need to know which release caused them. Release tracking tags each error with a version identifier (like v2.3.1 or a git commit hash), letting you filter errors by release and see which deployments introduced regressions. Deployment notifications go further—automatically alerting your team the moment a new release starts generating errors, before users complain.
Think of it like labeling batches in a factory. If defective products appear, you can instantly trace them back to batch #451 and stop the line before shipping more bad units.
How It Works
When initializing your error tracker (like Sentry), you specify a release identifier:
Sentry.init({
dsn: "your-project-dsn",
release: "my-app@2.4.0", // Tag all errors with this version
environment: "production"
});
This release string gets attached to every error. In your monitoring dashboard, you can now:
- See which errors started appearing in
2.4.0 - Compare error rates between
2.3.9and2.4.0 - Get Slack/email alerts: "10 new errors detected in release 2.4.0"
Automation
In your CI/CD pipeline, automatically notify the error tracker about deployments:
// In your deployment script
await fetch('https://sentry.io/api/0/organizations/my-org/releases/', {
method: 'POST',
headers: { 'Authorization': `Bearer ${SENTRY_TOKEN}` },
body: JSON.stringify({
version: '2.4.0',
projects: ['my-app']
})
});
This creates a "release" record. The monitoring tool can now correlate error spikes with deployment times and send notifications immediately.
Key Takeaway: Release tracking tags errors by version, while deployment notifications alert your team the instant a new release introduces problems, enabling fast rollbacks and fixes.