You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an automated release-please PR that bumps the version from 1.627.0 to 1.627.1 and adds the corresponding CHANGELOG entry. The changes are limited to two files:
CHANGELOG.md: Adds the 1.627.1 section with the single bug fix entry.
version.txt: Updates 1.627.0 → 1.627.1.
Both changes are correct and consistent with each other and with the release-please conventions used throughout the CHANGELOG history.
Since this release only contains the fix from #7821 ("prevent schedule pool connection exhaustion"), I reviewed that commit (e655a06) as well:
Problem: fetch_authed_from_permissioned_as was acquiring its own pool connection inside push() while a transaction already held one, leading to pool exhaustion under pressure and schedules disabling themselves.
Fix:
In jobs.rs: Pre-computes Authed via fetch_authed_from_permissioned_asbeforedb.begin(), so the pool connection is returned before the transaction starts.
In schedule.rs: For the on_behalf_of_email path, uses a new fetch_authed_from_permissioned_as_conn variant that reuses the existing transaction connection instead of acquiring a new one.
In auth.rs: Introduces fetch_authed_from_permissioned_as_conn that accepts &mut sqlx::PgConnection instead of &DB, and generalizes get_groups_for_user/get_folders_for_user to accept any PgExecutor.
The fix is well-structured — peak pool usage drops from 2 to 1 for all schedule push paths. The approach of making the helpers generic over PgExecutor is the idiomatic sqlx pattern. The commit also includes 19 comprehensive tests covering all schedule push code paths.
No issues found. The release PR is clean and ready to merge.
Reproduction Instructions
This is an automated release version bump PR — there are no user-facing UI changes to verify through the app. The underlying fix (#7821) prevents schedule pool connection exhaustion, which would manifest as schedules self-disabling under high load. To verify: navigate to the Schedules page, create or enable a schedule that triggers frequently, and confirm it remains enabled and continues to execute jobs correctly without self-disabling errors.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
1.628.0 (2026-02-06)
Features
Bug Fixes
This PR was generated with Release Please. See documentation.