Skip to content

bugsink

v2.3.0 Feature

This release adds 2 notable features for engineering teams evaluating rollout.

✓ No known CVEs patched
Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Summary

AI summary

Added native CSP violation report handling and a 28‑day event‑volume sparkline on issue pages.

Full changelog

2.3.0 (23 June 2026)

CSP reports

Add native support for CSP violation reports via a new /api/<project_pk>/security/ endpoint, compatible with the
report-uri directive browsers emit. Reports are translated into events and pushed through the existing envelope
pipeline, grouped by (effective-directive, blocked-uri), see #371.

Sparklines

Issue event pages now show a 28-day event-volume sparkline. The sparkline is backed by hourly event-count buckets, so
regular page views do not need to rescan the event table. Bars can be clicked to jump to an event in that time bucket,
see #417 and #420.

Smaller fixes

  • Show full exception values on stacktrace pages, see #412.
  • Include Bugsink's Sentry-compatible API surface in the OpenAPI schema, see #413.
  • Return {"id": ...} from the /envelope/ endpoint, see #396.
  • Update the Docker run command in the README, see #415.

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Track bugsink

Get notified when new releases ship.

Sign up free

About bugsink

Self-hosted Error Tracking

All releases →

Related context

Earlier breaking changes

  • v2.4.0 Fails to start if PID_FILE directory not owned by process.

Beta — feedback welcome: [email protected]