It occurred to me when looking at FL-9231 and the GraphQL bug that we should be looking at ways to improve the capabilities/quality of our tag and release selection, rather than purely looking at technical features like pagination and API language. So basically, adopt a "results-oriented approach".

This is because our goal, as metatools users, is to have our GitHub API provide reasonable and intuitive defaults, so we should think about what we would consider to be better default query behavior.

For example, I was thinking, let's say you query a single page of tags, and you can see that you have received all the tags that have been created in the last 5 years. Do you really want to exhaustively query ALL tags for versions?

It is possible to query tags this way:

https://api.github.com/repos/zeromq/libzmq/git/matching-refs/tags

We are currently using this way:

https://api.github.com/repos/zeromq/libzmq/tags

both provide pagination, but none provide easy date metadata. Is GraphQL different and could it provide this capability?