Repository navigation
Couldn't get the latest Tectonic release since recent update #651
Description
Tectonic recently released a new version (on April 10th). Since then, my workflow has been failing with the following error:
Error: Couldnt get latest tectonic release
I managed to work around this by temporarily pinning a specific version in my workflow (I used 0.15.0, though I haven't tried any others).
I'm not entirely sure if this is an issue with the Tectonic repository itself or with this GitHub Action workflow. If it's not related to the workflow, feel free to close this issue! I just wanted to report it in case someone else runs into the same problem, or in case there is a bug in how the action fetches the latest release.
Activity
WtfJoke commentedon Apr 13, 2026
Hi @FelixSiegel
Thanks for reporting it, can confirm the issue (not sure where the issue lies, but older version are still working as you wrote). I will look into it.
🐛 Fix pagination issue in getLatestRelease (#651)
🐛 Fix pagination issue in getLatestRelease (#651)
🐛 Fix pagination issue in getLatestRelease (#651)
🐛 Fix pagination issue in getLatestRelease (#651) (#652)
WtfJoke commentedon Apr 13, 2026
Fix is merged and rolled out in latest setup-tectonic v4 release (v4.0.3).
Background:
So it was a bit of both, but mainly the issue was on my (the action side) when not specifying an actual version (so specifying 0.16.8 would have worked as well).
When not specifying a tectonic version and using latest, the action crawls the 30 last releases (default pagesize) and looks for the tectonic (binary) release. The issue was, that tectonic published recently more than 30 releases without publishing an actual tectonic release 😅 (when I built that I wouldn’t have thought that there might be more than 30 releases without a binary releases, my bad :D).
Now first the latest release will be checked (latest release seems to be maintained now by the tectonic maintainers or its a coincidence currently) and if that is not a tectonic binary release it looks for the 100 last releases and paginates until it finds one or gives up eventually (or get rate limited).
FelixSiegel commentedon Apr 13, 2026
Thanks for the fast reaction to this issue. I never would have guessed that was the cause, but it's interesting how those unexpected edge cases pop up. 😅
The fix sounds solid. Thanks for your effort on this!