Consider tagging releases

[jaraco]

I notice that this repo has no tags. That means there are many different commits that correspond to a given release in PyPI. I recently wanted to know what releases might contain the fix for #147, so I went to the merged commit containing the fix (5def664), but it gave me no indication of what version(s) might contain that fix. After figuring out where the version is stored, I can see that the version at the time that commit was added was 1.8.0, implying that >1.8.0 would include the fix. Still, it would be nice if there were a way to see which commit specifically was the one that was released to PyPI for any given release. Is there any reason not to tag commits with the release numbers?

[polyzen]

Running git blame on src/pyperclip/init.py to find commits matching particular releases is rather tedious, please tag releases to make things easier for downstream consumers. We at Arch Linux (and perhaps others) have to dig up the commit manually for every release when we want to update our package.

[polyzen]

Finding what's changed between releases also requires this tedium.