Comparing changes

Fixes getsentry#8066

Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync. This adds `monitor_cron_jobs` to `ArqIntegration`, matching Celery's `monitor_beat_tasks`. When it's on, each `cron(...)` job sends check-ins with its schedule in the worker's timezone, so Sentry creates the monitor on the first run. The slug is the job name without arq's `cron:` prefix. It's off by default. ```python sentry_sdk.init( integrations=[ArqIntegration(monitor_cron_jobs=True, exclude_cron_jobs=["cleanup"])], ) ``` Jobs check in without a config when Crons can't express the schedule: a `second` other than 0, both `day` and `weekday` set, or a UTC offset that isn't a whole number of hours. Before arq 0.25, the config is only sent when the system timezone is UTC. Docs: getsentry/sentry-docs#20056

Update with more specific instructions on how to do things in order to increase the reviewability and maintainability of the produced changes. Also removed the Key Paths section as agents are quite adept at grepping and figuring out where what lives.

Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync. This adds `monitor_cron_jobs` to `RqIntegration` for recurring jobs from rq-scheduler's `scheduler.cron(...)` and `scheduler.schedule(..., interval=...)`. Only the worker needs the option, and it sends the cron string or interval as the monitor config. The slug is the job `id`, and jobs without one share a monitor named after the function's import path. It's off by default. ```python sentry_sdk.init( integrations=[RqIntegration(monitor_cron_jobs=True, exclude_cron_jobs=["cleanup"])], ) ``` Jobs aren't monitored when Sentry may read the cron string differently (6 fields, `@daily`, `MON`, both day fields set), the interval isn't whole minutes, the job has `repeat`, or the worker's local timezone isn't UTC. RQ's built-in `rq cron` scheduler isn't covered. The rq test envs now install `rq-scheduler` for RQ 2.x. Docs: getsentry/sentry-docs#20058 --------- Co-authored-by: Claude <[email protected]>

) Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync. This adds `monitor_periodic_tasks` to `HueyIntegration`, matching Celery's `monitor_beat_tasks`. When it's on, each `@huey.periodic_task` run sends check-ins with its `crontab(...)` schedule in UTC, so Sentry creates the monitor on the first run. The slug is the task name. It's off by default, and regular tasks are unaffected. ```python sentry_sdk.init( integrations=[HueyIntegration(monitor_periodic_tasks=True, exclude_periodic_tasks=["cleanup"])], ) ``` Tasks aren't monitored when they use a custom `validate_datetime`, restrict both `day` and `day_of_week`, or run on a Huey instance with `utc=False`. Docs: getsentry/sentry-docs#20057 --------- Co-authored-by: Claude <[email protected]>

…ry#8098) Part of a series adding automatic Crons monitoring for the most-used job schedulers in each SDK. Check-ins for a monitor that doesn't exist yet are dropped, so today each monitor has to be created by hand with its schedule copied from the code. Sending the job's schedule as the monitor config lets Sentry create the monitor and keep it in sync. This is a quick fix to keep the arq integration behaviour in line with how other integrations work. Sorry for the churn! Follow-up to getsentry#8051. Cron jobs whose schedule Crons can't express are no longer monitored, instead of checking in without a config. This matches Celery beat, and the Huey and RQ integrations from getsentry#8052 and getsentry#8053. Docs: getsentry/sentry-docs#20056 Co-authored-by: Claude <[email protected]>

### Description Fixes Celery beat interval schedules being rounded down. A 90-minute schedule was sent as "1 hour" and a 36-hour one as "1 day", so Sentry expected runs that never happened and raised false missed-check-in alerts. Intervals now use the largest unit that divides them evenly (90 minutes stays 90 minutes). Intervals that aren't a whole number of minutes, such as 90 seconds, send no monitor config and log a warning, like sub-minute intervals already do. Existing monitors with uneven intervals get the correct interval on their next check-in. For intervals that now send no config, new monitors aren't auto-created and existing ones keep their current schedule. ### Testing Unit tests for the interval conversion and the beat monitor config. --------- Co-authored-by: Claude <[email protected]>

### Description That version [is vulnerable](https://safedep.io/litellm-pypi-compromise-credential-stealer-backdoor/#payload-2-the-backdoor-in-sitecustomizepy) so it would be great to exclude it from extras. To be honest, we don't use that extra but since we use poetry, the litellm version range shows up in our poetry.lock and it doesn't look good for our security team. Thanks! #### Issues * resolves: getsentry#8103 * resolves: PY-3035 #### Reminders - Please add tests to validate your changes, and lint your code using `uv run ruff`. - Add GH Issue ID _&_ Linear ID (if applicable) - PR title should use [conventional commit](https://develop.sentry.dev/engineering-practices/commit-messages/#type) style (`feat:`, `fix:`, `ref:`, `meta:`) - For external contributors: [CONTRIBUTING.md](https://github.com/getsentry/sentry-python/blob/master/CONTRIBUTING.md), [Sentry SDK development docs](https://develop.sentry.dev/sdk/), [Discord community](https://discord.gg/Ww9hbqr) Co-authored-by: Jonny <[email protected]>

…#8114) Bumps [certifi](https://github.com/certifi/python-certifi) from 2026.7.22 to 2026.10.19. <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/certifi/python-certifi/commit/662df63d7906df66f1f07c0751a3dfe9da14d914"><code>662df63</code></a> Restore unaffected emSign roots (<a href="https://redirect.github.com/certifi/python-certifi/issues/439">#439</a>) (<a href="https://redirect.github.com/certifi/python-certifi/issues/440">#440</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/5cb238caeeb6c30ec1a7309ad3e16a5aa7b10ce8"><code>5cb238c</code></a> Remove emsign (<a href="https://redirect.github.com/certifi/python-certifi/issues/437">#437</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/69494a764d0a08f90838d53d4b0fefd3e84045d6"><code>69494a7</code></a> Bump actions/download-artifact from 8.0.1 to 8.0.2 (<a href="https://redirect.github.com/certifi/python-certifi/issues/436">#436</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/029c7b0913d79e2efb73a216fc5c5e13ef958536"><code>029c7b0</code></a> Bump actions/upload-artifact from 7.0.1 to 7.0.2 (<a href="https://redirect.github.com/certifi/python-certifi/issues/435">#435</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/9d0a8f1f3a0d6b2e38d5773db7afe1a37e4527b6"><code>9d0a8f1</code></a> Add support for Python 3.15 (<a href="https://redirect.github.com/certifi/python-certifi/issues/432">#432</a>)</li> <li><a href="https://github.com/certifi/python-certifi/commit/db472abf0a37067cb4488f036f4c19adf6b6ec3c"><code>db472ab</code></a> Bump pypa/gh-action-pypi-publish from 1.14.1 to 1.14.2 (<a href="https://redirect.github.com/certifi/python-certifi/issues/431">#431</a>)</li> <li>See full diff in <a href="https://github.com/certifi/python-certifi/compare/2026.07.22...2026.10.19">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=certifi&package-manager=uv&previous-version=2026.7.22&new-version=2026.10.19)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/getsentry/sentry-python/network/alerts). </details> Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

…ng `sentry-` entries (getsentry#8116)

Navigation Menu

Repository navigation

Comparing changes

Open a pull request

Uh oh!

Commits on Oct 20, 2026

Commits on Oct 21, 2026

Commits on Oct 22, 2026

Commits on Oct 23, 2026

This comparison is taking too long to generate.

Uh oh!