Suspended GitHub App installations are now treated as an expected state, so affected installations and projects are marked inaccessible and disabled without generating noisy error reports. This release also includes security fixes for known dependency advisories, reducing risk in areas that process and sanitize user-facing content.

If a connected GitHub App installation has been removed, sync and repository fetching now treat it as no longer accessible instead of failing unexpectedly. This helps keep your connected projects in a consistent state by automatically disabling access when GitHub reports the installation is gone.

This release tightens several security-sensitive flows, including custom template rendering, webhook validation, and redirect handling. It also fixes edge cases around repository slugs and makes background processing more resilient, so updates and notifications are less likely to fail unexpectedly.

This release updates Redis-backed caching and request throttling to stay compatible with recent library changes that introduced breaking behavior. The result is a more reliable setup for background jobs and Redis-based features, without needing special workarounds in production.

This release includes a security-related update to address CVE-2026-33658 affecting file uploads via Active Storage. It also resolves compatibility issues with newer Redis connection pooling behavior, helping rate limiting and caching behave more reliably in production environments.

Repository syncing now stays accurate when GitHub orgs or repositories are renamed, keeping your projects matched to the right owner and repo. Metadata syncs also make fewer GitHub calls and handle authorization and rate-limit errors more gracefully, reducing failed syncs and keeping projects up to date.