fix(api): Add missing cursor query parameter to paginated endpoint OpenAPI schemas

[MathurAditya724]

Summary

• Adds CursorQueryParam to @extend_schema parameters on 19 paginated API endpoints that support cursor-based pagination at runtime (self.paginate()) but were missing the cursor query parameter in their OpenAPI spec
• This is a schema-only change — no runtime behavior is modified. The cursor parameter already works at runtime because self.paginate() reads it from request.GET; this just makes the OpenAPI spec accurately reflect that

Motivation

The getsentry/sentry-api-schema repo (which produces the @sentry/api npm package) consumes the OpenAPI spec generated from this repo. The missing cursor declarations cause the generated TypeScript SDK to produce types where query is never or omits cursor, making type-safe pagination impossible for SDK consumers.

Upstream issues:

• getsentry/sentry-api-schemaDebian package configuration #59 — unwrapResult() discards Link headers, consumers can't paginate
• getsentry/sentry-api-schemasentry permissions not working (patch included) #60 — Missing paginated variants for team, repository, and issue list endpoints

Endpoints Modified

Priority 1 — High-impact (actively blocking SDK consumers)

Endpoint	File
GET /organizations/{org}/repos/	src/sentry/integrations/api/endpoints/organization_repositories.py
GET /organizations/{org}/releases/	src/sentry/api/endpoints/organization_releases.py
GET /organizations/{org}/members/	src/sentry/core/endpoints/organization_member_index.py
GET /organizations/{org}/issues/{issue_id}/events/	src/sentry/issues/endpoints/group_events.py

Priority 2 — Other paginated endpoints

Endpoint	File
GET /organizations/{org}/integrations/	organization_integrations_index.py
GET /organizations/{org}/monitors/	organization_monitor_index.py
GET /organizations/{org}/monitors/{monitor}/checkins/	organization_monitor_checkin_index.py
GET /organizations/{org}/releases/{version}/commits/	organization_release_commits.py
GET /organizations/{org}/releases/{version}/deploys/	release_deploys.py
GET /organizations/{org}/releases/{version}/files/	organization_release_files.py
GET /organizations/{org}/repos/{repo_id}/commits/	organization_repository_commits.py
GET /organizations/{org}/sentry-app-installations/	sentry_app_installations.py
GET /projects/{org}/{project}/releases/{version}/commits/	project_release_commits.py
GET /projects/{org}/{project}/releases/{version}/files/	project_release_files.py
GET /projects/{org}/{project}/rules/	project_rules.py
GET /projects/{org}/{project}/tags/{key}/values/	project_tagkey_values.py
GET /projects/{org}/{project}/teams/	project_teams.py
GET /projects/{org}/{project}/user-feedback/	project_user_reports.py
GET /projects/{org}/{project}/users/	project_users.py

Endpoints from plan intentionally skipped (do NOT paginate)

These were listed in the plan but return full results directly without self.paginate():

• OrganizationUserTeamsEndpoint — returns Response(serialize(list(queryset), ...))
• ProjectEnvironmentsEndpoint — returns Response(serialize(list(queryset), ...))
• ProjectMemberIndexEndpoint — returns Response(context) with manual sort

How It Works

The CursorQueryParam serializer is defined in src/sentry/apidocs/parameters.py and declares a single optional cursor string field. Adding it to @extend_schema(parameters=[...]) causes drf-spectacular to include the cursor query parameter in the generated OpenAPI JSON for that endpoint.

Fixes getsentry/sentry-api-schema#59
Fixes getsentry/sentry-api-schema#60

[JoshFerge]

for some of these endpoints, the api docs may not be based on the in-code tooling, for example the user reports

sentry/api-docs/paths/projects/user-feedback.json

Line 4 in 3940fa1

"description": "Return a list of user feedback items within this project.\n\n*This list does not include submissions from the [User Feedback Widget](https://docs.sentry.io/product/user-feedback/#user-feedback-widget). This is because it is based on an older format called User Reports - read more [here](https://develop.sentry.dev/application/feedback-architecture/#user-reports). To return a list of user feedback items from the widget, please use the [issue API](https://docs.sentry.io/api/events/list-a-projects-issues/) with the filter `issue.category:feedback`.*",

will need the json there updated