fix(pagination): when tagging release, use updated, vs., created

[bcoe]

There's a danger that someone comments on an old merged release PR, brining it earlier in chronological order, this would mean that we attempt to re-release the same version given how last release is calculated.

This is not a problem when tagging a release, which only occurs once after a PR is merged.

[codecov]

Codecov Report

Merging #708 (670f0e4) into master (e0c7b00) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master     #708   +/-   ##
=======================================
  Coverage   86.77%   86.78%           
=======================================
  Files          55       55           
  Lines        6579     6582    +3     
  Branches      616      586   -30     
=======================================
+ Hits         5709     5712    +3     
  Misses        869      869           
  Partials        1        1           

Impacted Files	Coverage Δ
src/github-release.ts	96.17% <100.00%> (+0.03%)	⬆️
src/github.ts	83.70% <100.00%> (+0.01%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update e0c7b00...670f0e4. Read the comment docs.

[feywind]

To paraphrase Asimov, we had the answer that satisfied but now we have the answer that was true :D