This repository was archived by the owner on Sep 8, 2026. It is now read-only.
build(deps): bump the pip group across 1 directory with 2 updates - #1
Closed
dependabot[bot] wants to merge 1 commit into
Closed
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the pip group with 2 updates in the / directory: [cryptography](https://github.com/pyca/cryptography) and [h11](https://github.com/python-hyper/h11). Updates `cryptography` from 43.0.1 to 44.0.1 - [Changelog](https://github.com/pyca/cryptography/blob/main/CHANGELOG.rst) - [Commits](pyca/cryptography@43.0.1...44.0.1) Updates `h11` from 0.13.0 to 0.16.0 - [Commits](python-hyper/h11@v0.13.0...v0.16.0) --- updated-dependencies: - dependency-name: cryptography dependency-version: 44.0.1 dependency-type: direct:production dependency-group: pip - dependency-name: h11 dependency-version: 0.16.0 dependency-type: direct:production dependency-group: pip ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Author
|
Superseded by #11. |
pull Bot
pushed a commit
that referenced
this pull request
Jun 2, 2026
…16708) Extend the hourly `detect_expired_preprod_artifacts` reaper to also mark `PreprodSnapshotComparison` rows stuck in `PROCESSING` for more than 30 minutes as `FAILED` + `TIMEOUT`, mirroring the existing `PreprodArtifactSizeComparison` handling. When a `compare_snapshots` task is hard-killed mid-run — SIGKILL after a deploy/worker SIGTERM, or OOM — the `except BaseException` cleanup that would set the row to `FAILED` never runs, so the row is left stuck in `PROCESSING`. The task's retry guard only re-runs `PENDING`/`FAILED` rows, and the task is only enqueued on a build upload or a staff recompare — never on page load/poll. So a stuck comparison is skipped forever (`skipping, comparison not in retryable state (state=1)`) and spins indefinitely for the customer. Marking it `FAILED` makes the row retryable again on the next upload or recompare, and turns the perpetual spinner into an honest failed state. This matches how the sibling `PreprodArtifactSizeComparison` PROCESSING rows are already recovered. This is fix #3 of a two-PR Graphite stack. The follow-up PR (#1) parallelizes the odiff comparison phase so large comparisons finish well within the deadline — that's the durable fix for the underlying slowness; this PR stops affected comparisons from getting permanently wedged in the meantime. Co-authored-by: Claude <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 4, 2026
…entry#116893) Each tightening replaces `-> Response` with `-> Response[T]` where `T` is the same shape already declared in the method's `@extend_schema` decorator's `inline_sentry_response_serializer("...", T)` call. No source changes were needed — the autoderive plugin from getsentry#116879 already exposes `Serializer[T]` for the 15 sites' bodies, so mypy verifies them end-to-end without any helper or serializer touchups. Part of the march toward 100% `@extend_schema` typed coverage. Drives the Goal #1 metric from 54.1% → 64.4% (79 → 94 typed of 146 with-inline-serializer methods). Remaining ~50 sites need denylist removal + caller fixes, pydantic source rework, or helper annotations — handled per-cohort in follow-up PRs. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 4, 2026
…16898) Adds `-> Response[T] | Response[DetailResponse]` to four bare `-> Response` methods on `organization_detector_index` and `organization_workflow_index`. The success arm matches the `inline_sentry_response_serializer` T already declared in the `@extend_schema` decorator; the `Response[DetailResponse]` arm covers the `{"detail": "..."}` error paths. No source changes — the autoderive plugin from getsentry#116879 plus mypy's literal-narrowing already match each error-path body to `DetailResponse`. Part of the march toward 100% `@extend_schema` typed coverage tracked in the umbrella `type-http-response-coverage` change. Drives the Goal #1 metric from 64.4% → 67.1%. Other remaining sites need denylist removal or per-endpoint source typing — handled in follow-up PRs. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 4, 2026
…ry#116918) Tightens `project_tags.get` to `Response[list[ProjectTagKeyResponse]]` and `sentry_app_stats_details.get` to `Response[SentryAppStatsResponse]`. Both fixes type the response-building local variable (`data` / `result`) so the body matches the existing decorator-declared `T`. Pattern is the same as the cohort-2 PRs but reaches sites whose bodies are built inline rather than via a typed `Serializer`. Part of the march toward 100% \`@extend_schema\` typed coverage tracked in the umbrella \`type-http-response-coverage\` change. Drives Goal #1 from 67.1% → 68.5%. Other remaining sites need denylist removal (cohort 2e) or pydantic source rework (cohort 2d) — handled in follow-up PRs. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 8, 2026
Eleven Phase 1 / Goal #1 endpoint methods with `@extend_schema(inline_sentry_response_serializer(...))` but bare `Response` annotations. All fixes are typing-only at the source. Two patterns used: **Source-typed where the serializer is typeable:** - `organization_relay_usage.get()`: annotate `RelayUsageSerializer.serialize` + align TypedDict with runtime (datetime, nullable). - `organization_stats_v2.get()`: annotate `massage_outcomes_result` / `massage_sessions_result`; move `StatsApiResponse` to `snuba.outcomes`. **Typed-variable trick where the serializer is denylisted:** - `project_member_index.get()` — pin `context: list[OrganizationMemberResponse]` (OrganizationMemberSerializer denylist). - `organization_user_teams.get()` — pin `teams: list[TeamSerializerResponse]` (BaseTeamSerializer denylist); also fix decorator using serializer-class-as-type. - `organization_release_details.get() + put()`, `organization_releases.post()`, `project_release_details.get() + put()`, `project_release_stats.get()`, `project_release_repositories.get()` — pin locals against `ReleaseSerializerResponse` / `RepositorySerializerResponse` (ReleaseSerializer denylist). `as_validation_errors(serializer)` replaces raw `serializer.errors` in error paths so `Response[ValidationErrorResponse]` arms verify. --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 8, 2026
…entry#117123) Three more PUBLIC endpoints in the Goal #1 gap. - `group_ai_autofix.get()` → `Response[AutofixStateResponse]`. Both return paths already match the existing TypedDict shape; no body change. - `organization_group_index.get()` → `Response[list[StreamGroupSerializerSnubaResponse]] | Response[DetailResponse]`. Widen `StreamGroupSerializerSnubaResponse` with `NotRequired[matchingEventId / matchingEventEnvironment]` to declare the direct-hit mutations, then apply the typed-variable trick at four `serialize()` call sites (GroupSerializerBase is denylisted, so `serialize()` flows `Any`). - `group_details.get()` → `Response[GroupDetailsResponse]`. Fix three TypedDict drifts so the declared shape matches runtime: `inbox: InboxDetails | None`, `owners: list[OwnersSerialized] | None`, `sentryAppIssues: list[PlatformExternalIssueSerializerResponse]`. No body changes. --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 8, 2026
…17138) Five more Goal #1 endpoint methods. Typed-variable trick for denylisted serializers (Release, OrganizationMember) plus narrower union arms for the custom error shapes each endpoint emits. - `organization_member_requests_invite_index.post()` → `Response[OrganizationMemberResponse] | Response[DetailResponse] | Response[ValidationErrorResponse]`. - `project_releases.post()` → `Response[ReleaseSerializerResponse] | Response[ValidationErrorResponse]`. - `organization_release_assemble.post()` → `Response[ReleaseAssembleResponse] | Response[_AssembleErrorResponse]`. New local TypedDict covers the existing `{"error": str}` wire shape verbatim. - `installation_external_issues.post()` → 4-arm union: success + `DetailResponse` + `ValidationErrorResponse` + `SentryAppPublicErrorBody`. Also annotates `IntegrationPlatformEndpoint.respond_rpc_sentry_app_error` return as `Response[SentryAppPublicErrorBody]` (was bare). - `prompts_activity.get()` → 3-arm union with a new local `_NoFeatureSpecifiedResponse` TypedDict that preserves the existing `{"details": ...}` typo wire shape verbatim. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 9, 2026
Two more Goal #1 method tightenings. - `group_event_details.get()` → 3-arm union: `Response[GroupEventDetailsResponse] | Response[EventSerializerResponse] | Response[DetailResponse]`. The `stacktraceOnly` query-param path returns a stripped event shape (`EventSerializerResponse`) via the typed-variable trick — `EventSerializer` is denylisted, so `serialize()` flows `Any` and we pin the local to the typed shape. Normal path returns `GroupEventDetailsResponse` from `wrap_event_response`. Multiple error paths return `DetailResponse`; the shared `error_response` literal is pinned as `DetailResponse` so mypy reads it correctly. - `preprod_artifact_snapshot.post()` → `Response[SnapshotCreateResponseDict] | Response[DetailResponse]`. The success-path dict literal already matches the TypedDict; many validation paths emit `{"detail": ...}`. Branch name is stale — started by probing `release_file_details` endpoints but those have `FileResponse` paths I didn't want to touch in this PR. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 10, 2026
…ses) (getsentry#117276) Tightens 8 of the 14 Goal #1 untyped PUBLIC endpoints: - `release_threshold_status_index.get` → typed against existing `dict[str, list[EnrichedThreshold]]` decorator T - `organization_trace_meta.get` → `Response[OrganizationTraceMetaResponse]` via existing helper return type - `organization_trace.get` → `Response[list[SerializedSpan | SerializedIssue | SerializedUptimeCheck]]` matching the decorator - `organization_profiling_profiles` flamegraph + chunks endpoints → `Response[None] | Response[ValidationErrorResponse] | HttpResponse` (the success path is the proxy_profiling_service HttpResponse) - `project_profiling_profile.get` → `Response[dict[str, Any]] | Response[None] | HttpResponse` - `project_replay_recording_segment_details.get` → corrects the decorator from `list[dict[str, Any]]` to a structured `{"data": ...}` envelope via new local `_SegmentDetailsResponse` + `_SegmentMetadataResponse` TypedDicts. Spec-only correction; runtime has always emitted the envelope. - `project_replay_video_details.get` → `Response[DetailResponse] | HttpResponseBase` - `organization_stats_summary.get` → `Response[StatsSummaryApiResponse] | HttpResponse` Validation paths route through `as_validation_errors()`. No wire changes. --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
pull Bot
pushed a commit
that referenced
this pull request
Jun 10, 2026
…y#117280) Tightens the last 4 untyped PUBLIC endpoints, bringing the Goal #1 `@extend_schema` + typed-decorator gap to **zero**: - `group_ai_autofix.post` → multi-shape union (`AutofixPostResponse | AutofixHandoffResponse | None | DetailResponse | ValidationErrorResponse | str`). New `AutofixHandoffResponse` TypedDict captures the `step=coding_agent_handoff` branch's `{successes, failures}` envelope. The decorator's 202 keeps `AutofixPostResponse` (the kickoff/step-advancement default) — the linter accepts annotation arms not declared by the decorator (subset semantics). `trigger_coding_agent_handoff()` now returns `AutofixHandoffResponse` via a cast at the source-of-truth boundary (`client.launch_coding_agents` still returns `dict[str, list]`). - `organization_events.get` → `Response[EventsApiResponse] | Response[DetailResponse]`. `EventsMeta` widened to `total=False` with all keys `handle_results_with_meta` actually emits (`tips`, `units`, `dataset`, `dataScanned`, etc.) — the empty-projects short-circuit emits a meta with only `tips`, the standard path emits the full set. - `scim/teams.patch` → `Response[None] | Response[ValidationErrorResponse]`. The `ParseError`/`UnsupportedAttributeError` detail attribute is coerced to a dict at each except site so the union arm typechecks; the in-scope raisers all use SCIM-shaped dict details. - `event_attachment_details.get` → adds the missing `Response[EventAttachmentSerializerResponse] | Response[None] | Response[DetailResponse]` arms alongside the existing `StreamingHttpResponse` (the `?download` path). No wire changes. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Bumps the pip group with 2 updates in the / directory: cryptography and h11.
Updates
cryptographyfrom 43.0.1 to 44.0.1Changelog
Sourced from cryptography's changelog.
Commits
adaaaedBump for 44.0.1 release (#12441)ccc61da[backport] test and build on armv7l (#12420) (#12431)f299a48remove deprecated call (#12052)439eb05Bump version for 44.0.0 (#12051)2c5ad4dchore(deps): bump maturin from 1.7.4 to 1.7.5 in /.github/requirements (#12050)d23968achore(deps): bump libc from 0.2.165 to 0.2.166 (#12049)133c0e0Bump x509-limbo and/or wycheproof in CI (#12047)f2259d7Bump BoringSSL and/or OpenSSL in CI (#12046)e201c87fixed metadata in changelog (#12044)c6104ccProhibit Python 3.9.0, 3.9.1 -- they have a bug that causes errors (#12045)Updates
h11from 0.13.0 to 0.16.0Commits
1c5b075this time for surerd9c3699this time for sure...d91b9ddblacken5a4683cSoothe mypy9c9567fBump version to 0.16.0114803aMerge commit from fork9462006Bump version to 0.15.070a96beMerge pull request #181 from Julien00859/Julien00859/get_int_max_str_digits60782adReject Content-Length longer 1 billion TBdff7cc3Validate Chunked-Encoding chunk footerDependabot 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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.