Issue listing pagination transition from page-based to cursor-based in GitHub REST API

Goal: Retrieve large sets of GitHub issues efficiently while staying within rate‑limit and payload constraints.

Currently the REST API uses page‑based pagination with a per_page ceiling of 100 items, but internal discussions suggest a move toward cursor‑based pagination for more stable navigation. It is unclear whether the page parameter will remain supported, what the default page size will be under the new scheme, and how clients should handle responses that may mix both styles during the rollout.

What will be the supported pagination methods after the transition? Will existing page‑based requests continue to work, or must clients migrate to cursor‑based tokens? What is the maximum page size allowed when using cursor‑based pagination?