Skip to content

fix: avoid unnecessary re-downloads of the same runner as an "update"#812

Merged
Vysp3r merged 1 commit intoVysp3r:mainfrom
uwuclxdy:version-tags
Feb 16, 2026
Merged

fix: avoid unnecessary re-downloads of the same runner as an "update"#812
Vysp3r merged 1 commit intoVysp3r:mainfrom
uwuclxdy:version-tags

Conversation

@uwuclxdy
Copy link
Copy Markdown
Contributor

Category

Bugfix

Overview

This PR updates runner.vala to track the version tag of Latest runners with a .protonplus_tag file in runner's directory. After a successful update or when the existing version/proton check confirms the runner is up to date, a .protonplus_tag file is written inside the runner directory containing the GitHub tag_name. This is needed as some runners have different tags where the internal version/proton files don't match the tag_name (e.g., Proton-Sarek10-29 vs Proton-Sarek10-29-async).
I've discovered this issue while implementing cli support. Additionally, if API fails (for being rate limited, which happens often with the current implementation), check .protonplus_tag file and returns NOTHING_TO_UPDATE instead of an error (it was confirmed up to date when the file was created).

before:
image

after:
image

@Vysp3r Vysp3r merged commit 5ac68b8 into Vysp3r:main Feb 16, 2026
1 check passed
@uwuclxdy uwuclxdy deleted the version-tags branch February 16, 2026 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants