Bugsink - Package Updates

[nebulon]

This topic is to track Bugsink package updates.

Please open issues in a separate topic instead of replying here.

[nebulon]

[0.1.0]

• Initial release

[Package Updates]

[0.2.0]

• tests implemented

[Package Updates]

[0.3.0]

• username is actually email

[Package Updates]

[0.4.0]

• Fix env.sh

[Package Updates]

[0.5.0]

• Fix documentation link

[Package Updates]

[0.5.1]

• Update bugsink to 2.0.14
• Full Changelog
• sourcemaps upload now works for sentry-cli >= 3.0.0, See #290
• Add chunk_max_days and file_max_days parameters to vacuum_files command and task
• Update whitenoise requirement from ==6.11.* to ==6.12.*
• Fix FEATURE_MINIDUMPS env-parsing in docker template
• mobile menu: somewhat workable, See #120
• Add index on (digested_at, digest_order) Fix #322
• Move mark_safe closer to actual escaping

[Package Updates]

[0.6.0]

• Update bugsink to 2.5.0
• Full Changelog
• Fail to start when PID_FILE is configured to be in a directory not owned by the process running gunicorn/snappea (typically: the bugsink user). The reason for this is: extra defense in depth, as per #195.
• Fix: prevent DNS rebinding bypasses in outbound webhook protection.
• Fix: cap the number of tags stored per event.
• Fix: scope issue actions and event lookups to the authorized project/issue.
• Fix: scope sourcemap and minidump debug-file metadata to projects.
• Fix: harden webhook URL validation parsing and reject non-RFC characters.
• Fix: avoid using upload checksums as temporary filenames.

[Package Updates]

[1.0.0]

• Update bugsink to 2.5.1
• Full Changelog
• Some very ancient migration files, long since squashed and replaced, have been removed. In the unlikely event that you are running a pre-1.2.0 release and have not yet run migrations, you will need to upgrade to any release from 1.2.0 to 2.5.0 and run migrations before upgrading to 2.5.1 or later. See #470.
• Fix: enforce the configured lifetime for email verification, password-reset and new-user setup links.
• Fix: reject webhook targets with non-global IPv4 addresses embedded in IPv6 destinations.
• Alerts can now be sent to Telegram, Microsoft Teams and custom webhook endpoints. Telegram supports channels, groups and topics, Microsoft Teams uses Power Automate Workflows, and custom webhooks receive a payload based on the canonical issue API. See #368, #433 and #461.
• Log-message issues now use the actual message as their title instead of the generic "Log Message" label, including the formatted message when an SDK provides one. See #111 and #364.
• Stacktrace views now render thread-based stacktraces from message and log events, show multiple threads alongside exceptions, and support the deprecated top-level event stacktrace. See #471 and #482.
• Accept events that do not specify a platform, see #474.
• Remove the broken, Python-specific plain-text event view; the Markdown view remains available, see #473.
• Only accepted team members can join team projects, and send issue alerts only to accepted, active members, see #481.
• Hide raw exception details from production error responses when MINIMIZE_INFORMATION_EXPOSURE is enabled, see #481.