Skip to content

Remove v1 pagination logic [staging] - #516

Open
duckduckgrayduck wants to merge 1 commit into
stagingfrom
remove_dead_pagination_code
Open

duckduckgrayduck wants to merge 1 commit into
stagingfrom
remove_dead_pagination_code

Conversation

@duckduckgrayduck

@duckduckgrayduck duckduckgrayduck commented Oct 26, 2026 •

Copy link
Copy Markdown
Contributor

Related issue: #490

Remove API v1 page-number pagination

v2 cursor pagination has been the default in production for a long time, and v1 is deprecated. This removes the v1 pagination code, but keeps the versioning infrastructure in case we need a v3.

  • ALLOWED_VERSIONS is now ["2.0"], so ?version=1.0 returns a 404. QueryParameterVersioning is kept for a future v3.

  • Removed PageNumberPagination, VersionedPagination and VersionedCountPagination. CursorPagination is now the default, and ProjectMembershipViewSet uses CursorCountPagination directly.

  • Solr search no longer reads version itself. It always uses cursor pagination, and the page-number path (_paginate, _paginate_page and the page branch in _format_response) is removed.

  • Removed the AUTH_PAGE_LIMIT/ANON_PAGE_LIMIT settings, which only v1 used. After deploying, we should remove those env vars on Heroku too.

  • The search ValueError handler now returns "code": "invalid_query" instead of "max_page", since it now only catches luqum ParseErrors. The API docs now say v1 has been removed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants